@UnnDunn: Lol Nope just like the use of photomode as an valid alternative benchmark when XSX's performs worse than PS5's in real time graphics (it must be a bug), 1+1=2. There's more to GPU power than just TFLOPs, you know like how a Radeon VII's performs worse in GPU bound scenarios despite a higher TFLOPs than 2080Ti
@regnaston Control is pretty much a GPU bound game in real time game, and every fps dip involves heavy Alpha effects (GPU based) this the whole isolating the GPU via photomode is BS lol
I agree with @davillain-. You have got to be trolling.
@Zero_epyon: lol everything is already rendered with a bit of polish that's not done real time game and paused. There's nothing more to it you know 1+1=2.
@Zero_epyon: lol everything is already rendered with a bit of polish that's not done real time game and paused. There's nothing more to it you know 1+1=2.
So you think when the game is paused, the game renders one frame and just repeats it over and over until the game is unpaused?
Why do you think that photo mode is the same as pausing the game?
@Zero_epyon: lol everything is already rendered with a bit of polish that's not done real time game and paused. There's nothing more to it you know 1+1=2.
Your comment proves that ignorance has no limits. 😎
@Zero_epyon: Sucker Punch has it's own implementation (like add extra fancy effects isolated from real time game rendering) that's different than Control's (which is effectively pausing a game).
@Zero_epyon: Sucker Punch has it's own implementation (like add extra fancy effects isolated from real time game rendering) that's different than Control's (which is effectively pausing a game).
How is it different? How does a game pause but also allow you to move the camera around?
@Zero_epyon: It's different by allowing effects (like Weather/Lighting/etc) outside of gameplay, otherwise there not much difference lol?. All rendering associated with gameplay interaction is simply halted.
@Zero_epyon: It's different by allowing effects (like Weather/Lighting/etc) outside of gameplay, otherwise there not much difference lol?. All rendering associated with gameplay interaction is simply halted.
I have to say, it's pretty sad that the PS5 can't even display a pre-rendered still-frame image with non-real-time once-ray-traced lighting at more than about 40fps. Can't imagine how much it would struggle to actually render the image :-p
I have to say, it's pretty sad that the PS5 can't even display a pre-rendered still-frame image with non-real-time once-ray-traced lighting at more than about 40fps. Can't imagine how much it would struggle to actually render the image :-p
TRUE
If it only a still image as whatever his name is saying and it is having problems hitting 40fps then the PS5 is doomed 😁
@Zero_epyon: Yes a 3D still image that was already rendered (whose assets don't have to be rerendered from scratch), in context of 3D the only thing the camera does is projecting or "rendering" the view to the user while being decoupled from the environment.
Real-time 3D gameplay involves user interacting (which is what give's it the "3D" aspect, otherwise it's nothing more than a 2D projection/illusion of a 3D object) with the environment, and environment/assets moving relative to the user (vice versa), you know like light bouncing off the user/environment, particles moving and colliding, etc. All of which have to be rerendered on the fly from scratch on frame-by-frame ( All of which stresses the entire GPU pipeline).
@Zero_epyon: Yes a 3D still image that was already rendered (whose assets don't have to be rerendered from scratch), in context of 3D the only thing the camera does is projecting or "rendering" the view to the user while being decoupled from the environment.
Real-time 3D gameplay involves user interacting (which is what give's it the "3D" aspect, otherwise it's nothing more than a 2D projection/illusion of a 3D object) with the environment, and environment/assets moving relative to the user (vice versa), you know like light bouncing off the user/environment, particles moving and colliding, etc. All of which have to be rerendered on the fly from scratch on frame-by-frame ( All of which stresses the entire GPU pipeline).
Don't mind me. I'm just quoting this to capture the cluelessness and insanity of this post. 🤣
@Zero_epyon: Yes a 3D still image that was already rendered (whose assets don't have to be rerendered from scratch), in context of 3D the only thing the camera does is projecting or "rendering" the view to the user while being decoupled from the environment.
Real-time 3D gameplay involves user interacting (which is what give's it the "3D" aspect, otherwise it's nothing more than a 2D projection/illusion of a 3D object) with the environment, and environment/assets moving relative to the user (vice versa), you know like light bouncing off the user/environment, particles moving and colliding, etc. All of which have to be rerendered on the fly from scratch on frame-by-frame ( All of which stresses the entire GPU pipeline).
Log in to comment