Since the release of Nightmares & Visions, we’ve been closely monitoring performance on our platforms. We’ve found in particular that XBOX Series S players are suffering from out of memory issues.
We’re in the process of doing an in-depth memory rundown to address this. In the meantime, we’ve put together a fix that should reduce the frequency of out of memory issues.
This fix will be a part of our Hotfix #65, scheduled for next Tuesday, 8 April.
I don’t know if it will solve the most serious problems at present
30 series graphics cards cannot enable frame generation mode, frame rate locked at 60 frames per second cannot be increased, and frame generation mods cannot be used
When switching between grenades, primary weapons, and secondary weapons, players will get stuck and unable to perform attack actions
The green light pillar of the ceremony will lock onto a player’s head and continuously illuminate it, making it impossible to see anything in a green area
The scope of ceremony generation is too large, even standing on the rooftop can trigger the ceremony to start downstairs
The ceremony will suddenly refresh within 30 meters of the player, with nothing in the first second and a row of enemies suddenly appearing the next second
It’s great that this is being addressed! That said, I cannot emphasize enough, if it’s anything other than “deranking was a dumb idea, our bad, we’ve removed it”, it’s probably just going to end up like Crafting again. Doubling and tripling down on the old crafting concept by giving just a bit of RNG mitigation through a couple iterations over two years didn’t help anything, the fundamental concept was inherently bad, it just kept the reviews negative and the perception of the game bleeding. If the deranking system is kept with some minor changes, I would expect the same player reaction. Don’t let Havoc deranking be Crafting 2.0!
Derank being removed from Havoc addresses like 90% of the problems with the mode in one fell swoop. It was always an unforced error on Fatshark’s part. Fingers crossed that they go all in and just remove it wholesale. I don’t want it tweaked; I want it gone.
And please don’t come out with something like “Takes time to adjust” or some other empty platitude.
The code for the previous version didn’t magically cease to exist. Rolling back is always an option to immediately alleviate the issue while working on a proper solution.