How to fix frame stuttering?

[Garf]

i have just bought dead by daylight and i have played it many time on free weekends and their was no problem but now that i playing it now i have been getting very severe frame stuttering and it happens and the worst times such as when chasing a survior and etc. I have tried everything such as lower setting custom low settings turing v sync off i don't know whys its still stuttering i have a good pc with good framerate on 90% of my games and in the tutioral i have no stuttering at all and also in the free weekends when i played so i have no idea what's wrong so please help me

[Shirei]

Unless you have some overheating/driver issue there is no way to fix. You will get frame drop as a killer when:
-Frenzy
-Hitting survival
-destroying palette
- doing 360 (you can detect survivor by this)

[Moorish]

https://www.youtube.com/watch?v=RoPOiaSLXms

Thank me later.

[Old Habits Die Hard]

Originally posted by Steve-e-wonder:

https://www.youtube.com/watch?v=RoPOiaSLXms

Thank me later.

Thank you for what? A link to a video that doesn't work at all written by someone that's either very dumb or outright lying for views?

Please stop sharing this nonsense guide, I'll happily thank you to do that!

Like every other DBD guide out there making the same claims, this doesn't work because it can't and this is why:

1. When this game, as well as 99.9% of all games, starts up it reads the contents of the defined ini files and writes them into a live working copy that it creates and only uses while the game is running that only it can access. Any properties or parameters of those properties that are either invalid or not allowed that it encounters it simply uses the preset defaults in its live working file.

2. Changing the FullScreenMode parameter =0 in GameUserSettings.ini does exactly the same as setting the -fullscreen startup switch does, which is that it sets (writes) FullScreenMode=0 in GameUserSettings.ini, so using them together would be pointless. Using them together wouldn't cancel each out one of many clear signs whoever came up with this idea doesn't understand what he's even suggesting.

3. This game is designed specifically to only run in either Borderless fullscreen windowed mode (FullScreenMode=1) or windowed mode (FullScreenMode=2) and as such will not run in Exclusive True Fullscreen mode (FullScreenMode=0) so as I mentioned in point #1 it does exactly the same thing that it will do anytime it is given an invalid parameter for one of it's properties which is it will use the default for that line. When this happens the change is normally reflected in GameUserSettings.ini because it automatically updates the parameter that it is actually using to that file. This is an easy way to find out which properties and/or parameters you're allowed to use because if you're using an allowed parameter the game will not change it back.

For example bUseVSync= has two valid allowed parameters, True or False, with it's default being True. So if we change it manually from default to False then run the game when you check GameUserSettings.ini you'll notice it will still be set to False. Had you used an invalid or parameter that isn't allowed it such as bUseVSync=WOOOHOOO would have used its default of True and would have written this isn't that line in GameUserSettings.ini. This is why so many think that setting "read only" overcomes this, which is doesn't and I'll cover next.

4. Setting Read Only on a file simply stops a file from being overwritten and that's it. Comically enough this defeats the point of using -fullscreen, but anyway it cannot force the game to use the contents of GameUserSettings.ini. This should be a gigantic red flag the guide is written by someone that is clueless because this a trivial thing to understand and also to prove. You can fill up your GameUserSettings.ini with random gibberish or leave it blank, then set "Read only" and start the game, you'll notice it starts up using all defaults. If it was actually being "forced" to use the contents the game would certainly not run. Using "Read only" not only doesn't do what they claim it will do, it can also create other issues so it should not be used, ever.

[Ackranome]

^ are you trying to tell me this is sphagetti code...?

[Ｔｏｈｋａ 夜刀神]

Change FrameRateLimit to something else than 0, maybe 120.
I don't think your issue is same than mine, but you can give it a try.

[Moorish]

Originally posted by Breakaway:

Originally posted by Steve-e-wonder:

https://www.youtube.com/watch?v=RoPOiaSLXms

Thank me later.

Thank you for what? A link to a video that doesn't work at all written by someone that's either very dumb or outright lying for views?

Please stop sharing this nonsense guide, I'll happily thank you to do that!

Like every other DBD guide out there making the same claims, this doesn't work because it can't and this is why:

1. When this game, as well as 99.9% of all games, starts up it reads the contents of the defined ini files and writes them into a live working copy that it creates and only uses while the game is running that only it can access. Any properties or parameters of those properties that are either invalid or not allowed that it encounters it simply uses the preset defaults in its live working file.

