Quick Answer: Nightmare Frontier's 1.0 launch (July 22, 2026, version 1.0.0.1607) came with one headline technical issue: a purple screen / missing-textures bug on starting a new game, reported across NVIDIA, AMD and Steam Deck within hours — the developer is actively collecting logs, and two partial workarounds exist (switch resolution, or set Decal mode → DBuffer). Beyond that: your Early Access save is gone by design (wipe at 1.0, old build available for rollback), the scary "unsaved progress" quit dialog is misleading — the game autosaves every combat turn, one story softlock has been reported (the Slums transmitter), and the community's longest-running complaints — performance and the ad launcher — carried over from EA. Status below as of July 23, 2026.
The "Game Saved" toast mid-raid: the game really does autosave constantly — the quit dialog just doesn't admit it. (Screenshot: Ice Code Games)
Purple Screen / Missing Textures on New Game (Launch Bug, Developer Investigating)
Symptom: starting a new game loads into a purple, textureless void — "no texture, only purple shade everywhere." Reported within hours of the 1.0 launch by multiple players on distinct hardware: an RTX 3060 Ti (Windows, D3D11, ultrawide fullscreen), an RX 6800 XT, and a Steam Deck.
Developer response (same day): it's being treated as a graphics-related issue; affected players are asked to email their graphics card model and the Player.log file from %USERPROFILE%\AppData\LocalLow\Ice Code Games\NightmareFrontier\Player.log to [email protected].
Workarounds so far (both partial, from the same thread):
- Switch to another resolution — this fixed it for the RTX 3060 Ti reporter (who was on 3440x1440 exclusive fullscreen). It did not work on Steam Deck.
- Set Decal mode → DBuffer in the graphics settings — suggested in-thread; unconfirmed as a general fix.
If neither works, send the log — this is the bug the developer is most actively chasing at launch.
Your Early Access Save Doesn't Work (By Design)
The 1.0 patch notes lead with it: beta saves were wiped for the release. Old EA saves won't load in 1.0. The developers are keeping the old Early Access build active "for a little while" so you can roll back (via the Steam betas branch) and finish an in-flight EA run — but plan on 1.0 being a fresh start. Not a bug, and no workaround beyond the rollback.
"Unsaved Progress Will Be Lost" — Misleading, Not True
The most-viewed quality-of-life thread at launch asked for mid-mission saving. The studio's answer in that thread: the game already autosaves at the start of every combat turn — you can quit partway through a raid and resume where you left off. If a run doesn't pick up where you left it, that's a bug they've asked to have reported with details.
The quit dialog still warns that unsaved progress will be lost, which is what misleads people — the reporter in that thread had been finishing runs in one sitting for fear of losing them. Until the dialog is reworded: trust the autosave, and note the "Game Saved" toast that appears in raids.
Slums Transmitter Softlock (Single Report)
Symptom: in the Slums transmitter story mission, after killing the enemy wave the "restart the transmitter" action never reappears — quitting to menu and continuing didn't help, and the player had to abandon the run.
Status: one report, July 22, no reply yet. Worth knowing because 1.0 specifically reworked this mission (fewer and easier enemy spawns in both stages, per the patch notes) — so the mission is on the developers' radar even if this softlock isn't confirmed yet. The autosave system limits the damage to the current run. If it hits you, a forum report with your version number is the fastest path to confirmation.
Performance & Heat (Ongoing, Pre-1.0 Complaint)
The most consistent criticism across the review history, not new at 1.0:
- GPU load/temperature complaints — multiple reviews report cards running unusually hot for the visual load (one RX 590 owner: 70-90°C against 40-60°C in other games; another review: "shouldn't stress my GPU this much").
- A stuck bright-light bug after explosions — one EA review describes bright yellow light streaming across the screen after bombs explode and not going away.
- Steam Deck: long loading times, flagged even in otherwise positive reviews.
Status: no player-side fix confirmed for any of these. Settings reduction is the only current lever. Optimization is a standing community ask; nothing specific appears in the 1.0 patch notes about it.
The Launcher (Not a Bug, but Asked Constantly)
The game launches through a launcher that shows ads for other games before the play button — added during EA, and the single most-complained-about non-gameplay decision in reviews ("its only purpose is presenting you ads"). There is no in-game toggle. We haven't verified any bypass method, so we won't recommend one — just know the launcher is expected behavior, not a broken install.
Known 1.0 Oddities (Cosmetic)
- Gambler class was removed at 1.0, but some Gunslingers still display the Gambler's 3D model — patch notes acknowledge this; cosmetic only.
- The 1.0 notes fixed several EA-era issues worth knowing were real: NullReference errors after winning combats, and Jar of Essence / Plague Mask III abilities failing to clear Bleeding.
FAQ
Is there an official known-issues list? The pinned "Known Issues" thread on the Steam forum dates from Early Access (May 2025) and predates 1.0 — treat this page and the launch-week threads as more current until the developers refresh it.
The AI art controversy — is that a bug topic? No, it's a disclosure: the store page notes AI-assisted assets and the developers have discussed it on the forums. We cover it in the hub FAQ since it's a buying-decision question, not a technical one.
My problem isn't listed. The developers answer forum threads fast — same-day replies on launch day, including log-collection instructions. Post in the Steam discussions with your game version (1.0.0.1607 at writing), OS and graphics card; for crashes and visual bugs, attach the Player.log from the path above.
Sources: the official 1.0 patch notes (1.0.0.1607), launch-day forum threads (purple screen with developer replies, transmitter softlock, save-behavior thread with the studio's response), and Steam review history for the performance and launcher complaints. Single reports are labeled as such. Compiled July 23, 2026 — we re-check daily during the launch window.