Description
This tool is based on How To Install Buffout 4 And Resolve Crash Logs article.
It automatically scans Buffout 4 crash logs and gives you detailed information on detected settings and mods that might be causing the crash, along with additional steps to take depending on what it finds. Currently implemented logic checks for (more than) 225 different things.
Documentation
For documentation on reading Buffout 4 crash logs, see Poet’s How To Install Buffout 4 And Resolve Crash Logs resource.
Support
Poet also provides support and update information on their Collective Modding Discord channels in: Poet Guides & Help.
For additional help reading Buffout 4 crash logs, visit this Collective Modding Discord channel: fo4-crash-logs and post your logs in the appropriate thread.
An invite to the server can be found on the Collective Modding resource page.
Additional Resources
Some additional MRC resources from Poet:
If you are having trouble running the scanner with the latest version of Buffout 4 logs, you can try this fork beta version by evildarkarchon. As far as i know this is a temporary fork until Poet's scanner version is updated or Buffout 4 is. Not sure which at this time.
Updates
NEW FEATURES - PART 1
- Automatically checks for its own updates every 7 days.
- Warns you if MS OneDrive is overriding your Documents folder location.
- Automatically grabs all crash log files from the Script Extender folder.
- Plays a short notification sound once crash logs and game file scans are done.
- Various settings were moved to YAML files for much easier access and editing.
- Various functions and tasks are now automatically logged to CLASSIC Journal.log
- Extended scan support for crash logs from new and old Buffout 4 versions.
- Extended compatibility and features for Virtual Reality (VR) version of the game.
- VR Mode setting that will prioritize scanning files from the VR version of the game.
- Simplify Logs setting that removes some useless and redundant lines from crash log files.
- Show FID Values setting that will look up FormID values for Possible FormID Suspects.
- Papyrus Log monitoring built into the GUI. Also plays a warning sound when things go bad.
- Buttons for quick access to the DDS Texture Scanner, Wrye Bash and BethINI Nexus pages.
Ability to scan all mod files from your Staging Mods Folder to detect these issues
- Check if DDS texture file dimensons are not divisible by 2 (Ex. 1024 x 1025)
- Check if texture files are in the wrong format (TGA or PNG instead of DDS)
- Check if sound files are in the wrong format (MP3 or M4A instead of XWM or WAV)
- Check which mods have custom precombine / previs data (so you can load them after PRP)
- Check which mods have custom animation file data (to narrow down Animation Data Crashes)
- Check which mods have copies of Script Extender files (to prevent problems and crashes)
- Mod files scan will also move any found fomod and readme files to the CLASSIC Misc folder.
- You can also generate FormID values for all active mods, so AUTOSCAN reports can use them.
AUTOSCAN reports will now additionally provide the following information:
- List all mod INI files and settings that have enabled game VSync, if any.
- Show how many times each Possible FormID Suspect appears in the crash log.
- Warn you if Fallout4.ini, Fallout4Prefs.ini or Fallout4Custom.ini become corrupted.
- Notify you when Buffout 4 fixes in the TOML config file get changed or disabled.
- Show an additional warning if you went over the Plugin Limit (254 esm/esp).