Menu
What's new
By:
Filters
the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Buffout 4 help

Bored Peon

Bored Peon

Well-Known Member
Banned
Messages
1,786
I installed Buffout 4 the other day to help with some CTD reports. However I can not find a single log it created.
I went through the posts and such on the Nexus and could not find anything useful.

Is there someplace it belongs in the load order?

How about an example of the filename it creates so I can try searching for it? Since it does not appear in the folder it is supposed to be in.
 
Sort by date Sort by votes
Bored Peon said:
Nah, using Vortex. Pretty sure I probably missed some vague instruction somewhere...
Click to expand...
I'm not familiar with vortex, is it possible the address library .7z isn't setup correctly for vortex to install? There is an F4SE folder inside the zip, that needs to end up in your fallout4\data directory, if its going in the directory with the fallout4.exe it isn't going to work.
 
Upvote 0 Downvote
don't use vortex to download the preloader put it in the fallout 4 main folder your self. also wait saves and any of the auto saves are bloat central hard saves are the only way to go it prevents file size bloat and prevents issues down the line. pretty sure there is a mod or tool that creates hard saves instead of auto saves but i just turn off any of the save on wait save on fast travel and save in pipboy options.
Nosimo said:
I'm not familiar with vortex, is it possible the address library .7z isn't setup correctly for vortex to install? There is an F4SE folder inside the zip, that needs to end up in your fallout4\data directory, if its going in the directory with the fallout4.exe it isn't going to work.
Click to expand...
vortex works fine for the address library but the xse preloader needs to be done the old way directly into the main fallout folder.
 
Upvote 0 Downvote
XxA1xX said:
also wait saves and any of the auto saves are bloat central hard saves are the only way to go it prevents file size bloat and prevents issues down the line. pretty sure there is a mod or tool that creates hard saves instead of auto saves but i just turn off any of the save on wait save on fast travel and save in pipboy options.
Click to expand...
I knew about this,but couldn't remember why. Now I'm curious. What bloat? I just thought they were buggy...
 
Upvote 0 Downvote
msalaba said:
I knew about this,but couldn't remember why. Now I'm curious. What bloat? I just thought they were buggy...
Click to expand...
when the save file size starts getting larger it can cause infinite loading screens longer loading times or flat out crashing for me when its around the 40 to 50 mb size for some reason. the auto saves and idk why are always larger then a hard save even in the exact same area spot time. lets say my hard save is 18mb my auto save and exit save with everything the same is 21mb only real answer i remember reading about is save size bloat when using them. buffout 4 seems to fix the file size limit though but i no longer use any auto saves quick saves or exit saves and it seems to keep the game more stable this way.

my best guess is that the auto saves are referencing more stuff in the background that isn't needed to load a game. like if its an exterior save its trying to also have interior stuff. there's a couple of places i remember reading up about this long ago but ive found for me not using them keeps everything more stable.
 
Upvote 0 Downvote
Upvote 0 Downvote
Bored Peon said:
Ok, finally go this to work, lol. Thanks to some of the comments from you guys I was able to figure out what was not done right.

First off you need to have all the required files (which aint mentioned as part of the installation.)
Microsoft Visual C++ Redistributable for Visual Studio 2019
xSE PluginPreloader F4
Address Library for F4SE Plugins
TBB Redistributables

Once you have all four it works.

You would think there would be a readme or a sticky post somewhere pointing all this out.
Click to expand...
You could be awesome and write one up in the tutorial section here... ;) It could be beneficial to others in the community that probably wouldn't want to share your struggles. At least you got that sorted :agree:
 
Upvote 0 Downvote
XxA1xX said:
quick saves
Click to expand...
I don't mean to necro, but curiosity killed me...

Now I need to actually look at my save files... I'm lazy and religiously spam the F5 key cause its too much work to hit the esc key...
 
Upvote 0 Downvote
msalaba said:
I don't mean to necro, but curiosity killed me...

