DF made a stress test video 6 days ago, patch 1.3. The results differ:
The swamp area is fine in the XB1 version, for the most part, taking into account what kind of test is that. I just hope patch 1.4 doesn't degrade the framerate.
The game seems to run at 30 fps like 90+% of the game -Novigrad could have spikces, but not so noticeable, the swamp isn't that ad either. I am in the 1.3 version of the game, I played yesterday night -XB1- and the patches apply automatically, am I missing anything?
Watch again, results are very similar than NX gamer's in the purely swamps area, but it's obviously not at the beginning of
their video.
From 1:10 to 1:48 the XB1 game never even reaches 30fps
once with a constant fluctuating framerate (from 25 to 29), capped 20fps on PS4 with fluctuations too, and again they only did a fast travel test, like if they wanted to stress test one version more, as fast as they could on the horse...They didn't stop to fight a few enemies like NX gamer and that's what you often do during quests and stuff.
But during those ~30 seconds the XB1 game runs at 30fps
0% of the time indeed, not 90%, similar to what NX gamer video showed.
Now analyse closely when they stop the horse and walk near the house (still in the middle of the swamp) from 1:51 to 2:02, it's the PS4 game that now reaches more often 30fps than the XB1 game...
Like what NX gamer video showed, when you are not fast traveling on your horse (walking, questing or fighting), in the swamps, the PS4 game reaches more consistently 30fps. And I suspect it's the same thing in the cities too, the streaming involved during fast traveling must be straining the framerate on PS4 more than on the XB1 version. It could be interesting to test the PS4 version with a SSD installed...Do we know what HDD DF use on their test machines?
We can see on the latest DF PS4 video 1.03 vs 1.04 (when the 2 versions are ideally synced), that the drops usually happen at the same exact moment which could be easily explained if those happen during the same streamed loading process. And what about those textures that need several seconds (an eternity in computing!) more to load on PS4 in some cases in the city compared to the XB1 game? A CPU bottleneck couldn't explain that kind of loading anomalies. Could it be because of the directX nature of this game that could explain those differences? Because those problems never happen in Sony first party games.