2. Changing the FullScreenMode parameter =0 in GameUserSettings.ini does exactly the same as setting the -fullscreen startup switch does, which is that it sets (writes) FullScreenMode=0 in GameUserSettings.ini, so using them together would be pointless. Using them together wouldn't cancel each out one of many clear signs whoever came up with this idea doesn't understand what he's even suggesting.

3. This game is designed specifically to only run in either Borderless fullscreen windowed mode (FullScreenMode=1) or windowed mode (FullScreenMode=2) and as such will not run in Exclusive True Fullscreen mode (FullScreenMode=0) so as I mentioned in point #1 it does exactly the same thing that it will do anytime it is given an invalid parameter for one of it's properties which is it will use the default for that line. When this happens the change is normally reflected in GameUserSettings.ini because it automatically updates the parameter that it is actually using to that file. This is an easy way to find out which properties and/or parameters you're allowed to use because if you're using an allowed parameter the game will not change it back.

For example bUseVSync= has two valid allowed parameters, True or False, with it's default being True. So if we change it manually from default to False then run the game when you check GameUserSettings.ini you'll notice it will still be set to False. Had you used an invalid or parameter that isn't allowed it such as bUseVSync=WOOOHOOO would have used its default of True and would have written this isn't that line in GameUserSettings.ini. This is why so many think that setting "read only" overcomes this, which is doesn't and I'll cover next.

4. Setting Read Only on a file simply stops a file from being overwritten and that's it. Comically enough this defeats the point of using -fullscreen, but anyway it cannot force the game to use the contents of GameUserSettings.ini. This should be a gigantic red flag the guide is written by someone that is clueless because this a trivial thing to understand and also to prove. You can fill up your GameUserSettings.ini with random gibberish or leave it blank, then set "Read only" and start the game, you'll notice it starts up using all defaults. If it was actually being "forced" to use the contents the game would certainly not run. Using "Read only" not only doesn't do what they claim it will do, it can also create other issues so it should not be used, ever.

Wow wow wow calm ur tits bud, i posted the video for OP cuz i tried it and it worked for me, i had -fullscreen on steam launch parameters and it didnt do jack sh/t but when i changed the values in the ini file and making them read only it worked like a charm. Dont be rude, if you dont agree with someone/something, dont go buzurk but instead u can say it does work because this and that. Jeez

[rat]

A good start would be to disable v-sync from the engine.ini. Then make sure you run the game with "Disable Fullscreen optimizations" enabled.

Other than that maybe your hardware is bottlenecking. What are your PC specs?

Edit: Oh as you said you already disabled V sync. Did you try to uncap FPS? Would help if you also posted your specs.

[Old Habits Die Hard]

Originally posted by Steve-e-wonder:

Originally posted by Breakaway:

Thank you for what? A link to a video that doesn't work at all written by someone that's either very dumb or outright lying for views?

Please stop sharing this nonsense guide, I'll happily thank you to do that!

Like every other DBD guide out there making the same claims, this doesn't work because it can't and this is why:

1. When this game, as well as 99.9% of all games, starts up it reads the contents of the defined ini files and writes them into a live working copy that it creates and only uses while the game is running that only it can access. Any properties or parameters of those properties that are either invalid or not allowed that it encounters it simply uses the preset defaults in its live working file.

2. Changing the FullScreenMode parameter =0 in GameUserSettings.ini does exactly the same as setting the -fullscreen startup switch does, which is that it sets (writes) FullScreenMode=0 in GameUserSettings.ini, so using them together would be pointless. Using them together wouldn't cancel each out one of many clear signs whoever came up with this idea doesn't understand what he's even suggesting.

3. This game is designed specifically to only run in either Borderless fullscreen windowed mode (FullScreenMode=1) or windowed mode (FullScreenMode=2) and as such will not run in Exclusive True Fullscreen mode (FullScreenMode=0) so as I mentioned in point #1 it does exactly the same thing that it will do anytime it is given an invalid parameter for one of it's properties which is it will use the default for that line. When this happens the change is normally reflected in GameUserSettings.ini because it automatically updates the parameter that it is actually using to that file. This is an easy way to find out which properties and/or parameters you're allowed to use because if you're using an allowed parameter the game will not change it back.

