Traffic Architect White Map, Black Screen and Graphics Crashes

Separate a blank-map failure from ordinary congestion

The original player describes a short freeze followed by white terrain, or black ground, with the UI still visible. Their posted log identifies Traffic Architect Demo 1.0.8 build a67e5777, Windows and a GTX 750 Ti. That is a source player’s configuration, not a requirement, a diagnosis for your GPU or this site’s test.

A district overload or No Route Available warning has a different investigation. If the map still renders normally and the problem is a building’s destination, follow route checks.

Try the bounded setting check and record the outcome

1. Record the edition and displayed build before applying advice from another release.
2. The developer suggests Settings → Graphics Quality → Medium or Low for the reported Demo case. Compare whether the same blank-map failure still occurs.
3. Note whether the failure appears immediately or after traffic builds, and whether it happens in windowed and fullscreen play.
4. If you can reproduce it with Windows Task Manager’s Performance → GPU view open, record GPU usage or VRAM behavior just before the freeze, as requested in the thread.

Low settings are not a guaranteed fix. The original player says Low still failed. The developer’s later reply distinguishes an actual GPU-process crash from the game merely struggling with a demanding scene.

Collect the documented Windows Demo log

For the Windows Demo in that discussion, press Win+R, enter %appdata%\TrafficArchitectDemo\logs, and open the folder. The developer asks for game.log and game.old.log if present.

Include the GPU model, driver details, whether the machine is a laptop with integrated and dedicated GPUs, and the exact error. In the reported log, GPU process gone and CONTEXT_LOST_WEBGL identify the failure path; the earlier ResizeObserver message alone is not established as its cause. This source does not establish the full game’s log-folder path, so do not assume the Demo directory contains a full-release session.

Interpret the current version correctly

The full 1.1.0 notes say a graphics-driver crash now produces an explanatory message instead of a blank map. A later player in the thread reports seeing a graphics crash error, and the developer asks for specifications. A clearer message is not evidence that every driver crash was repaired.

The developer asks the original player whether the GPU gets hot or throttles and whether other 3D programs show similar crashes. Those are diagnostic questions, not proof of a faulty card or a reason to buy replacement hardware. Send the actual log and conditions through the original support discussion if the problem persists.

You have either stopped the reproducible failure with a documented setting change, or assembled the exact edition/build, graphics settings, GPU details, error and matching log for support. An unresolved crash remains unresolved; a working UI or a clearer message alone is not recovery.