Skip to content

Racing games are won or lost on the car, not the track

By Eduardo Orellana · Updated

You can tell whether a racing game is any good in one corner. Flockbay makes handling something you tune by driving and describing, rather than by editing a physics script you did not write. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

The main page on this subject is AI racing maker: karts, hovercraft, boats. Racing is wider than cars.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The first corner is the review

Players decide about a racing game almost immediately, and the decision is about the car. Does it turn in when you ask. Does the back end do something you can predict. Does braking transfer weight in a way you can feel. Is there a difference between fast and slow, or does it just move.

This is why so many first racing games feel dead. They have a track, a lap counter, a car that moves at a speed, and no handling model worth the name. The scenery is fine and the driving is nothing.

Handling is code, and it is code you tune by driving rather than by reasoning. That takes a lot of iterations, which is exactly what a person who does not program cannot afford.

More on this: Racing game maker: handling is a feel, and feel is tuned by driving

How you tune a car without writing physics

You drive it and describe the problem in the words you would use to a friend. It pushes wide on the exit. It snaps around when I lift. It feels heavy in the slow stuff and light over crests. Flockbay changes the GDScript in your project.

None of that requires you to know what a slip curve is. It requires you to notice, which anyone who has played racing games can do. Naming the technical cause is the part that gets handled for you.

Then you drive again. Twenty times in an afternoon is normal, and that iteration count is the whole reason the car ends up feeling like something.

More on this: Godot racing templates give you two different answers to how a car drives

Tracks in a real landscape

Flockbay builds tracks into real terrain from a Godot terrain plugin, with water and weather where the game needs them, so a track is a route through a landscape rather than a ribbon floating in a void. Elevation change is where racing tracks get their character: blind crests, downhill braking zones, cambers that help or betray you.

Flockbay lays the route from the brief, and the verdict on each corner comes from driving it, because the placement of a corner in a landscape is a judgement a sentence only gets close to. Say the hairpin comes too soon after the crest and it moves; when it is a matter of metres, Godot's own editor is right there and you can move it yourself. Drive it, move it, drive it again.

Weather is a layer of the world, so the same circuit in rain at dusk is a different event from the same circuit at noon. That is cheap variety of the good kind.

The rest of the game

Lap timing, checkpoints, position, a rewind, opponent AI, a championship structure, tyre wear if you want it. All of that is code described in plain language and written into your project.

Opponent AI deserves a mention because it is the practical route to a game you can play alone. Flockbay provides no servers, hosting or matchmaking, so online racing is not something it hands you. Bots that drive the line and make mistakes are.

What it runs on

A desktop app for Windows, macOS and Linux with Godot bundled inside it. Your game runs locally on your own hardware, which for a genre judged on frame timing and input latency is the only sensible arrangement.

Building needs an internet connection because the chat and asset generation come over the network. Playing does not. Free to download. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Speed is an effect, not a number

A car doing two hundred can feel slow and a kart doing forty can feel terrifying. The sensation comes from things around the number: field of view widening with speed, camera shake, motion blur, engine note rising, objects close to the road, a bit of screen distortion at the top end.

This is worth knowing because the instinct when a game feels sluggish is to raise the speed, and that usually makes it worse. The car becomes hard to place and the sensation does not improve.

Every one of those effects is code and each is a sentence to request and a lap to evaluate. Try the presentation before the physics; it is cheaper and more often the actual problem.

A starting project for this is the racing and sports game templates.

Questions

Can I make an arcade racer rather than a simulator?
Yes. The difference is in the handling code, which is described and tuned the same way either way.
How do I tune handling with no physics knowledge?
By driving and describing what feels wrong. Translating that into a change to the code is the part Flockbay does.
Is online multiplayer racing possible?
Not from Flockbay, which provides no servers or matchmaking. AI opponents are the supported route to racing against something.
Where do the cars come from?
The library of ready-made objects, your own models, a model Flockbay builds on your computer with no key, Godot's own shapes, or a generated model on your own Tripo key. You will be told which route was used.
What does it cost?
The platform costs nothing. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

Free for Windows, macOS and Linux. Get one corner feeling right and the rest follows.

Download Flockbay free