Performance settings: getting a smooth drift on modest hardware
If Slipline Garage runs slowly, open Settings → Graphics and set Quality to Low. Low turns off shadows and anti-aliasing, renders at your screen’s base resolution and uses about a third of the smoke particles. It changes nothing about how the car handles or scores.
What each preset changes
| Low | Medium | High | |
|---|---|---|---|
| Shadows | Off | On, 1024 px map | On, 2048 px map, softer |
| Anti-aliasing | Off | On | On |
| Maximum pixel ratio | 1× | 1.5× | 2× |
| Smoke particles | 48 | 140 | 260 |
| Skid mark segments | 240 | 700 | 1,400 |
Automatic (the default) picks Low on most touch devices, on machines reporting four or fewer processor cores or 4 GB of memory or less, and when the browser reports an integrated graphics chip. Otherwise it picks Medium. If Medium still cannot hold its frame rate after resolution has been lowered as far as it goes, Automatic steps down to Low once and tells you. The Settings screen shows which one is in use.
Resolution adapts before anything else
On every preset the game watches its own frame time. If frames take longer than about 26 ms on average, it lowers the internal rendering resolution in 10% steps, down to 60% of the preset’s maximum. If frames get comfortably fast again, it raises it back. The picture gets a little softer; nothing else changes.
This is deliberate. Track edges, car silhouettes and clipping zones stay readable, and the simulation is untouched.
Why handling never changes with quality
The physics runs on its own clock: 60 fixed steps per second, each split into two smaller steps, regardless of how many frames your screen manages to draw. A slow machine draws fewer pictures of the same simulation. An automated test replays one recorded set of inputs at 30, 60, 120 and 144 frames per second and requires the car to finish in the same place with the same score.
If a frame stalls badly — a background tab, a system hiccup — the game simulates at most five steps for that frame and drops the rest. The run slows down for an instant instead of leaping forward.
A checklist for slower machines
- Set Quality to Low. The single biggest change.
- Close other tabs, especially video. They compete for the same graphics memory.
- Turn on hardware acceleration in your browser’s settings, then restart the browser. Without it, 3D runs on the processor and will be very slow.
- Plug in. Many laptops throttle graphics on battery.
- Shrink the browser window. Fewer pixels to draw. The game scales to any size.
- Turn on Reduced effects (Graphics) for even less smoke.
- Pick Academy Yard or Canyon Loop first. Skyline Deck draws the most scenery.
If the game will not start
- “3D graphics are not available.” Your browser is not providing WebGL. Update the browser, enable hardware acceleration, or try another current browser.
- “The graphics context was lost.” The graphics driver reset. Your run is paused and your saved progress is safe; the game offers to restore or retry, and a Retry on Low quality button.
- An endless load is never the answer. If something fails to load, the game shows what failed and a retry button instead of spinning forever.
What has been measured, honestly
One real measurement exists so far: a Windows 11 laptop with Intel UHD integrated graphics, in Chrome, on Harbor Circuit at roughly 1520 × 670. Low ran at 60 frames per second (median frame 16.8 ms). Medium held 30. That is one machine, not a promise for yours.
The game has not yet been measured on a physical Chromebook, a low-end laptop or a mid-range phone, so this page does not state a frame rate for them. The targets the project holds itself to are 60 frames per second on a reasonable desktop and a usable 30 on Low for mid-range phones; those are goals to verify, not results. If you play on modest hardware, a note via the contact page saying what you saw is genuinely useful.
Related: drift games on a Chromebook and how a browser drift game works. Or head back to the drifting games overview.