@dynamitecop said:
@dakur said:
@dynamitecop said:
@Epak_ said:
It doesn't, probably just makes it more stable. Probably won't even fix the frame pacing. I'm excited for it, but remain skeptical since I don't want to be disappointed.
It doesn't, frame pacing is an issue caused by improper coding, that can only be fixed by altering the game code.
@dynamitecop said:
They assert absolutes before a situation has drawn itself to its conclusion, something only stupid people do.
I'm just quoting you here from a post you recently made in another thread bashing others for making statements before they have all the information and facts at hand, something you clearly do here by asserting that it won't be fixed as an absolute. So I just want to make it evident that you're a hypocrite who constantly does what you accuse others of doing. You constantly try to pass your poorly informed opinion as facts. Furthermore you also called yourself stupid...
But anyways frame pacing can have multiple causes, some of them can be fixed by more powerful hardware that can render some heavy frames quicker so it's still possible that this could be better in Bloodborne.
I have all the information, I know what frame pacing is, why it exists, how it functions and the reality that it's a problem with game code itself. This isn't an issue spawned of multiple GPU's where microstutter is present due to incorrect GPU sync and can be corrected at a system level by drivers. Bloodborne holds its 30 FPS at nearly all times even on the base PlayStation 4, throwing more power at it cannot correct frames that are drawing at inconsistent intervals from within the renderer, it's a rendering issue, an issue in the internal coding of the game, this won't do anything for that, the game needs to be updated.
No you don't know shit. Whatever Sony does for this "boost" could help faster rendering by the GPU of the individual GPU which will cut their rendering time and allow for more fluidity. That can happen to single individual cards and not necessarily with mutiple GPUs. And that has nothing to do with how a game is programmed, it could be a driver issue that is fixed or tampered with. Stop talking about what you clearly don't know anything about as if you did because you're frankly pathetic and in your own words "something only stupid people do".
Here is a pretty lengthy and good explanation about frame pacing from an expert and what it is so that you can educate yourself for next time and maybe you could stop talking out of your ass for once in your life.
http://techreport.com/review/21516/inside-the-second-a-new-look-at-game-benchmarking/
Page 1
"GPU 1 is obviously the faster solution in most respects. Generally, its frame times are in the teens, and that would usually add up to an average of about 60 FPS. GPU 2 is slower, with frame times consistently around 30 milliseconds.
However, GPU 1 has a problem running this game. Let's say it's a texture upload problem caused by poor memory management in the video drivers, although it could be just about ANYTHING, including a hardware issue. The result of the problem is that GPU 1 gets stuck when attempting to render one of the frames—really stuck, to the tune of a nearly half-second delay. If you were playing a game on this card and ran into this issue, it would be a huge show-stopper. If it happened often, the game would be essentially unplayable."
Page 3
"In fact, have a look at the two frame times following the 58 ms delay; they're very low. That's likely because the video card is using triple buffering, so the rendering of those two later frames wasn't blocked by the wait for the one before them. Crazily enough, if you consider just those three frames together, the average frame time is 23 ms. Yet that 58 ms frame happened, and it potentially interrupted the flow of the game."
Notice my highlight of the word anything. This guy, an expert in the subject, is telling people that bad fps pacing could be caused by anything. And here you are telling us that it can be only about the game's coding. Not only are you extremely arrogant but also extremely stupid to think that you know things without actually knowing them. In fact the expert spends most of his time analyzing GPUs and how their pacing on different games work. If the problem of those games were coding then they would have the same problem on every GPU yet on ones there's an issue and on others don't because the issues he examines have not to do with the game coding. And yet you try to isolate that as the only possible issue.
At least read the article before you make your next dumb and uninformed post you bozo.
Log in to comment