oldbastard42 Posted July 30, 2019 Share Posted July 30, 2019 Vortex 0.19.1Fallout 4 v1.10.138F4SE v0.6.17Mod count - 145 Problem: "Scrap Everything - Ultimate Edition.ini" overriding "Fallout4Custom.ini". I noticed that any changes I make to Fallout4Custom.ini, don't do anything and I have to edit Scrap Everything - Ultimate Edition.ini instead. It seems the game is using that as the default .ini file. If I disable the mod "Scrap Everything",the game starts properly, but if I remove the file "Scrap Everything - Ultimate Edition.ini", the game starts but I just get a black screen. On the Vortex profile page, "Game Settings" is set to "No". Vortex.log only shows references to the correct .ini files. Is Vortex somehow forcing the game to use the wrong ini file? Thanks. Link to comment Share on other sites More sharing options...
HadToRegister Posted July 30, 2019 Share Posted July 30, 2019 Vortex 0.19.1Fallout 4 v1.10.138F4SE v0.6.17Mod count - 145 Problem: "Scrap Everything - Ultimate Edition.ini" overriding "Fallout4Custom.ini". I noticed that any changes I make to Fallout4Custom.ini, don't do anything and I have to edit Scrap Everything - Ultimate Edition.ini instead. It seems the game is using that as the default .ini file. If I disable the mod "Scrap Everything",the game starts properly, but if I remove the file "Scrap Everything - Ultimate Edition.ini", the game starts but I just get a black screen. On the Vortex profile page, "Game Settings" is set to "No". Vortex.log only shows references to the correct .ini files. Is Vortex somehow forcing the game to use the wrong ini file? Thanks. This has NOTHING to do with Vortex, and everything to do with the Mod "Scrap Everything" that is referencing the "Scrap Everything - Ultimate Edition.ini" instead. Link to comment Share on other sites More sharing options...
wcurtin1962 Posted July 30, 2019 Share Posted July 30, 2019 I had a scrap everything mod conflict with a settlement boundaries expansion mod. Link to comment Share on other sites More sharing options...
Pickysaurus Posted July 30, 2019 Share Posted July 30, 2019 This is my understanding of how these things work. With the vanilla game you have Fallout4Custom.ini which you can use to edit your settings. However, mods can include their own INI, these tweaks override the ones set in any INIs related to the vanilla game. So if I have MyMod.esp installed with MyMod.ini in the data folder. The game will load up with Fallout4Custom.ini and apply any additional edits from MyMod.ini over the top. So what you're experiencing is correct. The values in Scrap Everything - Ultimate Edition.ini will always overwrite the base INI settings. Link to comment Share on other sites More sharing options...
oldbastard42 Posted July 31, 2019 Author Share Posted July 31, 2019 Yeah, I was pretty sure it was not being caused by Vortex but asked just in case. I can't understand why scrap everything has to copy the entire (current at mod install time) custom ini file - it seriously stuffs a lot of other things up, especially the custom savegame directories for Vortex. Link to comment Share on other sites More sharing options...
Pickysaurus Posted August 2, 2019 Share Posted August 2, 2019 Yeah, I was pretty sure it was not being caused by Vortex but asked just in case. I can't understand why scrap everything has to copy the entire (current at mod install time) custom ini file - it seriously stuffs a lot of other things up, especially the custom savegame directories for Vortex. So I just tested that and I can confirm that Vortex's savegame support is only broken if your mod INI file contains the following sections: [General] SLocalSavePath=Saves\breakallthethings\ To be frank, it would be stupid of a mod author to include this line in their mod INI file so it isn't something we'd be able to avoid in Vortex. Link to comment Share on other sites More sharing options...
Glass1411 Posted August 2, 2019 Share Posted August 2, 2019 @Oldbastard42I ran into the same issue when I was putting together my little Useful Combinations mod. If you want to use a Fallout4custom.ini and Scrap Everything's extra's just copy the line(s) from the SE.ini into your Fallout4.ini. SE's ini's contain one or two entries:[General]bUseCombinedObjects=0& or[Display]bUsePreCulledObjects=0 Once you have copied these lines into your Fallout4.ini (placing bUseCombinedObjects=0 into the Fallout4Custom.ini did not work for me) you can delete the SE.ini file and your Fallout4Custom.ini will then work normally. EDIT: I'm sure you know that using the bUseCombinedObjects=0 option will allow you to disable objects you wouldn't normally be able to, but it comes with the cost of sever performance/fps loss in some places, particularly Downtown Boston. Link to comment Share on other sites More sharing options...
oldbastard42 Posted August 4, 2019 Author Share Posted August 4, 2019 Thankyou @glass1411 - you saved me tons of time, that was the exact answer I was looking for - even though I hadn't asked the question :D. So I can simply delete the hijacked .ini file and all will be well again. Many thanks ;). Link to comment Share on other sites More sharing options...
Glass1411 Posted August 6, 2019 Share Posted August 6, 2019 Your very welcome :) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.