Visit the Kill Switch Master List for more information on this and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
If I change GameUserSettings can I get banned?
Just found out that mine have everything on "3" and it seems I can go to "4" and have better graphics.
Would I get banned if I do that?
Comments
-
You technically can be, but you in all likeliness won't be. EAC does not recognize these file changes as malicious, and if it were to, it at most would tell you your game files have been modified and not allow you to play until you rectify it.
This is a user configuration file that is being written to all the time anyway, you "manually" modify it by using in-game settings as well. Plus BHVR has restricted the use of most of all variables that could be harmful from these files to my knowledge. Either way, as long as you only change values of existing variables, you will be fine.
And there are various important changes people use this file for that the game unfortunately (and ridiculously) still does not present from the in-game menu. Such as disabling V-Sync and enabling true fullscreen mode with distinct display resolutions. Although the "3" and "4" thing is something the devs had already realized - "Ultra" used to be 3, but last I checked Ultra does now set the variables to 4. If that has since been reverted, I'd chalk it up as one of many such oversights where old issues pop back up in the game by accident. Their internal version documentation must be pretty wild, because old build bugs always showed up again frequently.
1 -
Thanks for replying. :)
All of this makes sense. Went ahead and changed a few things in the file and it didn't made ANY difference XD
It seems I was already using max settings indeed.
Thanks anyway :)
0 -
When a fresh GameUserSettings is generated it sets =4 and shows "Ultra" on the in-game graphic setting. Previously using =4 used to be Cinematic mode and would show nothing on the in-game graphic setting but now =4 is identical to =3.
Also, at least in Win10/11, simply setting Fullscreenmode=0 does not enable exclusive fullscreen mode, it's FSO even if you manually choose "Disable fullscreen optimizations". To actually get exclusive fullscreenmode is possible but almost everyone that thinks they are using FSE is really just in FSO they've just never actually checked and are assuming. FSO works better than FSE ever used to and using FSE actually creates issues.
0 -
According to @forthelulz, 3 is now identical to 4. I wouldn't know because I always play on 0. One cool thing about setting graphics options through the file though is that you can selectively choose quality for the different elements. So you can for instance have everything on 0, but then set shadow quality to the highest value. This is also something most games offer from the in-game menus.
I would recommend using true fullscreen mode to most of anyone, in my experience the performance is much better. It also allows you to actually disable V-Sync (in windowed mode even with V-Sync disabled you still have the DWM's compositor), which reduces input latency.
Thanks for the clarifications.
I'm actually interested in the different fullscreen modes, do you mind sharing more? What are the practical difference, are there non-negligible performance differences, and how does one actually enforce different modes?
I've been using true fullscreen in DbD for a long time, even back on Windows 7. I haven't really noticed any difference with it in Windows 10 - it still applies the set screen resolution, screen tearing still occurs when V-Sync is disabled, and tabbing out of the game still takes a relatively long time if the desktop and game resolution differ. I have manually disabled FSO from the executable, but I also don't think it really changes anything. The Windows media playback overlay thing pops up on top of the game, which did make suspect it's not the FSE mode it used to be.
One thing that did change but that I'm pretty sure was due to updates to the game itself, is that it used to be possible to open the Steam overlay, right-click anywhere within it, and then move the cursor to a secondary monitor and do stuff on it without having to tab out of the game (so even the game resolution would be maintained on its monitor). This was pretty handy, but it stopped working at some point.
0 -
Considering that the primary reason people modify these files is to disable Vsync and raise the FPS to 120, is there any plan to make either or both of these available in the in-game configuration so that people don't have to modify these files to get those options?
If no, is this because there's an intentional choice to hide these options or because it hasn't been prioritized by the developers?
3 -
To find out exactly what's happening and know if you're using FSO vs FSE and so on, instead of guessing the simplest and best way is to install Frameview:
It's free and from Nvidia and works with Nvidia & AMD GPUs. You don't even need to restart your computer to use it.
I made a quick video awhile ago demonstrating it so that anyone interested can see how easy and useful it is even if you just want to use the overlay. Simply install, set any applicable options (I disable PPW because it doesn't interest me, I prefer using F10 instead of Scroll Lock to start/stop benchmarking and I like using a 5 second delay before benchmarking begins and using a 20 second timer for benchmarking because that's usually enough for what I need) and then startup game.
The last line is the mode tags which are as follows:
F = Fullscreen Mode - the game is running in a Fullscreen mode
I = Independant Flip Mode - the game is simulating as if it was running in Full Screen Exclusive mode but is actually running in either Fullscreen Optimized or Windowed Optimized mode
W = Windowed Mode - the game is running in a Windowed mode
V = Vsync Enabled (Lack of V means Vsync is Disabled)
T = Tearing Allowed (Lack of T means Tearing is Disallowed)
Edit: I would be interested to know if you're actually using FSE because like I said, it's very rare to find someone that's done it because it requires a lot more than just changing a line in GameUserSettings you need to change specific registry keys inside Windows, most times people just think they are using FSE when in reality they're using FSO and don't realize it because they don't know how to verify which Presentmode is in use and Microsoft has done such a good job with FSO that the difference is essentically zero.. in fact using FSE nowadays actually creates issues with other programs.
Installing Frameview and firing up the game will let you know immediately what's happening, and it's awesome! :)
0 -
Thanks!
F I T, so fullscreen in simulated mode. Did suspect that registry tinkering would be needed to actually get legacy fullscreen mode, but since there's no discernible difference between it and simulated I never really looked into it. Although I would be curious whether it'd bring back the right-click functionality I mentioned.
1 -
No problem! I'm not sure about right-click and mutliple monitors but I do remember reading that it actually mattered which monitor was plugged into which HDMI/DisplayPort which isn't helpful and vague I know but I know I read something about that being a solution, so maybe for the hell of it you could try switching them around? :)
0 -
Can you check your Registry to see if you have the following?
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm
- DWORD: OverlayTestMode
- Value: 0x00000005(5)
I remember this being a fix for some multimonitor issues a year ago, normally it wouldn't be there but for some people adding it solved their issue.
0 -
Entry wasn't present, created it myself. Didn't change anything so far, as far as I can tell. But maybe important to note is that I'm currently playing on DX12 since I have been having crashes on DX11 on my new PC for some reason. So perhaps I will play around with this some more and try to get actual legacy FSE in DX11 too. Main monitor is DVI btw, secondary HDMI.
0 -
I'd guess that something is wrong somewhere if you're getting crashes and using dx12 is a workaround.
I would, if it were me, do what I call the nuclear option lol which is pretty much doing everything possible all in one big single sequence that I know makes everything work perfectly. I just installed 22H2 and it's made DBD run terribly as well as it has added Windowed optimizations now which wasn't previously active or even availabel via registry changes.
If interested in the changes: https://support.microsoft.com/en-us/windows/optimizations-for-windowed-games-in-windows-11-3f006843-2c7e-4ed0-9a5e-f9389e535952
This very much directly effects DBD players since almost everyone IS playing in windowed mode (even though I'm sure 3/4 of them actually think they're using fullscreen exclusive but they aren't as we talked about lol) so I've actually just started doing nuclear option which is why it came to mind.
22H2 started releasing about 2 weeks ago and they are trickling it out week by week over the course of a month, it only became available to me early this morning so I installed it and I'm only just now able to check it out and tried out DBD to find it a mess :( Feels exactly like it did "out of the box" which is so awful I genuinely can't believe they don't realize how bad it is or think about how many people that turns away from the game.
0 -
I suspect the crashes are somehow due to Reshade. I installed a newer version of it on my new PC than I had had before, but I was too lazy to do all the settings and get all the filters again, so I just replaced its files with those of my old install, and I suppose that can somehow have led to this. At least when I googled my crash code, the only thing DbD-related among the already very limited results was about Reshade. Why running on DX12 prevents those crashes beats me however. Either way, I haven't noticed any negative performance differences as compared to DX11, so I don't mind staying on DX12. Only thing is that the game takes a little longer to open perhaps. I think I'll uninstall Reshade and see if that prevents crashes on DX11, and if so, I'll see about getting around to actually installing it properly.
I'm still on Win 10 (21H2), but I had to change from Education to Home with my new PC, so I unfortunately won't be able to hold off on the 22H2 update too much longer either I'm sure. I guess maybe the Win 11 windowed optimizations won't be in it however? Do let me know if in your nuclear approach you find anything to get DbD back to being/feeling like "true" fullscreen.
A little something you might not be aware of: Using
[/Script/Engine.InputSettings] bEnableMouseSmoothing=False
in the Input.ini makes mousing feel noticably better to me. I think it's another thing making DbD feel a little off "out of the box". And yeah, "true" fullscreen mode, distinct resolutions, disabled V-Sync, uncapped/unsmoothed framerate, these are all things that make the game perform and feel so much better, it's ridiculous they are still not options in the in-game menu. Those are completely default options in basically all video games.
1 -
OMG! Thanks for reminding me about mouse smoothing!
I had meant to mention to @Rizzo about them using mouse smoothing by default & hiding it and how it effects a ton of users and is one thing that you can't change without editing ini files. I made a video months ago about it, I had meant to go into more detail but it got lost in my pile of "things I'm going to do tomorrow" lol
Edit: To also add to the above, this is why a decent amount of users found FPS issues "improved" when they lowered their mouse polling rate to 500Mhz or below, while it's a bandaid fix it does help quite a bit although if you fling your mouse around you can still it still starts to cut into FPS just only a small fraction of the impact of 1000Mhz and up. So anyone that has had to lower their poiling rate should look into turning off mouse smoothing + making sure that in Windows Mouse Setting "Enhance Mouse Pointer Precision" is UNCHECKED at all time.
This game is completely unplayable with my mouse because of the 8k polling rate, if I leave mouse smoothing enabled anytime my mouse is moving my FPS tanks and if I move it around quickly for 4-5s or frantically click mouse buttons (this is because changing the mouse polling rate does not effect mouse buttons they always run at the max polling rate regardless if the setting in software which has been verified but other with the equpiment to actually verify it) the game will actually crash because my FPS drops to literally 0.
I can make another video demonstrating that 4-5 seconds of fast mouse movement will 100% crash the game every time if @Rizzo would like.
0 -
The last version of Reshade, basically all the 5.0's have had issues with this game. It's best to go back to 4.9's if you want to use it.
I used to always use Reshade but because of the issues I just stopped using it completely.
Edit: Oh and Windows 11 22H2 has competely screwed DBD up. I am going to see if G-Sync works with it but otherwise I've tried everything I could think of but nothing makes it run normally so I'm reverting back and pausing updates for 5 weeks. Hopefully by then either Windows or DBD will patch it, although I'm honestly afraid that so many are used to this game running so badly that they won't even notice.
Before I do though I'm going to make a few videos showing the night & day difference between 11 21H2 & 11 22H2 with identical settings after 100% completely fresh install of both 22H2 + GPU drivers + Steam & EGS + DBD. It's so awful everything stutters all the time and FPS and frametimes are garbage "out of the box" and with every tweak that I've used for 5 years that always makes this game run amazingly, which can always be seen in any of my videos because I always have at least Frameview monitoring on screen if not others.
0 -
Makes sense that smoothing issues get worse the more frequently mouse data comes in, more points to process. I'm on 1kHz poll rate and smoothing effects are definitely most noticable on faster mouse movements. Feels like negative acceleration, which would make sense if framerates collapse momentarily. They should indeed just disable this by default, nobody needs count smoothing in this day and age anyway.
Also pretty sure that Windows' Pointer Precision was disabled by default on Win 10 Edu, yet on Home it was enabled by default. Also a shame that people still need to be told to disable that.
Yeah, it seems to be the new Reshade version. I played DX11 without Reshade for around an hour, no crashes. Did a fresh install of Reshade and manually applied settings and adjusted filters, rather than replace the files. Still got two random crashes in a session of two to three hours. Weirdly the crashes tend to happen on loading into a trial or exiting the post-trial screen. Now I'm back on DX12 and again no crashes even over multiple hours. I will definitely try DX11 + an older version of Reshade.
I hope 22H2 won't be that catastrophic once it hits Win 10, ha, or that we'll figure out some remedy.
1 -
I brought up the issues with Reshade on the forum page but didn't get much of a reply other than at first he blamed DBD which could be the case I'm not sure. The first couple of 5.0's made it crash either right at match start or at the end and then eventually around 5.3 or something the crashes stopped but FPS would tank quite hard occasionally which was annoying enough for me to quit using it altogether.
I believe I figured out the 22H2 issue, after a lot of tinkering. I was able to get it working on a completely fresh install on a new drive, so now I'm upgrading my current 21H2 to 22H2 to test if I can do the same thing with an upgrade. It has to do with Windows stupid Gamebar recording feature, it turns on parts of it with 22H2 and I had to dig into the registry to figure it out and re-do the changes I previously always did.
Once it is done upgrading in awhile I will test it out and report back. I sure hope it works to avoid having to completely commit to a fresh install of everything, but this stuff bugs me enough that I'll do that if I have to lol
Edit: I can tell you which registry entry to change to test FSE vs FSO but I don't want to do it on here because I think it will create more problems especially for average users but if you look at my video list for the one regarding using Frameview to test for FSE vs FSO and how to compare them I'll leave the registry line to change in the video description for awhile until you get a chance to copy it.
1 -
I to make these videos I did the same thing each time for the most part. I just restarted PC and put the ini files, nccpl and win version on the screen to keep track of things, fired up OBS and then start DBD up and jump into the first match possible and record it so there is a fairly long session of the game running along with the stats on screen. So forgive the gameplay, the point of the videos are so that you can watch the stats carefully to see if hilarious but sad difference between 21H2 & 22H2 with identical settings on everything. Easiest to just watch it in high speed and focus on the following stats:
- AVG
- 90th
- 95th
- 99th
- DROP
- PLAT
**The 1st video I forgot to add the RTSS stats but I from then on & in 3rd video I forgot or thought I hit record but realized after a couple of minutes that it wasn't recording and started it.
Here Is First Example Of 22H2 And It's So Bad I Don't Even Play A Match Because I Can Tell It's Going To Be Horrible Within 1 Second Of The Game Starting :/
Edit: Had Audio Muted Not That It Makes A Difference. I Can't Even Shake My Character Or FPS TANKS - Visable Stutters Right From Main Menu Appearing - Clicking On Anything Or Even Moving Mouse Over Icons Creates Stutters + FPS Drops - Even When Just Sitting In Menu 95th + 99th Stats Constantly Going Up And Down
I'll force myself to record a couple of matches tonight and upload them though but I can promise it's going to be a terrible experience to try and play.
Post edited by forthelulz on0 -
Let's be honest. That won't ban anyone.
1
