Godot racing templates give you two different answers to how a car drives

Kenney Starter Kit Racing is the first. It is 3D, viewed from behind the vehicle, released under MIT and CC0, and it is built as a foundation rather than a showcase. Its own description covers an arcade vehicle controller, track pieces you can lay out, a follow camera, smoke, and skid and engine sounds. There is a motorcycle variant alongside the car.

The second is Truck Town, one of the demo projects the Godot project maintains itself. Also 3D and MIT licensed, it exists to demonstrate the engine's built-in vehicle physics: selectable trucks including trailer and tow variants, driving built on Godot's VehicleBody3D, several cameras to switch between, a speedometer, and a town to drive around with its own lighting moods.

The intents are different and that matters more than the feature lists. A starter kit is written to be extended. An engine demo is written to show you that something works. Both are honest about themselves; neither is pretending to be a game.

This is the fork. An arcade controller does not simulate a car. It moves a body around according to rules chosen because they feel good, and grip is a number somebody picked. Kenney's kit sits at that end. Godot's VehicleBody3D sits at the other: actual wheels, actual suspension, engine force applied through them, and handling that emerges from physics values rather than being stated directly. Truck Town is the demonstration of that path.

Neither is the correct answer. They fail in opposite directions. Arcade handling struggles the moment you want weight to matter, a trailer to swing, or a heavy vehicle to behave differently from a light one. Simulated handling struggles when you want the car to simply feel snappy and responsive, because you cannot type that in. You approach it through spring rates and friction until it arrives.

The reason to decide early is that the choice is not a setting. Everything you tune, every piece of feedback you build, and much of what your track has to be, is shaped by which model you are on. Swapping late means throwing away the tuning, which is where most of the work went.

A track. Both projects contain something to drive on, and that is not the same thing. A track is a sequence of corners with a rhythm, sightlines that let a driver commit, a straight long enough to matter, and at least one place where overtaking is possible but not free. Laying that out is the design job of the genre, and it takes driving your own track badly a great many times.

Opponents. AI drivers that are enjoyable to race against are their own discipline: a racing line, a sense of when to yield, mistakes that look like mistakes rather than malfunctions, and some quiet correction so the pack stays near you without it being obvious. None of the starters solve this, and it is the difference between a driving toy and a race.

The race itself. Laps, checkpoints, a timer, position, restart, a results screen, penalties for cutting the corner you will absolutely cut. And the sensation of speed, which is largely a lie told by camera and sound: field of view widening, the camera lagging under acceleration, engine pitch, tyre noise, wind. None of that comes out of the physics. It is all built on top, and it is half of what players mean when they say a car feels fast.

Handling is tuned by changing values in the vehicle script and driving again. That loop is the work in a racing game, and there is no way around doing it many dozens of times. What is worth knowing in advance is that the values mean completely different things on either side of the fork. Grip in an arcade controller is a dial the author invented. Grip in a wheel simulation is an outcome of four or five interacting settings, and moving one moves the others.

So adopting a racing starter is adopting somebody's vocabulary as well as their code. Before you can change the feel you have to work out which value in their script corresponds to the thing you disliked while driving. That translation is the real cost, and it is paid in reading rather than in typing.

If you read GDScript this is a fair price for skipping the whole build-a-car stage. If you do not, you have a car you can drive and cannot adjust, in a genre where adjusting the car is the game.

Stage Engine goes at it from the other end. It is a desktop app for Mac and Windows with Godot bundled inside. You lay out the track yourself, as terrain and as intent, and Director 1 writes the driving, the lap logic and the opponents as GDScript in your project. The handling model is chosen for the game you are making rather than inherited from a demo, and when you dislike how the car turns in you say so and drive it again.

What that is not: there is no template picker in Stage Engine, and Kenney's kit and Truck Town do not open inside it. Those are public projects you clone and open in Godot yourself. These are two separate ways to end up with a racing game, not two menu items.

Building needs an internet connection, since Director 1 and asset generation come over the network. Driving what you built does not; it runs locally on your own machine at your machine's framerate, which for a racing game is not a small detail. The download is free, Indie is $10 a month, Pro is $50, and paid plans buy more usage rather than a different engine.