Badmagic Posted August 6, 2018 Share Posted August 6, 2018 Been away for a considerable time, see people saying you can use this in "Documents\My Games\Fallout4\Fallout4Custom.ini" to reduce some esp's but whatever I do it doesn't seem to work and I cant find any clues as to where its going wrong. Bottom of [General] section. sStartingConsoleCommand=cl rim 0.0005; gr off; setgs fSandboxCylinderTop 576; setgs fSandboxCylinderBottom -576; setgs iTerminalDisplayRate 1200; setgs fGunShellLifetime 600; setgs fGunShellCameraDistance 51200; setgs iDebrisMaxCount 1500; setgs fworkshopwiremaxlength 4096; setgs fBumpReactionSmallWaitTimer 0.5; setgs fBumpReactionMinMoveDist 150; setgs fBumpReactionIdealMoveDist 250 On opening the console in game, either from launch or once the game is actually loaded its clear it stops after the first command. Now, I'm not totally new to this and I know you use the semi colon to comment lines so, I would presume this is incorrect information being spread around but I've seen it stated this is correct when challenged. I've also seen it said you can make it a batch file, so for example. Filename:start.txt Contents:cl rim 0.0005gr offsetgs fSandboxCylinderTop 576setgs fSandboxCylinderBottom -576setgs iTerminalDisplayRate 1200setgs fGunShellLifetime 600setgs fGunShellCameraDistance 51200setgs iDebrisMaxCount 1500setgs fworkshopwiremaxlength 4096setgs fBumpReactionSmallWaitTimer 0.5setgs fBumpReactionMinMoveDist 150setgs fBumpReactionIdealMoveDist 250 Then change "sStartingConsoleCommand=" to "sStartingConsoleCommand=bat start" (excluding the quotes) Nope, still stalls after the first command. To note, manually running "bat start" (excluding the quotes) from the console once in a running game it works fine, but kind of entirely misses the damned point of trying to automate it. Anyone know what's missing from the instruction from topics discussing this? Link to comment Share on other sites More sharing options...
Deleted3082751User Posted August 6, 2018 Share Posted August 6, 2018 (edited) should be in the fallout 4 root folder: download this: https://www.nexusmods.com/fallout4/mods/102 place it in your fallout 4 root folder, open fallout4ConfigTool - Click on the Tweaks Tab - Click on AutoExec - Click on Add - and add all of them commands into the AutoExec.txt Document that Pops up, save the document, then back on the tool, click on Save. you should be good to go i have tried it myself with many commands and it worked flawlessly the game has to check all 3 fallout 4 ini files on load, which is likely why it is flopping after the first command, where as using the method above, it will check the commands at the right time, meaning it will have a much higher success rate. because it is an AutoExec document (Auto Execute, has the highest priority), as the game will read it as soon as the game launches, quite possibly before everything else. Edited August 6, 2018 by Guest Link to comment Share on other sites More sharing options...
BlackRelic27 Posted January 6, 2019 Share Posted January 6, 2019 (edited) Few months old necro, but I'm having the exact same problem. I'm doing everything to the letter but only the first command in the bat file takes. Nothing else does and I have to activate the bat in the console manually if I want all the lines to take. I'm running the game through MO2 but I've made sure the command is in the MO profile folder ini's. I put it in both ini locations (MO2, regular My Documents/My Games/Fallout 4 location) just to be extra sure but no dice. I've never had a problem with this till just recently when I reinstalled everything due to a clean Windows install. Edited January 6, 2019 by SacredKnight81 Link to comment Share on other sites More sharing options...
HULKHOD3N Posted January 9, 2019 Share Posted January 9, 2019 Same here. Worked fine for months, after a clean Windows install it just doesn't work anymore like before. Link to comment Share on other sites More sharing options...
Nofsdad Posted June 13, 2019 Share Posted June 13, 2019 And I'm having the same problem also. This command used to work just fine until one of Beth's monetization updates overtook it and broke it. All of these old "solutions" are invalid. Has anyone running a currently updated version of the game found a way to make this work again? Link to comment Share on other sites More sharing options...
lvhoang Posted August 29, 2021 Share Posted August 29, 2021 I'm still having the same issue, whether using a bat file or inputting commands directly into "sStartingConsoleCommand". Had anyone figured out a solution yet? Been away for a considerable time, see people saying you can use this in "Documents\My Games\Fallout4\Fallout4Custom.ini" to reduce some esp's but whatever I do it doesn't seem to work and I cant find any clues as to where its going wrong. Bottom of [General] section. sStartingConsoleCommand=cl rim 0.0005; gr off; setgs fSandboxCylinderTop 576; setgs fSandboxCylinderBottom -576; setgs iTerminalDisplayRate 1200; setgs fGunShellLifetime 600; setgs fGunShellCameraDistance 51200; setgs iDebrisMaxCount 1500; setgs fworkshopwiremaxlength 4096; setgs fBumpReactionSmallWaitTimer 0.5; setgs fBumpReactionMinMoveDist 150; setgs fBumpReactionIdealMoveDist 250 On opening the console in game, either from launch or once the game is actually loaded its clear it stops after the first command. Now, I'm not totally new to this and I know you use the semi colon to comment lines so, I would presume this is incorrect information being spread around but I've seen it stated this is correct when challenged. I've also seen it said you can make it a batch file, so for example. Filename:start.txt Contents:cl rim 0.0005gr offsetgs fSandboxCylinderTop 576setgs fSandboxCylinderBottom -576setgs iTerminalDisplayRate 1200setgs fGunShellLifetime 600setgs fGunShellCameraDistance 51200setgs iDebrisMaxCount 1500setgs fworkshopwiremaxlength 4096setgs fBumpReactionSmallWaitTimer 0.5setgs fBumpReactionMinMoveDist 150setgs fBumpReactionIdealMoveDist 250 Then change "sStartingConsoleCommand=" to "sStartingConsoleCommand=bat start" (excluding the quotes) Nope, still stalls after the first command. To note, manually running "bat start" (excluding the quotes) from the console once in a running game it works fine, but kind of entirely misses the damned point of trying to automate it. Anyone know what's missing from the instruction from topics discussing this? Link to comment Share on other sites More sharing options...
aurreth Posted August 29, 2021 Share Posted August 29, 2021 Create a text file in you FO4 root directory called "autoexec.txt". In that file put one console command per line. In your Fallout4Custom.ini add the line "sStartingConsoleCommand=bat autoexec". That's it. Link to comment Share on other sites More sharing options...
Recommended Posts