all the light and stuff is on though, and everything else is high.ĭisable the bloody-screen and dirt effects. Lastly, what are the best graphics settings in the video menu for visibility? I disabled lens flare, distortion and motion blur. Here is what my HUD and game in general looks likeĬheck out /r/dirtybombconfigs to find a nice HUD. These configs will focus all the important HUD information on one spot. What you could do however, is to get yourself a centered HUD config. In terms of graphics, there is not much to do. "stat fps" - Will display FPS and frametime. "disconnect" - Will disconnect you from the current server, no matter if you are ingame or in the lobby screen. "killallsounds" - Type this if you hear some sound repeating itself constanly (happens rarely, still neat to know). Some other commands you should know about, but shouldn't put into the autoexec "colorgrading 2" - Removes color filters on some maps like Trainyard or Chapel. It will improve visibility on a lot of maps and help your eyes. You can also disable the colorgrading (blue tone on Chapel and orange tone on Trainyard) by adding "ColorGrading 0" to the exec file, but that's not a solely positive change, so just use it if you like it.Īny commands I should put in my autoexec, to improve visibility and mouse movements and other general improvements?ĭefininetely put "colorgrading 2" in your autoexec. You could also add "Stat FPS" to always display FPS, which can be a good way of checking that the autoexec works. Rename the file to "autoexec.cfg" and place it in "C:\Program Files (x86)\Steam\SteamApps\common\Dirty Bomb\Binaries". Replace 1024 with 680 if you have a 2GB GPU, or remove it entirely if you have less than 2GB VRAM. Then create a new txt file, open it, type in: FogDensity 0 You can also add "-NOSPLASH" and "-USEALLAVAILABLECORES for good measure.
#Best dirty bomb config file how to#
Here's how to do it and the most important commands:Īdd "-EXEC=autoexec.cfg" to the Steam launch options (without quotation marks). There is a point in using an autoexec though (console commands that execute automatically when you start the game). Changing them and making the config Read-only can cause all kinds of issues. So.Also, any changes I should make to the. Then there's also -windowed and -fullscreen, both fully functional.Īnd some other options I found but was completely unable to tell if they made any noticeable difference or were even functional at all: In theory, using -useallavailablecores and -forceshadermodel2 should improve performance on some computers, and -novsync should obviously get rid of VSync although it didn't seem to make a difference (?). I get ~300-400fps no matter the launch options, and any comparisons were useless as they all appeared to have exactly same results. It does seem to work fine.Īs for the others, I'm unable to see any difference. accidentally change fov or sensitivity and save those changes. noini disables changes to config files while in-game, making it impossible to, i.e. but the graphics quality was just unusable it was really bad. I found a config which gave me 120-150fps.
nosplash is probably the one most users should be interested in, it disables the annoying splash screen that no one cares about. It's actually one of the really good configurations if you know how to tweak some settings in it. Some of the more interesting launch options I've found and ones I use currently are: -forceshadermodel2 -novsync -noini -nosplash -useallavailablecores I don't know how common this knowledge is, I've never seen anyone mention this before so I thought it would be a good idea to bring it up to discussion.
0 kommentar(er)
