Nightingale

Nightingale wants to be the survival-crafting game where you build a house and tame the land in fantasy-Victorian England, ideally with a few friends along for the weekend, and two years after launch, it's gotten good at that part. The developers added charms that turn carry-weight limits into a strategy instead of a punishment, rebuilt entire starting realms for new players, and fixed enough of the early systems that longtime players now credit the studio with climbing out of "Mixed" review purgatory, a shift the numbers back up: the overall Steam rating sits at 70 percent, Mostly Positive, off ten thousand reviews, and that's not nothing.

The part that keeps costing them: it still runs like garbage on hardware that should have no trouble with it, with players on a 4070 reporting the same frame drops as players on a 1660 Ti. Lower the game's Lumen lighting setting to fix your frame rate and the shadows start flickering everywhere like a bad strobe light. A patch in March fixed a handful of crash bugs and connection timeouts, and cleared up a nasty bug that wiped progress on returning to the main menu, but it never touched the performance problem players have been posting about since the alpha.

That's the part I paid for and didn't get: I run a mid-range rig that handles everything else on my desktop without complaint, and Nightingale still stutters through basic outdoor exploration like it's rendering the world twice. Recent Steam reviews, the last thirty days of them, sit at 33 percent, Mostly Negative, and a two-year-old game with a rebuilt reputation is losing ground again, right now, over the same problem it launched with.

I want to like this game more than I do. The systems underneath are solid, and I'm not going to pretend two years of real work didn't happen. But a game that still can't hold a steady frame rate in year three has stopped being a rough launch. This is how the game runs now, and no amount of new content fixes a stutter.