• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

[DF] - The Division 2: Next-Gen Runs at 60FPS - Visual Analysis on PS5 - Series X|S




The title is actually "what's up with PS5 visuals?" but I changed it since the Hitman 3 analysis title wasn't popular.

Next-gen support lands for The Division 2. Its latest update 1.21 lets PS5, Xbox Series X and S all run at 60fps, though there are some curious side-effects on Sony's latest machine. Even compared to PS4 Pro it's bizarrely missing screen-space reflections and volumetric fog. Tom and Alex dissect the update to talk on the state of the game on all platforms.

Summary incoming:

- Game is running in BC mode, or as Tom calls it "BC+ mode"
- Notable downgrades to PS5 version compared to PS4 Pro, missing fog and other effects
- Series S targets 60fps/1080p (dynamic)
- Series X targets 60fps/4k, as high as native 4k, drops as low as 1800p
- PS5 reconstructs to 4k from a max resolution of 1890p, lowest res they counted was 1080p
- Series X takes lead with better BC enhancements
- Newer consoles have better texture pop-in
- Tom hopes the missing effects on PS5 is a bug that will be addressed, Alex surprised this patch even made it out the door in current state
- Black levels are crushed on PS5 version (around 8:20 mark)
- Reflections not working properly on PS5, flat out missing in some areas, Alex says it is definitely a bug that needs to be addressed
- PS5 holds 60 fps very well, Tom did notice one instance of screen tearing around the 12:15 mark that wasn't duplicated on Series X
- Series X holds 60 well but has more slight dips than PS5 probably due to higher settings
- PS5 version clearly not tapping into the increased I/O bandwidth

Sounds like a crappy patch. Hope it gets fixed

Loading Times:

xRdji22.png


EDIT

Framerate stats from VG Tech, who also counted the same resolutions as DF does and notes the same missing effects on PS5 version.

PlatformsPS5Xbox Series XXbox Series S
Frame Amounts
Game Frames205102046820492
Video Frames205102051020510
Frame Tearing Statistics
Total Torn Frames000
Lowest Torn Line---
Frame Height216021601080
Frame Time Statistics
Mean Frame Time16.67ms16.7ms16.68ms
Median Frame Time16.67ms16.67ms16.67ms
Maximum Frame Time16.67ms33.33ms33.33ms
Minimum Frame Time16.67ms16.67ms16.67ms
95th Percentile Frame Time16.67ms16.67ms16.67ms
99th Percentile Frame Time16.67ms16.67ms16.67ms
Frame Rate Statistics
Mean Frame Rate60fps59.88fps59.95fps
Median Frame Rate60fps60fps60fps
Maximum Frame Rate60fps60fps60fps
Minimum Frame Rate60fps50fps57fps
5th Percentile Frame Rate60fps60fps60fps
1st Percentile Frame Rate60fps57fps59fps
Frame Time Counts
16.67ms20510 (100%)20426 (99.79%)20474 (99.91%)
33.33ms0 (0%)42 (0.21%)18 (0.09%)
Other
Dropped Frames000
Runt Frames000
Runt Frame Thresholds20 rows20 rows20 rows

----------------------------------------------------

EDIT 2

Ubisoft said that they are aware of issues on PS5


From Ubi forum:

xPFhOmI.png


---------------------------------------------

EDIT Feb 23

DF analyzed the updated patch on PS5 today



Division 2 Updated:
- SSR and Volumetric fog are back after the initial upgrade broke them, now these are on same level as Series X
- Load times are similar to before. In original update PS5 loaded in 16 seconds, in this patch PS5 loads in 15 seconds. Series X loads in about 6 seconds
- PS5 renders at 1080p (lowest) to 1800p (highest)
- PS5 still has framerate advantage over Series X, albeit at lower resolution (on average)
- He had an issue with screen tearing and FPS dips to 40s in one fight, but restarting the PS5 fixed it
 
Last edited:
I don't understand why if a game is buggy on ps5 they speak quite ill of it, yet if xbox has the same issue with another game it's instantly classed as a bug or they sugar coat it with vrr talk and they tend to contact the developer or whatever.
Well I don't understand why you are making things up but you are. They more than likely have told the developer of the problems, Alex said it shouldn't have been released on PS5 because its a rush job.
 

Traxtech

Member
Well I don't understand why you are making things up but you are. They more than likely have told the developer of the problems, Alex said it shouldn't have been released on PS5 because its a rush job.
I'm talking about how they go about talking about the situation and advertising their videos.
 

Zathalus

Member
I don't understand why if a game is buggy on ps5 they speak quite ill of it, yet if xbox has the same issue with another game it's instantly classed as a bug or they sugar coat it with vrr talk and they tend to contact the developer or whatever.

And people say DF aren't bias.
Did either of you watch the video? The only mention this is a bug like 3 or 4 times. They even outright state that the PS5 is capable of so much more.
 

Kuranghi

Member
Please say this black crush/gamma issues trend we are seeing on PS5 versions of PS4 games (Seen in Control:UE and now this) isn't just some stupid mismatch of HDR being on in the PS5 settings and off in the game when they test it. It sounds stupid

I don't think so just yet since this game actually has HDR, unlike Control:UE, but HDR seems to lead to the biggest amount of dev-confusion I've seen with a graphics "effect" so far. Control looks like it should in SDR mode, when you enable HDR in the system settings the big bright lights in the game are brighter but without no extra detail in them and the shadows are elevated in cutscenes especially. If you want the same bright lights but keep the proper shadow levels just max out the backlight/brightness on your TV and leave the PS5 in SDR (Depending on your TV this might look like shit so ymmv).

Why the hell can't Sony just have a checkbox to detect whether any game you run is outputting SDR or HDR and disable the HDR system setting if its outputting SDR. Its not like the game needs to be restarted when you do that anyway, it can be done while its running.
 
Top Bottom