For example bUseVSync= has two valid allowed parameters, True or False, with it's default being True. So if we change it manually from default to False then run the game when you check GameUserSettings.ini you'll notice it will still be set to False. Had you used an invalid or parameter that isn't allowed it such as bUseVSync=WOOOHOOO would have used its default of True and would have written this isn't that line in GameUserSettings.ini. This is why so many think that setting "read only" overcomes this, which is doesn't and I'll cover next.

4. Setting Read Only on a file simply stops a file from being overwritten and that's it. Comically enough this defeats the point of using -fullscreen, but anyway it cannot force the game to use the contents of GameUserSettings.ini. This should be a gigantic red flag the guide is written by someone that is clueless because this a trivial thing to understand and also to prove. You can fill up your GameUserSettings.ini with random gibberish or leave it blank, then set "Read only" and start the game, you'll notice it starts up using all defaults. If it was actually being "forced" to use the contents the game would certainly not run. Using "Read only" not only doesn't do what they claim it will do, it can also create other issues so it should not be used, ever.

Wow wow wow calm ur tits bud, i posted the video for OP cuz i tried it and it worked for me, i had -fullscreen on steam launch parameters and it didnt do jack sh/t but when i changed the values in the ini file and making them read only it worked like a charm. Dont be rude, if you dont agree with someone/something, dont go buzurk but instead u can say it does work because this and that. Jeez

I am calm. I simply provided detailed proof using multiple examples as to why it can't work for anyone.

Can you dispute the clear points I clearly made? How about even something simple such as telling us which verifiable way you used to know it was in exclusive true fullscreen mode instead of borderless windowed fullscreen?

It didn't work for you, because it doesn't and can't work for anyone due to the points that I made.

Sorry if that hurt your feelings, that wasn't my intention. I even said I would thank you not to share that guide, which I happily would and will!

[Moorish]

Originally posted by Breakaway:

Originally posted by Steve-e-wonder:

Wow wow wow calm ur tits bud, i posted the video for OP cuz i tried it and it worked for me, i had -fullscreen on steam launch parameters and it didnt do jack sh/t but when i changed the values in the ini file and making them read only it worked like a charm. Dont be rude, if you dont agree with someone/something, dont go buzurk but instead u can say it does work because this and that. Jeez

I am calm. I simply provided detailed proof using multiple examples as to why it can't work for anyone.

Can you dispute the clear points I clearly made? How about even something simple such as telling us which verifiable way you used to know it was in exclusive true fullscreen mode instead of borderless windowed fullscreen?

It didn't work for you, because it doesn't and can't work for anyone due to the points that I made.

Sorry if that hurt your feelings, that wasn't my intention. I even said I would thank you not to share that guide, which I happily would and will!

I don't got time to argue with brainless people sorry. What you think is not gonna change anything, OP still gonna try and figure out for himself if it works for him or not. PERIOD.

[Sonnolo]

Edit cfg are equal to cheating

[Garf]

Originally posted by Steve-e-wonder:

https://www.youtube.com/watch?v=RoPOiaSLXms

Thank me later.

This did help a bit it lessened the stutters but still thxs

[Old Habits Die Hard]

Originally posted by Steve-e-wonder:

Originally posted by Breakaway:

I am calm. I simply provided detailed proof using multiple examples as to why it can't work for anyone.

Can you dispute the clear points I clearly made? How about even something simple such as telling us which verifiable way you used to know it was in exclusive true fullscreen mode instead of borderless windowed fullscreen?

It didn't work for you, because it doesn't and can't work for anyone due to the points that I made.

Sorry if that hurt your feelings, that wasn't my intention. I even said I would thank you not to share that guide, which I happily would and will!

I don't got time to argue with brainless people sorry. What you think is not gonna change anything, OP still gonna try and figure out for himself if it works for him or not. PERIOD.

In other words you can't, what a huge surprise.

You're a perfect example of the Dunning-Kruger effect in action. This type of thinking, and lack of education is why it's nearly 2020 but small groups of people think that the earth is flat and vaccines cause autism.

Please stay in school kids!

[Perfect Cell]

Originally posted by TwitchSonnolo🤟🏼:

Edit cfg are equal to cheating

it's a necessary evil when the game doesn't work right

[LoopzAhoy]

anyone find a fix?

[egs]

Steam Deck should help a lot.