Now I need to actually look at my save files... I'm lazy and religiously spam the F5 key cause its too much work to hit the esc key...
Click to expand...
yeah I need to reread up some but I’m still almost sure it’s a bug related to save file size and that auto saves cause larger save file size.
Bored Peon said:
Now I just need to figure out wtf I am looking at in the log, lol.
Click to expand...
I’m not 100% on them but normally you can see a pattern on the read out. Say a mod causes crashing and the mods named something like robo crack 35 it will give you a readout saying something like
1 robo crack 35 caused blah blah
2 fallout 4 ext
3 void
4 robo crack 35 misaligned item function
5 blah blah blah.

you just have to look for the patterns in the call stack ( call stack ) call stack is what it’s called that’s is giving you the readout of stuff going on frame to frame.
 
Upvote 0 Downvote
XxA1xX said:
yeah I need to reread up some but I’m still almost sure it’s a bug related to save file size and that auto saves cause larger save file size.

I’m not 100% on them but normally you can see a pattern on the read out. Say a mod causes crashing and the mods named something like robo crack 35 it will give you a readout saying something like
1 robo crack 35 caused blah blah
2 fallout 4 ext
3 void
4 robo crack 35 misaligned item function
5 blah blah blah.

you just have to look for the patterns in the call stack ( call stack ) call stack is what it’s called that’s is giving you the readout of stuff going on frame to frame.
Click to expand...
Yeah, last code I learned was DOS.
So...
20200418144654_1.jpg
 
Upvote 0 Downvote
Bored Peon said:
Now I just need to figure out wtf I am looking at in the log, lol.
Click to expand...
Bored Peon said:
Yeah, last code I learned was DOS.
Click to expand...
Super secret code that when you decipher it you will end up finding robo crack 35's super secret stash... ROFL...
You guys seriously! Its too early in the morning to be cleaning up coffee. :clap

There is a ray of hope! If I can learn Papyrus, I have the faith that you will be able to decipher the log. Or maybe @Whisper could create a script for you to find the relevant data...
 
Upvote 0 Downvote
msalaba said:
Super secret code that when you decipher it you will end up finding robo crack 35's super secret stash... ROFL...
You guys seriously! Its too early in the morning to be cleaning up coffee. :clap

There is a ray of hope! If I can learn Papyrus, I have the faith that you will be able to decipher the log. Or maybe @Whisper could create a script for you to find the relevant data...
Click to expand...
Sorry I just use random names and stuff that way I don’t offend somebody if I giving a name similar to their mod. Also I’m not good at picking random names.
 
Upvote 0 Downvote
GuardianMF said:
You need the two main files from Buffout 4 (the other one is called TBB Redistributables), the requirements, C++, and change the load method to OnThreadAttach in the xSE PluginPreloader.xml if you're using MO2. Some files go to the root directory, some in the F4SE folder.
Click to expand...
sorry for necro post. But I have been able to play good so far but now I am getting dynamic navmesh/scrap heap errors on my crash logs in buffout. I do have all the requirements but I didnt know about the OnThreadAttach in xse plugin preloader.xml

Could you pls elaborate on how to do this exactly? I opened the file and cant tell what to do next. I do use MO2.
 
Upvote 0 Downvote
The scrap heap is a settlement thing with workshop mode I’d guess power related since that always seems to be the big issue that causes crashes. The dynamic navmesh could be a plot that isn’t navmeshed correctly or a mod that messes with navmeshing. My first place to start though is checking the power grids in your settlements , as well as refreshing plots to make sure they are functional.
 
Upvote 0 Downvote
Jinncrazey said:
sorry for necro post. But I have been able to play good so far but now I am getting dynamic navmesh/scrap heap errors on my crash logs in buffout. I do have all the requirements but I didnt know about the OnThreadAttach in xse plugin preloader.xml

Could you pls elaborate on how to do this exactly? I opened the file and cant tell what to do next. I do use MO2.
Click to expand...
You're getting crash logs, which suggests that Buffout 4 is working...
See XxA1xX's post for troobleshooting.

To answer your question:
You can open the file with Notepad and change
<LoadMethod Name="OnProcessAttach">
to
<LoadMethod Name="OnThreadAttach">
 
Upvote 0 Downvote
You must log in or register to reply here.
Top