Value of NXGamer technical investigation videos *spawn

It’s a recurring mistake. At 1:45, he says the PS4 Pro res is “double that [of the base PS4], and targets 2720x1530, which gives us a half resolution of 1360x765.” (Is the “half” res the min res that he pixel counted, and the “target” the max?) Unless this is A/V shorthand where all resolutions are quoted as vertical (not so useful with rendering as sometimes resolution is reduced on only one axis), he’s forgetting an axis and so off by a factor of two.

I’m a little unclear as to what’s happening with the res. He says the game “targets” the reconstructed res, the Pro (~1:58) “looking close enough to 4k on a 4k screen to never be offensive. Remember, this is resolving to that native target [1530p?] most often but at fast movement, camera cuts and the edge of screen, that’s when you can see this breakdown of it [765p?] resolving back in[to 1530p?].”

The PS5’s 120hz mode “likely scales at 1080p, which it’s most often at in action, then up to 3840x2160 with that reconstruction method when it’s at quieter sections.” I guess he’s using “resolving” and “scaling” interchangeably? Isn’t the game always reconstructing to 4k, no matter the native rendering resolution (from 1080p min to 2160p max)? ¯\_(ツ)_/¯

The PC footage is credited as captured by someone else. The repeated resolution goof makes me wonder if he’s viewing raw or compressed footage when he’s comparing with the presumably raw PS5 footage he’s capturing. PS5 may well look close enough as to be equivalent to PC 4k to the average gamer at TV distances and the IGN audience may be less discerning than other tech analysis outlets, but it’s sloppy.

He is a fast talker, but I’m more confused by his terminology. And my brain is working at half res today, but I set nitpick to ultra in my settings. :)

Edits: He does mention “half width and height” at 7:00. But then he shortly follows that with “pushing twice the amount of pixels” at ~7:30. I understand he’s probably under more time pressure than, say, DF, but why make a technical analysis narrated at breakneck speed more confusing than necessary?

If I can judge from a 4k YT video, I agree with his opinion that it’s hard to distinguish between PS5 “4k”60 and PC 4k max settings. The PS5 apparently made smart sacrifices to hit 60fps. Pity he didn’t have the time to qualify the “third of the framerate” by at least enabling DRS on the PC to see if that alone can bring the min up in that one scene. Was the PS5 rendering at 1080p there? Surely quartering the res could get the PC to 60. I’m sure if Alex’s does a recommended PC settings video we’ll find out.

11:40 The PS4 Pro “can get some streaming judder on the train section but it is loading a lot of detail and it is [pushing?] twice the pixel throughput of the PS4.” It’s asking a lot for me to realize that he means the PS4 Pro’s 1320x765 (base? min?) res is 2x the PS4’s 960x540 and assume they’re both bottoming out there in the five seconds it takes him to say that.

I watched the whole video and still can’t tell if the game always renders at his “half” resolutions or uses DRS. ~12:00 “The cutscene cinematics obviously again ramp up that resolution quality [?!], lowering the reconstruction to give you a sharper, cleaner image.” Sounds like DRS.

Maybe his FH5 perf analysis is easier to follow.
Don't forget the cost of reconstruction. Depending of methods it can be far from being free. We'll know more about the whole resolution subject with others analysis.
 
It’s a recurring mistake. At 1:45, he says the PS4 Pro res is “double that [of the base PS4], and targets 2720x1530, which gives us a half resolution of 1360x765.” (Is the “half” res the min res that he pixel counted, and the “target” the max?) Unless this is A/V shorthand where all resolutions are quoted as vertical (not so useful with rendering as sometimes resolution is reduced on only one axis), he’s forgetting an axis and so off by a factor of two.

I understood it as 1360x765 rendering reconstructed to 2720x1530 which is then upscaled by the console/tv to 4K. His repeated references to half/double resolution is probably just a mistake. People still get that math wrong.

