Ever booted up a remaster only to watch it stutter like a cursed Witcher? That's the reality for some The Witcher 3 Remastered players on PC right now. The shiny new upgrade is here, but it's not all smooth sailing.
CD Projekt Red has been quick to respond. In a post on Twitter, the studio revealed it's identified the culprit behind some performance woes: NVIDIA Hairworks. Yes, the tech that makes Geralt's luscious locks flow so realistically is also tanking your framerate. "We've identified an issue related to NVIDIA Hairworks that may significantly affect performance," the devs wrote. Their temporary fix? "We recommend disabling that setting until this is addressed in a patch."
So if you're struggling to slay monsters at a decent FPS, try turning off that hair setting. It's not a permanent solution, but CDPR is clearly working on a proper patch. The team alludes to a future update that should sort things out on PC.
But wait—it's not just PC players feeling the pain. The comments on that same post show frustration from console users too. One top reply begs: "Please fix The Witcher 3 Remastered on base PS5. The performance is absolutely horrible right now." Others echo that sentiment, noting that even the performance mode isn't holding up. So CDPR might have more than one platform to worry about.
Despite these hiccups, the remaster is still a critical darling. It's currently the top-scoring game of 2026 on Metacritic, beating the original 2015 release by two points. Not bad for a game that's already a classic.
Of course, performance issues are never fun, especially when you just want to lose yourself in the Continent. But CDPR has a history of supporting its games post-launch, so expect fixes sooner rather than later. Who knows, the PC patch might even address console problems too.
For now, if you're on PC, disabling Hairworks is your best bet. And if you're on console, hang tight—help is likely on the way. Will you be waiting for the patch, or are you braving the stutters? Let us know in the comments!
Comments (0)
Log in to join the discussion
Log InNo comments yet