http://dbd.game/killswitch
60 FPS on Last-Gen Console
Comments
-
HUH WHAT?
0 -
Confirmed on Q&A stream, the dream survives.
2 -
Insert ghostface helping blight meme here
1 -
So the 2018 Optimization Update is actually real
0 -
Wait, what!? Could someone please give me a lowdown because I legit can't sit through an entire q&a stream of anything. If it means what I think it means.... 👀
0 -
Yes.
0 -
Look I dream for the day that my console can finally play this video game at more than 15 fps
3 -
your the 🐐 of the forums
0 -
"Said on Q&A stream" is not "confirmed", we all know how the devs love to go back on their promises.
6 -
Correct, but now I have two instances of them saying something about it.
8 -
And it only took them 3 years to address it!
4 -
Yes
1 -
I don’t trust Bhvr
i will only believe it when I see it
6 -
Like some of us have been saying, the GPU can handle it, it's all their old spaghetti code doing unnecessary garbage in the background that screws things up.
5 -
Yeah they just said it.
Programmers working on CPU Load and reduced it a bit. If this is true, this is good.
0 -
In order to get 60 fps on last gen consoles/low end pc's they have to get the response time for cpu/gpu below 16ms. GPU is already below that threshold, so they have been converting old blueprint code to c++ to lighten the load for the cpu from 27ms to 22ms and its still ongoing.
2 -
And that's almost three instances.
0 -
If they keep working on stuff like that i think this is a good thing.
0 -
If by teardown you mean an entirely too long explanation, sure.
So back in 2019, we posted a roadmap to 60 FPS on console. Needless to say, this didn't end up happening. We were a little too ambitious and didn't manage it by the ETA we gave. That said, it's still ongoing.
Simply put, to hit 60 FPS on consoles, the frame time for both the GPU and CPU need to be below 16ms (16ms is one second divided by 60). The good news? On the GPU side, we're already there. But the CPU side is going to take more work to accomplish. In 2021, we started the year with ~27ms on the CPU side of things. By December 2021, that number went down to ~22ms.
This year, we're continuing our work on getting that number below 16ms. There's some things in this next update to help (The Nurse, skill checks), but we'll also be doing other things in the near future like reducing how often things tick when they're far away or off screen. These sorts of things take time to change as they can have knock-on effects in other places if we're not careful. For example, changing it so something doesn't animate if it's off screen might break a sound cue that normally plays when an animation starts.
All this to say the 60 FPS dream is not dead. There's no ETA for when we'll hit the goal, but things should get smoother as time goes on.
(On a related note, the reason why we don't do a "low graphics settings" mode for consoles to increase the FPS is because these settings almost entirely affect the GPU load, not the CPU load, so you'd still be bottlenecked and it would have no impact on performance. I know you didn't ask that, but I'm adding it anyway because we mentioned it in the stream.)
p.s. Credit to @Pulsar for bringing it back up.
Post edited by Peanits on20 -
My Crusade is nearly finished.
But I cannot rest until I see those frames arrive.
6 -
I feel bad for them in a way, those consoles tech is ancient, their cpus are trash
I would love to see a next gen only, unreal 5 dbd
0 -
The game literally came out 3 years after the Console's did.
0 -
Heh, you are lucky.
At least your cause might see the light of day.
1 -
It’s all thanks to you :) ❤️
5 -
from the stream I got that parts of their code is not in C++ (fast machine code) but in a script language (slow virtual code) which of course will make the game slow on older consoles because a "virtual cpu" is executing the code and not the real console cpu. They also mentioned Async loading (multiple things at once) which means they are using regular sync loading at this moment (only 1 thing at once, the 2nd starts when the 1st ends).
the next big challenge is maintaining the c++ code when new things are added. so good luck to the ones on old consoles.
0 -
LETS #########
GOOOOOOOOOOOOOOOO
0 -
On a similar note I wonder if 120 fps on new gen will ever happen
0 -
60fps for last gen will come when the next gen consoles come out.
2 -
And Xbox1x's came out in 2018 as well, plenty beefy enough for this game with tweeked coding.
Also, thank you @Pulsar for continuing to beat this drum! :)
0 -
True.
Why dont they just set a dynamic resolution and make it go as low as it needs to, to hit 60fps?
0 -
It was cool to hear that you actually were/are going ahead with the Blueprint -> C++ rewrite of (parts of) the basecode!
With regards to this part specifically:
(On a related note, the reason why we don't do a "low graphics settings" mode for consoles to increase the FPS is because these settings almost entirely affect the GPU load, not the CPU load, so you'd still be bottlenecked and it would have no impact on performance. I know you didn't ask that, but I'm adding it anyway because we mentioned it in the stream.)
I want to say that very basic testing of mine disagrees with this: Switching between the low and ultra graphics modes, I get about a 10% difference in average CPU load as per Windows resource monitor, and this is exacerbated whenever more is going on in the game.
You of course have likely tested this more extensively and also with regards to the respective console platforms specifically, but I still want to bring it up to discussion again. For one thing, even if rendering times are already below the 16ms target on last-gen GPUs and even if graphics settings don't affect their CPU loads at all, they might still benefit from a low graphics mode due to it potentially increasing the frame stability (combating stuttering) and preventing frame drops in particularly eventful game scenarios, where those GPUs might in fact not be capable of hitting that target. For another it can be argued that a low graphics mode would only be fair for console players to have, since it might provide some advantages (such as less visual clutter/noise) that the PC players they are now playing with and against as opposed to them can benefit from. Some people might also simply prefer the look of the game at lower graphics settings. A low graphics option on consoles would further allow you to hit the 16ms target without having to make too many compromises on the visual niceties of the game, since you could call it the "60fps mode". I assume most of those compromises must have already been made for the goals to have been achieved on the GPU side of things, but I suppose this could enable you to undo them.
With regards to PC platforms, I want to suggest that you implement exclusive fullscreen mode and distinct resolution settings in the in-game menu, as well as the ability to adjust VSync and the framerate cap. The game runs much better in exclusive fullscreen than windowed fullscreen, and being able to set distinct resolutions allows players to achieve better performance much more easily than the up-scaling technique of the current slider does. VSync and framerates are obvious further settings to be able to adjust (and VSync will actually start to be a relevant setting with exclusive fullscreen mode, as opposed to windowed fullscreen mode where desktop compositing already prevents tearing in the game).
2 -
Gotta wait for another 3 years, no worries it will be here soon.
0 -
Last gen consoles should be allowed to select low settings at the very least, runs like ass at the moment.
0 -
Why am I sensing another 100 page thread?
1 -
This member of the PC Master Race supports the console peasants in their Crusade for 60 FPS.
May the framerate be ever in your favor.
0 -
BHVR moments™
game doesn't work on major platform ಠ_ಠ
don’t worry all, we’ll fix it! (ﾉ◕ヮ◕)ﾉ*:･ﾟ✧
almost 4 years later ლ(ಠ益ಠლ)
don’t worry all, we’ll still fix it! ¯\_(ツ)_/¯
0 -
Just commenting so I can look back on this post when it finally happens. Let the day count begin...
0