The reconstructed visuals do look extremely close to the PC 4K version so I would agree with him that the result is very impressive. But that assumes the video is actually representative. It’s also a good thing to point out the diminishing returns of uber settings but the performance comparison was clumsy. If you weren’t paying attention you would get the impression that you have to run at native 4K with much lower performance on PC to match reconstructed PS5 visuals.
 
I dont want to get into it, esp since its a video which I dont like, I prefer text cause this way you're pretty sure they meant whats written unlike a video (do they ever go back and dub over misspeakings?)

I just will point out, the last COD from this developer

https://www.eurogamer.net/articles/...uty-world-war-2-ps4-pro-xbox-one-x-first-look
"It's early days here, but our impression is that WW2 employs dynamic resolution scaling on both systems, with the lower bounds set at 1920x2160, rising to a full-fat 3840x2160"

I assume the narrator misspoke (we often do call something 1/2 when its actually 1/4) I just want to point out that sometimes scaling is only used on one axis though I have no idea what they are doing in this game

Though personally the guy should be comparing like for like, i.e. if ps5 is 1920x1080 then the PC should be set to the same resolution
 
I understood it as 1360x765 rendering reconstructed to 2720x1530 which is then upscaled by the console/tv to 4K. His repeated references to half/double resolution is probably just a mistake. People still get that math wrong.
In general speech, I would expect 'half' to be more common than 'quarter' as it's easier to say, so the brain grabs the easiest way to talk about the difference which is a two-dimensional halving. That is, I don't think the maths is wrong at all, but the communication. Although to be fair, dimensional ratio is something often fumbled with, but that shouldn't be a problem for pixel-counters talking tech.

Perhaps worth those who watch the vids hitting NXGamer up and suggesting he use clearer terminology?
 
Anyway, Gamers Nexus findings on PS5 vs equal pc hardware.

if I remember correctly this Nexus video was realy absurd, testing games dynamic res vs 1080p and give conclusion ps5 gpu is gtx1060 level ;d
 
Last edited:
In general speech, I would expect 'half' to be more common than 'quarter' as it's easier to say, so the brain grabs the easiest way to talk about the difference which is a two-dimensional halving. That is, I don't think the maths is wrong at all, but the communication. Although to be fair, dimensional ratio is something often fumbled with, but that shouldn't be a problem for pixel-counters talking tech.

Perhaps worth those who watch the vids hitting NXGamer up and suggesting he use clearer terminology?
he literaly said half width half height and also there was written on screen resolution targets and internal resolution, quite clear for me
 
In general speech, I would expect 'half' to be more common than 'quarter' as it's easier to say, so the brain grabs the easiest way to talk about the difference which is a two-dimensional halving. That is, I don't think the maths is wrong at all, but the communication. Although to be fair, dimensional ratio is something often fumbled with, but that shouldn't be a problem for pixel-counters talking tech.

Perhaps worth those who watch the vids hitting NXGamer up and suggesting he use clearer terminology?
50% is also the common terminology in games with a resolution scale when you are really rendering 25% of the pixels. I always hated that.
 
This thread has turned in to a witch hunt for NXG.

NXG only has themselves to blame. If they didn't have such sloppy, inaccurate and amateurish video commentary then perhaps he could get across what he really means if it is indeed something other than what people are peceiving it as. And it's even plausible that some of the inaccuracy is due to the sloppiness of his commentary, but it still comes across as badly done if we're being generous.

Regards,
SB
 
NXG only has themselves to blame. If they didn't have such sloppy, inaccurate and amateurish video commentary then perhaps he could get across what he really means if it is indeed something other than what people are peceiving it as. And it's even plausible that some of the inaccuracy is due to the sloppiness of his commentary, but it still comes across as badly done if we're being generous.

Regards,
SB

Its no different to the Nexusgamer video where the findings are the 1060 is competing with the PS5 which actually is closer to a 2070 in non ray traced situations. And he got 'witchhunted' for it aswell. Theres stupid videos like these on each side of the platforms.
 
