Skip to content
Nivalis Nights Wiki

Troubleshooting

Bugs, and what the developer says about them

Performance complaints are not bugs and are covered elsewhere. This page is the smaller thread underneath it: what actually breaks, and how the publisher is answering.

Reports across these threads
130
Threads
3
Mirror snapshot
2026-09-30T05:52:19Z

What this page is not

It is not a list of everything players dislike. Frame rate dominates that list and has its own pages at /dlss-fsr and /performance, because it is the one problem where the answer is structural rather than a bug to report.

What is here is the remainder: crashes, objects that do nothing when you interact with them, lost progress, and the developer response to all of it. It is a short list, and the mirror supports a short list.

Crashes and soft-locks

43 of 1,119 written reviews (3.8%)

Does the game crash, and does it lose your progress?

Crashes are reported, and the pattern is early: first launch, and the first session. The save-loss complaint is the serious one — at least one reviewer says they now save manually before every session specifically so a crash does not cost them progress.

Limit: Self-reported, and every reviewer is describing their own machine. No crash rate is derivable from this.

“no obvious problems with the frame rate, but when I tried to go to the docks in a taxi the game crashed and I lost all progress since the last manual save, which was the entire Day 2. I repeated all the stuff I did since the save, went to travel again and it c”

Steam review #236511850 · english

Non-functional objects

26 of 1,119 written reviews — reported as a pattern, not measured

Anything that does not work when interacted with?

Yes, and in small ways: a bed that will not let you get up, refrigerators with no function. These are the kind of report that is easy to fix and easy to miss, and they are the clearest sign that a launch build shipped before every system was finished.

Limit: One or two reports each. Named here because they are specific, not because they are common.

No review in the mirror meets the bar for quoting here.

The developer response

61 of 1,119 written reviews — reported as a pattern, not measured

What are developers saying to players?

Several reviewers report that performance reports receive a canned reply suggesting the player change their system settings or restart the game. Two describe it as a copy-paste response. This is the most-cited frustration in the corpus that is not about frame rate, and it is why several of those reviewers say they will revisit their review after a patch.

Limit: Reported second-hand, by players, about replies on Steam. This page has not verified the replies themselves, and the mirror does not contain them.

“I saw a dude with rtx 5090 complaining about performance and the devs responded with "have u tried restarting your pc? lmao wtf”

Steam review #236484187 · english

What to do about it

  • Save before long sessions. This is the one piece of advice the corpus converges on independently, and it is advice the game should not have to earn.
  • Expect the first session to be the rough one. Launch crashes cluster early in several reports.
  • Re-read the store page's recommended VRAM before buying. Not a bug, but it is the difference between a smooth run and a refund.
  • Watch for a patch before deciding. The mirror is a first-week snapshot. Several negative reviewers say explicitly that they would change their rating if a patch landed — so the sentiment here is a snapshot, not a verdict.

Drawn from 1,119 written reviews in the mirror, fetched 2026-09-30T05:52:19Z (0 days ago). 2 of 3 threads carry a quotable review.