Online 3D game maker: the 3D is the reason this one installs

Everything hard about 3D is a spending problem. Draw distance costs. Terrain detail costs. Dynamic shadows cost. Every character alive at once costs. A 3D tool is mostly a set of decisions about where that budget goes.

A browser tab has a small budget and cannot be given a bigger one. That is not a criticism of any particular web tool, it is what a tab is. So browser 3D makers spend carefully: modest scenes, simple lighting, low counts, short view distances. They are honest engineering inside a fixed box.

Stage Engine installs on your machine and spends your machine's budget. That is the entire reason it is a download rather than a site. If the game you want is a small stylised scene, the box may be big enough and a web tool will be faster to start. If it is a landscape you can walk across, it will not be.

Terrain you shape by hand, which holds a real form rather than being a heightmap sketch. Water that fills the valley you cut instead of sitting on top of it. Sky and weather as controls you set, so an overcast morning and a hard noon are choices rather than accidents.

And population. A world with things moving in it — characters going about their business, weather changing, distant detail still drawing — is the case that separates a world from a scene, and it is the case that needs local hardware.

You place all of this yourself, with a mouse, in a builder that behaves like a level editor. Spatial decisions are faster made than described, so the builder is where you make them.

Director 1 writes the GDScript. Movement, interaction, inventories, enemies, whatever the game needs. It goes into your project, which is a real Godot project on your disk, and you never have to open it.

You play the result and judge it. If the camera is wrong or the jump is floaty, you say so and it goes again. That loop is the intended way to work, not a fallback.

It only runs on Mac and Windows. No Linux build, no browser, no phone or tablet version of the builder.

Building requires an internet connection, since Director 1, asset generation and world data all come over the network. This is not offline software and there is no degraded mode. The game you built plays locally without a connection.

Bigger worlds ask more of your computer. Local rendering means the ceiling is your hardware, which is higher than a tab's but is still a real ceiling.

Free to download with a free plan you can build on. Indie is $10 a month, Pro is $50. The paid plans buy more AI usage. The renderer, the engine and the export path are the same on every plan.

Build a small piece of landscape and walk around it. Not a game, just ground, a horizon and something to stand on. Fifteen minutes of that tells you more about whether a tool suits you than any feature list.

Pay attention to two things while you do it. Whether the controls do what your hands expect, and what the framerate does when you turn to look at the whole scene. The first is taste and the second is your hardware answering a question you need answered.

Then ask for one behaviour. Something that moves, something that opens, something that follows you. That completes the loop the tool is built around, and from there the difference between an experiment and a project is mostly time.