This thread has turned in to a witch hunt for NXG.
Your use of the term "witch hunt" is as sloppy as NXG's use of the term "half resolution." This is a technical forum discussing technical videos. The expectation is of correct and clear terminology, otherwise we're all just shooting opinions into the ether. I consider my criticism constructive, not malicious.

IGN is a more general audience, so while it's cool that NXG has a wider platform to discuss his findings, he makes a lot of assumptions of them. Is "reconstruction" a fixed cost per frame, regardless of source res? Does the game use DRS, or is it reconstructing the small font "half" resolution to the big font resolution? Is that reconstruction an intermediate step to the console then upscaling to a standard 1080p or 2160p res? IIRC, NXG said his framerate analysis was based on half an hour of capture. Was that half hour at what seemed like big stress points? Was it early game, populated MP servers? It's cool to know frame rates are pretty stable except for cutscenes, and that might be all that IGN expects, but I'd like more. Nitpicking doesn't mean I don't value his effort, but is it weird that it leaves me with more questions than answers? I could check if he's using a vernacular common to his prior work, check what previous CODs did technically, etc., but I'd rather he take an extra minute or two and explain it in the video. Maybe we're expecting too much from an IGN video, even if it's done by NXG. But it's weird that DF can get MS to give them Forza 5's console-equivalent settings for PC but an outlet like IGN can't get the same from the COD developer to put the 3090's performance in context.

I have no opinion on how biased he is for or against any particular console. Accusations of bias can reveal as much about the accuser as the accused (see: DF YT comments section).
 
NXG only has themselves to blame. If they didn't have such sloppy, inaccurate and amateurish video commentary then perhaps he could get across what he really means if it is indeed something other than what people are peceiving it as. And it's even plausible that some of the inaccuracy is due to the sloppiness of his commentary, but it still comes across as badly done if we're being generous.

Regards,
SB

Then make your own videos and show him how to do it properly.
 
Your use of the term "witch hunt" is as sloppy as NXG's use of the term "half resolution." This is a technical forum discussing technical videos. The expectation is of correct and clear terminology, otherwise we're all just shooting opinions into the ether. I consider my criticism constructive, not malicious.

There are comments in this thread that are nothing to do with his technical terminology misuse but pure witch hunt comments.

It's pretty clear, if people aren't happy with his video's

1. Don't watch them.
2. Contact NXG on Twitter and correct him.
3. Start their own YouTube channel and show him how it's done.

Talking about how he's wrong for X, Y and Z in this forum isn't going to help him improve.
 
There are comments in this thread that are nothing to do with his technical terminology misuse but pure witch hunt comments.

It's pretty clear, if people aren't happy with his video's

1. Don't watch them.
2. Contact NXG on Twitter and correct him.
3. Start their own YouTube channel and show him how it's done.

Talking about how he's wrong for X, Y and Z in this forum isn't going to help him improve.



"Start their own YouTube channel and show him how it's done."

I am not fully happy with how new Halo inifite looks but i will not start my own dev company and show them how its done ;)

"Talking about how he's wrong for X, Y and Z in this forum isn't going to help him improve"

Unless he visitis the forum and read what people have to say and what kind of feedback his videos get. Who knows maybe he is reading this forum.
Anyway if his videos are posted here there is nothing wrong to point out if he is wrong.
 
"Start their own YouTube channel and show him how it's done."

I am not fully happy with how new Halo inifite looks but i will not start my own dev company and show them how its done ;)

"Talking about how he's wrong for X, Y and Z in this forum isn't going to help him improve"

Unless he visitis the forum and read what people have to say and what kind of feedback his videos get. Who knows maybe he is reading this forum.
Anyway if his videos are posted here there is nothing wrong to point out if he is wrong.

But while some are pointing out his errors, others have basically used it as an excuse to bash his video without any form of constructive critism.
 
Back
Top