CALL TO ARMS — help build the game YOU want
Synapse Grid is a solo-dev game, and in the last month it has been shaped more by players pressing one button than by anything on my roadmap. This post is the next build, a thank-you, a look back at what you fixed — and an ask: keep them coming.
Press SPACE in any match — playing, paused, or on the results screen — to open the bug reporter. Fly the frozen scene, click the exact spot you mean, write a line if you want, and SAVE. You do not even have to write a word. Three of the fixes below happened because a player pressed that button and wrote nothing at all.
Every little bug report goes noticed, and I will definitely take action. That is not a slogan — the Month in Review below is the proof.
1.92.3 (build 144) — your graphics setting now works in solo missions
Fixed: the graphics setting did nothing in solo missions
A player on an Intel UHD laptop (Pentium Gold 7505) sent an in-game report from the tutorial on 22 October: 14 fps on Medium. Their report carried a new graphics line — and it showed the 3D view running at full resolution with no anti-aliasing. Medium never reached the game. The setting was applied in the menus and in local / split-screen matches, but never in solo missions — and solo is the tutorial and the whole campaign.
- Solo missions now use the setting you picked: Low renders the 3D view at 75% resolution, Medium at 85%, each with its anti-aliasing. Changing it in the pause menu takes effect immediately.
- Integrated graphics now start on Low the first time: Intel UHD-class laptops, and new Steam Deck installs. A setting you already chose is never changed.
- High now applies its anti-aliasing in solo too, including 1.92.1's AMD rule: no multisampling under ambient occlusion on AMD cards.
Full test suite on this build: 14,744 checks, 0 failures.
Also in 1.92.3: glaring white (or black) patches on Intel and AMD — fixed
The same player's screenshot showed a big white glare washing out the floor by the tutorial's nodes. A few shaders raised a number to a power when it could dip just below zero — undefined on a graphics card. NVIDIA hides it; Intel spreads it white, AMD spreads it black (that is the same family as the 19 October AMD black-screen report). The shaders now clamp the value first, and a new automatic check fails the build if any shader ever brings it back. The look is unchanged everywhere it was already correct.
Thank you
Many thanks for notifying me — to the Intel UHD player who pressed the report button in the tutorial on 22 October: thank you. The screenshot showed the glare, and the graphics line showed your Medium setting never reached the game. Both are fixed because you pressed that button. You made the game better for everyone on integrated graphics.
Your call to arms — 3 ways to build this game with me
- 1. REPORT BUGS — SPACE > SAVE, in-game. A crash, a black screen, a wall that kills you unfairly, 14 fps, a boring mission, a confusing lesson — all of it belongs in a report. The report auto-carries your screenshot, mission, seed, settings, graphics driver and hardware, so I can replay the exact moment. No bug is too small, and no message is required.
- 2. OFFER SUGGESTIONS — Steam Discussions, or the Discord linked on the store page. What do you want Early Access to become? Missions, sectors, rivals, difficulty, maps, accessibility, performance on YOUR hardware, controller and Steam Deck feel — tell me what would make you stay. Critical feedback and "this level is boring" are welcome here. Be specific; specifics get built.
- 3. HELP BUILD IT — play the demo hard, make maps, tell other riders. Push on the tutorial, try to break the editor and packages, test Low on the weakest laptop you own, and report what happens. In Early Access, starting Oct 28, your reports set the order of the first updates.
My promise back: every report gets noticed, acted on, and thanked publicly in the patch notes — by name if you leave one, anonymously if you don't. I will never argue with a negative review, and I will never pay for or incentivise one. Honest feedback is the whole deal. And as always: $7.99, $4.79 for launch week, buy once — no microtransactions, not now, not ever.
Month in Review — what you fixed, September to October
This started as a beta demo on Sep 8. Since then, almost every build exists because a player, a reviewer, or this community found something I could not see from my own desk:
Online, LAN and Steam review fixes (September)
- Steam lobbies that actually answer: the game was listening for Steam's reply on the wrong channel. It now listens on the networking peer, warms Steam's relay at boot, waits a full 30 seconds with a visible count, and tells you why if it ever fails.
- QUICK MATCH always finds a ride: our own partner host sits in a public lobby around the clock and plays as the Seeker.
- TEST LAN HERE: one click launches a second copy on your machine that joins over real LAN broadcast — no second PC needed.
- Your first bug report, fixed the same morning: a hazard bar / sentinel could sweep straight through a jump pyramid on The Warden / m06. Its whole path is now kept clear of every ramp.
Controller, Linux and Steam Deck (September)
- Pad A confirms, B cancels — everywhere, including the pause menu. START pauses. The Steam Overlay pauses. Unplugging your pad pauses. The mouse cursor hides while you play on a pad.
- Pad glyphs on every prompt, with PlayStation names on Sony pads, and a published Developer's Recommended Controller Configuration on both apps.
- Native Linux / SteamOS builds — no Proton — verified and shipped on both the game and the demo.
1.91.0 — the map editor grows up
- A real file menu, layers, free orbit camera, move/turn/scale handles, undo, and VALIDATE that lists problems and jumps you to the piece. One-click PLAYTEST, and back to the editor when you're done.
- Maps and mods became one hardened, data-only PACKAGE format — nothing in a package is ever run as code, bad packages are refused by name, never with a crash. New CONTENT screen, plus the official Hub Starter template to build from.
- Settings from the pause menu stopped throwing away your run — it opens over the paused match now.
Player-report hotfixes (October)
- 1.92.0 (Oct 18) — Steam Deck player, tutorial finale: the closing walls moved faster than the bike (13.5 vs 12 units/sec) with no warning, so GRID IGNITION ended in 1 second. Fixed the same day: walls now cap at half your cruise speed, with a 5-second on-screen countdown, and the readout says TAIL ENDLESS.
- 1.92.1 — RX 6500 XT player, Oct 19, "Camera constantly freaking out can't see anything": the world rendered black on AMD while the HUD stayed perfect. High on AMD now drops 3D multisampling and keeps ambient occlusion, fog, glow, shadows and FXAA. Bug reports now include your graphics driver and 3D settings.
- 1.92.2 into 1.92.3 — Intel UHD player, Oct 22: the white/black glare shader fix above, plus the solo graphics-setting fix — the biggest solo performance fix so far, found by a player on the weakest hardware in the report pile.
Heard, still being worked on
- The hitch on NEXT while the next arena builds (13 September report) is still being measured — heard, not forgotten, not fixed yet, and I won't pretend otherwise.
- The "dug against ?" line in two report logs is a missing label in the log only — not a gameplay fault. Noted in 1.92.3's notes.
What happens next
Steam Next Fest runs to Oct 26. Early Access launches Oct 28 — $7.99, $4.79 for launch week (40% off). The demo stays free. Online multiplayer is in, and it is honestly an unproven beta — please don't buy for online alone.
Then Early Access does what this month just did, at full scale: you report, suggest and push, I fix, thank, and ship. Help me build the game you want.
— Timothy Bunce (AlluringCoffee)
Version 1.92.3, build 144, Windows and Linux.