just a minor thing, i don't even know if it's an actual error: the radial blur description says "enable or disable depth of field", but if i'm not mistaken, previous versions said something about the screen effect whenever you took damage (not the blood splatter effect)
One of the more recent versions I linked all the button descriptions to the repository I've been working on for ~9 years with a few thousand descriptions, so all of the tool-tip descriptions are more reliable to be correct than before
Just a heads up (using latest tool 2.0.5.37197 with latest game PC 1.10.984): "Fix Sensitivity Ratio" (apparently a fix for ironsights issues) under Tweaks tab is not staying checked, regardless of setting config files to read-only or not. Hit Save Now button and it will stay checked between tabs, but when I exit and re-launch the tool it is always unchecked. Everything else is working fine.
I hate to bother you again, but there is another issue *lol*. ... I can replace the original launcher and it works quite wll. However, when I try to restore the original launcher do I get a large popup window "Unexpected Error" and it tells me "Unexpected Crash! Try running as administrator: ..." which makes no sense, because it could replace the original launcher, so it should also have no issues to restore it.
Yeah, a ton. Copy'n'paste does not work on it though or I would have dropped it here. Then window pops up like three times, then the settings window crashes. I will see if I can get you a screenshot.
I may have found a bug. When I open the Settings on the launcher for a second time do all settings come up empty. First time opening Settings shows all the values. Closing it with X closes the window, and pressing Settings again then shows no values. Or am I missing something?
I'm unable to replicate this. Do you have a settings file located:
%appsettings%\Bilago\BilagoBethesdaConfigTool ?
If you open it with notepad you should have all your settings in there that get filled out in the settings page. If this file is missing or empty it would explain your issue. If so, delete the file and run the app again
Also make sure in the top Window Bar you have "Fallout4" selected, not "Starfield"
I have AppData\Roaming\Bilago\BilagoBethesdaConfigTool\UserSettings.json
It is also set to "Fallout 4" and I should mention that it is also replacing the default launcher and set to start f4se_loader.exe. This is working as intended.
Only when I start the game through the replaced Fallout4Launcher.exe, go into Settings, close the Settings window, go back into Settings, do I still get empty fields. The fields are all there and set the first time. So it does appear to be working. Just not for the second time.
And to be sure did I completely uninstall it, removed any old folders and traces of it including under AppData, and reinstalled it with Vortex. It got installed as C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Fallout4ConfigurationTool.exe. It keeps doing it.
Hello, could you please allow vsync to be set to 3? This is a new feature of the updated game to now allow for 0, 1, 2, and 3. https://steamcommunity.com/app/377160/discussions/0/4365754575402357359/
Also, the game has some new .ini settings. Not sure if these are all, but here a link to their names and defaults: https://steamcommunity.com/app/377160/discussions/0/4365754151464961075/
I have made the change and will release it soon. For now, you can go to the Main tab and search for ipresentInterval and set it to 4 there.
Thanks for the link to new settings, however the user didn't provide the file it belongs in Prefs vs Custom - I don't have my game updated yet so I can't figure it out on my own.
I filtered those settings out of the game's executable and compared them to what I could pull out of the old one. There were larger differences, but these are the only ones that had genuinely no values when querying them with getini on the console of the old version 1.10.163. These settings only have values now with 1.10.980 and .984.
I suggest to put the [Memory] values and the [Interface] strings into Fallout4Custom.ini. I do not see much point for those being in the Fallout4Prefs.ini file. These also do not show up in any of the generated .ini files.
The [General] bIncludedContentMessageSeen=1 flag should go into Fallout4Prefs.ini and the game writes it there, too.
Two settings that are being talked about, but that may be simply dummy placeholders are:
The game (or the launcher?) writes these into the Fallout4Prefs.ini file. Both with a value of 0. Of course some speculate it would turn on these modes on the PC like one can find on consoles now. However, none of the two flags make a single difference in frame rates for me. So I doubt these do anything on the PC.
I appreciate the insight. I released a new version including these settings, and the extra iPresentInterval.
The [MAIN] section for all the other settings go in Fallout4Custom.ini so I wonder why the game is writing these specific ones to Prefs, but until someone looks into it, it might not matter if it's console only.n
think there's a mistake with the "all npc's killable" option. when i first launched the tool, it was blue (on), so i turned it OFF. later when i was playing, my companion died in the middle of the fight, lol, so i checked the tool again and looked for the bEssentialTakeNoDamage and the value was 0, but the tool says the default value is 1 and when i changed it back to 1, the "all npc's killable" option went blue (on) again.
The NPC Killable button has been renamed to NPC God Mode, as enabling the button (turning blue) means you're setting bEssentialTakeNoDamage to 1, not 0.
Fixed the bug where using the recommended button is turning bForceUpdateDiffuseOnly to 1, when it should be setting it to 0.
Excellent, thank you! I was running Fallout 4 maxed out without any problems before the update, after the update the game decided to run sluggishly in some areas. With this tool I easily tweaked my game and it's running great now. Thanks!
3444 comments
the settings window crashes. I will see if I can get you a screenshot.
You would need to run Fallout4ConfigurationTool.exe to restore the original launcher - else you will get an access denied error like this
%appsettings%\Bilago\BilagoBethesdaConfigTool ?
If you open it with notepad you should have all your settings in there that get filled out in the settings page. If this file is missing or empty it would explain your issue. If so, delete the file and run the app again
Also make sure in the top Window Bar you have "Fallout4" selected, not "Starfield"
It is also set to "Fallout 4" and I should mention that it is also replacing the default launcher and set to start f4se_loader.exe. This is working as intended.
Only when I start the game through the replaced Fallout4Launcher.exe, go into Settings, close the Settings window, go back into Settings, do I still get empty fields. The fields are all there and set the first time. So it does appear to be working. Just not for the second time.
And to be sure did I completely uninstall it, removed any old folders and traces of it including under AppData, and reinstalled it with Vortex. It got installed as C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Data\Fallout4ConfigurationTool.exe. It keeps doing it.
https://steamcommunity.com/app/377160/discussions/0/4365754575402357359/
Also, the game has some new .ini settings. Not sure if these are all, but here a link to their names and defaults:
https://steamcommunity.com/app/377160/discussions/0/4365754151464961075/
Thanks for the link to new settings, however the user didn't provide the file it belongs in Prefs vs Custom - I don't have my game updated yet so I can't figure it out on my own.
I suggest to put the [Memory] values and the [Interface] strings into Fallout4Custom.ini. I do not see much point for those being in the Fallout4Prefs.ini file. These also do not show up in any of the generated .ini files.
The [General] bIncludedContentMessageSeen=1 flag should go into Fallout4Prefs.ini and the game writes it there, too.
Two settings that are being talked about, but that may be simply dummy placeholders are:
[MAIN]
bQualityModeEnabled=0
bPerformanceModeEnabled=0
The game (or the launcher?) writes these into the Fallout4Prefs.ini file. Both with a value of 0. Of course some speculate it would turn on these modes on the PC like one can find on consoles now. However, none of the two flags make a single difference in frame rates for me. So I doubt these do anything on the PC.
The [MAIN] section for all the other settings go in Fallout4Custom.ini so I wonder why the game is writing these specific ones to Prefs, but until someone looks into it, it might not matter if it's console only.n
The function of the ability to describe commands in an AUTO executable file
We also need to check the archive invalidation and the inclusion of free files functions.
The NPC Killable button has been renamed to NPC God Mode, as enabling the button (turning blue) means you're setting bEssentialTakeNoDamage to 1, not 0.
Fixed the bug where using the recommended button is turning bForceUpdateDiffuseOnly to 1, when it should be setting it to 0.