afarchy

About a minute to delete and recreate the runner.

Thanks for the tip! I'll need to find out where museum folks hang out.

The editor portion is written from scratch using Svelte for the UI and BabylonJS for rendering.

What kinds of customization are you looking for? I'd love to know about the gap between what your clients need and what Virtual Maker does today.

This echoes my understanding as well. Virtual Maker uses BabylonJS under the hood for rendering. That said, I've been interested for some time in finding/developing a standard format for describing 3D content which can include some form of input handling (GLTF is just rendering, AFAIK). Think <button>, but for 3D/VR. Maybe then we could port some simple experiences easily between engines.

I've worked with both Unity and Unreal on past projects. While I love both, they have steep learning curves, long build times, and deploying cross-platform is much more difficult than the web.

Virtual Maker is a simplification of the whole process. We have built-in actions, navigation modes, and assets that you can use to get going quickly. We take care of hosting for you, ensuring your scenes work across platforms, with instant deploy times.

Of course, that means Virtual Maker won't give you all the options that Unity and Unreal do to build anything you can imagine. It's a trade off, and depends on what kind of project you're making.

Hello HN,

After spending the last decade designing and building 3D/AR/VR products, I've realized there are many hurdles one has to overcome to create a complete experience. Between learning the principles and tools, building the experience, testing, iterating, distributing, and ensuring everything works correctly on different devices, there's quite a bit of boilerplate work required to bring your imagination to life.

I designed Virtual Maker to simplify the whole process, letting you focus directly on designing your experience. Let me know what you think!