Known issues (tester build 0.7)

Thanks for testing. These are the problems we know about in this build, with a way round each one, so you don’t have to report them again (but do tell us if one hurts you). Labels are from docs/FEATURES.md. If you hit something that isn’t here, use Help > Report a bug and tell us roughly what time it happened.

Signing in and the launcher

Sign in can fail with a network error. The sign-in service isn’t open to everyone yet. Workaround: if your invite came with a tester token, paste it under Use a tester token instead (on the Projects tab, under Sign in). It works until you sign in with your account.
Right after installing, the Engine tab can say “No online documentation” and show an old “Last checked” time. Workaround: ignore it; the engine works normally.
“Windows protected your PC” appears when you run the installer or a game you downloaded. The files are new, so Windows hasn’t seen them yet. Workaround: choose More info, then Run anyway.

The editor

If the editor closes unexpectedly, open the project again: it offers back the work you hadn’t saved. Save often anyway while this is new, and tell us the time it happened.
When your AI starts the editor for you, the editor’s Log tab shows red “423 busy” lines every time you press Play. Play still runs normally. Workaround: open the project from the launcher yourself; then the lines don’t appear.
The Log tab is noisy on every Play: about ten technical lines, some of them raw data, and sometimes messages about “no authoring SDK” or “unverified content”. Workaround: ignore them; they don’t mean anything is wrong. A real problem pauses Play with a red “A script threw an error” message, and Open log shows just the errors.
Opening the Collection course template logs a warning that Arabic needs characters no font has. Workaround: ignore it; it only matters for a game shown in Arabic.
The editor doesn’t warn you when a scene has more triangles than its budget (for example after importing a detailed character). Workaround: if the game gets slow, ask your AI how many triangles the scene has against its budget, and use a lighter model.
A new first-person project can look dark and flat. Workaround: in World Settings, raise Exposure or Ambient, or ask your AI to brighten the scene.
In a new empty 3D project, the player can walk off the edge of the starting floor (it is only 20 m wide) and fall, and the camera then looks blocked by the floor. Workaround: make the floor bigger, or stay on it.

Working with your AI

Your AI may say a results screen whose only button is “Race again” has no way back. That isn’t a real problem. Workaround: if the game plays fine, ignore it; ask your AI to Play and check rather than trust the warning.
Your AI may build a kart as a scripted player instead of a real vehicle, because an old driving-course example still says there is no vehicle component. Workaround: ask it to use the vehicle and wheel components, as the Kart Starter does.
HUD text set directly, such as a lap counter “1/3”, can show up in double brackets: [[1/3]]. Workaround: ask your AI to set the value as a number, as the Kart Starter does (ctx.hud.set("lap", 2) shows the lap), or to use a text key from the game’s strings instead of the raw text.
For script authors: a few physics queries are unreliable. Box and capsule overlap checks don’t see terrain, an overlap check can return an object that was removed that same frame, and a contact can be reported for about 5 frames after two objects separate. Workaround: use a ray cast down for terrain, check that an object still exists before using it, and don’t rely on contacts for exact timing.

Vehicles (Kart Starter and karts you build)

Driving nose-first into a wall with the wheel turned can pin the kart there, and clipping a thin post with its edge can spin it round. Workaround: press R (Y on a pad), or wait 3 seconds and it puts you back on the road by itself.
A kart your AI builds doesn’t put itself back when it gets stuck or rolls over. The Kart Starter’s reset (R, or by itself after 3 seconds) is the sample’s own script, not part of the engine yet. Workaround: ask your AI to give your kart the Kart Starter’s behavior, or to copy its reset.
The vehicle “assists” settings (traction control, stability control, steering assist) do nothing yet, even though the descriptions your AI reads list them. Workaround: leave them out; tune the tires’ grip (tyres.muLat, tyres.muLong) and the steering lock (steering.maxAngle) instead.

Exported games

The first launch of a new game takes a few seconds while Windows checks the files; later launches take about 1 second.
A crash report opens with a dozen or so “unknown” lines. Workaround: send it anyway; the list of modules and offsets below those lines is the useful part.
Help > Report a bug sends the recent log but not the crash details. Workaround: in the report, say what you were doing and roughly what time it crashed.

Linux

This tester build is for Windows. A Linux x64 build is a tarball with the editor and the engine, but no launcher and no samples: the samples come only from the Windows launcher today. See START-HERE.md, “On Linux”.
A game exported for Linux needs the ALSA sound library on a fresh Ubuntu: without it the game doesn’t start and says nothing. Install it with sudo apt install libasound2t64 (Ubuntu 24.04).

Other

Arabic text that starts with a number can lose the number. Only games shown in Arabic are affected.

Features

Beta (works, below our quality bar): terrain, water (lakes, rivers, shores, waterline), foliage (including the fern preset), lighting and global illumination, characters and animation, vehicles, effects, the editor itself.
Experimental (off unless a project lists it in "experimental"): waterfalls, the forest-floor ground cover, lip-sync, the Android exporter, asset generation.
Tested on desktop graphics cards; laptops and integrated graphics are not tested yet.