0 of 0
About this mod
A log scanner for Buffout Crash Logs, a time-saver if I ever did see one!
- Permissions and credits
Name:
Buffout Scanner (Scans things relevant to Buffout)
Problem(s):
After a crash one is left searching for the buffout log files, it can be a test of sanity to then manually scan the stacks of each one, trying to remember ALL of the, esp and esl, mentioned in the given stack, and compare to multiple other logs in their head, and even then after doing so many of the logs, there is the issue of hallucinating and not seeing where the stack becomes the next section, and basically it can be stress and take time, and result in wrongful removal of mods, hours/days lost, etc.
Solution(s):
So, one would MANUALLY install my tool in any folder they like, though I advise the game dir, its fine in the game dir. After installing one run the program, navigate the menu and HAZAAH, quick as a lightning bolt, the ACTUAL results are right there, WOW, isnt that convenient. Check the pictures if your confused still what it does.
Demonstration:
Video on YouTube: `Buffout Scanner 002 Demonstration (a FallOut 4 Tool) Edit 4`...
...this needs to be updated as we are now on 005, but mostly the same.
Instructions:
Remember, its a program to make the process of debugging mod collections simpler, not replace the user's role in determining what should happen with mods...
1. You may extract the files to any folder, but a good choice is either the, f4se logs or fallout 4, folder. if added scripts to logs it will not have to read the registry for your `My Documents` location, and if put anywhere else it will work just fine, its portable from what I can tell.
2. You are supposed to run the batch by Double-Left Click on the `Batch_Scanner.bat` file, ensure NOT to, right-click run it as Admin or run the Python file, if ran correctly, the batch will launch the Python script.
3. The user is expected to reduce their log files to specifically the ones they wish to scan. When you run the program, it provides the option to open the log folder, the user must reduce the `crash_####_##_##.log` logs to only the ones they desire to scan, before scanning.
4. The user must run the analysis with `R`, this will display a report like shown in the pictures, the one at the top of the list is most frequently found and bottom the least. The one at the top is likely the culprit, but ensure there is clear distinction from producing enough crash log material first.
5. When one finds the mod that is crashing the most often, then take a look at, the relevant mod and the mods it has relevance too, reinstall, look at the options, ensure the requirements are covered, do things, or just remove it, then stability test FallOut 4, and then...
- if and when you are sure, its stable then delete the logs, and continue playing, you do not want to contaminate any further crash logs,
- if the program crashes still, then continue the process of accumulating crash logs, take a look at the other mods with high scores, and ensure to go to other areas in the game, to remove common elements from the crash logs.
6. If there is an issue with my program itself, then it will be reported to the user somehow at the appropriate point.
Notation(s):
- For clarification, Buffout Scanner will only count 1 esp/esl per script per filename, ie in the case of the picture, there were multiple crash logs that had the `fall damage` esp/esl, this does not mean multiple mentions in 1 file.
- Buffout Scanner does read a registry value to determine where `My Documents` is, and yes that means if you are using a custom location for `My Documents` (ie have it on a non-system drive), then it will correctly detect the location.
- This program was written in Notepad++, and was tested on a Pc with early windows 10 non-wsl with, Python 3.11.0 and Buffout/Buffout NG.
Requirements:
You must have this OS...
- Windows 7-11.
You must have these things installed...
- Buffout mod for fallout 4,
- Python 3 or higher.
You must have these things Enabled...
- Scripting Host.
Development:
The program represents a somewhat early release, there is currently an issue with...
- Determine if the `Buffout NG Fallout4 (1.10.984) PDB` optional esp for `Buffout NG` is having a different format of output, as it says something to that end "Needed for better debugging of crashlogs."
Structure:
.\Buffout_Scanner.bat
.\buffout_scanner.py
Warning(s):
- Enable scripting host if it is not already. You can do this through programs such as "AntiSpy-XP/10/11", or the likes, its the setting that enables script(s) to run such as written in, python or batch or powershell, but you probably have already done this I hope, but its covered in the video, but dont go "ExPeRiMeNtInG" with, `xp-antispy` or `system modification`, if unsure what it will do.
Buffout Scanner (Scans things relevant to Buffout)
Problem(s):
After a crash one is left searching for the buffout log files, it can be a test of sanity to then manually scan the stacks of each one, trying to remember ALL of the, esp and esl, mentioned in the given stack, and compare to multiple other logs in their head, and even then after doing so many of the logs, there is the issue of hallucinating and not seeing where the stack becomes the next section, and basically it can be stress and take time, and result in wrongful removal of mods, hours/days lost, etc.
Solution(s):
So, one would MANUALLY install my tool in any folder they like, though I advise the game dir, its fine in the game dir. After installing one run the program, navigate the menu and HAZAAH, quick as a lightning bolt, the ACTUAL results are right there, WOW, isnt that convenient. Check the pictures if your confused still what it does.
Demonstration:
Video on YouTube: `Buffout Scanner 002 Demonstration (a FallOut 4 Tool) Edit 4`...
...this needs to be updated as we are now on 005, but mostly the same.
Instructions:
Remember, its a program to make the process of debugging mod collections simpler, not replace the user's role in determining what should happen with mods...
1. You may extract the files to any folder, but a good choice is either the, f4se logs or fallout 4, folder. if added scripts to logs it will not have to read the registry for your `My Documents` location, and if put anywhere else it will work just fine, its portable from what I can tell.
2. You are supposed to run the batch by Double-Left Click on the `Batch_Scanner.bat` file, ensure NOT to, right-click run it as Admin or run the Python file, if ran correctly, the batch will launch the Python script.
3. The user is expected to reduce their log files to specifically the ones they wish to scan. When you run the program, it provides the option to open the log folder, the user must reduce the `crash_####_##_##.log` logs to only the ones they desire to scan, before scanning.
4. The user must run the analysis with `R`, this will display a report like shown in the pictures, the one at the top of the list is most frequently found and bottom the least. The one at the top is likely the culprit, but ensure there is clear distinction from producing enough crash log material first.
5. When one finds the mod that is crashing the most often, then take a look at, the relevant mod and the mods it has relevance too, reinstall, look at the options, ensure the requirements are covered, do things, or just remove it, then stability test FallOut 4, and then...
- if and when you are sure, its stable then delete the logs, and continue playing, you do not want to contaminate any further crash logs,
- if the program crashes still, then continue the process of accumulating crash logs, take a look at the other mods with high scores, and ensure to go to other areas in the game, to remove common elements from the crash logs.
6. If there is an issue with my program itself, then it will be reported to the user somehow at the appropriate point.
Notation(s):
- For clarification, Buffout Scanner will only count 1 esp/esl per script per filename, ie in the case of the picture, there were multiple crash logs that had the `fall damage` esp/esl, this does not mean multiple mentions in 1 file.
- Buffout Scanner does read a registry value to determine where `My Documents` is, and yes that means if you are using a custom location for `My Documents` (ie have it on a non-system drive), then it will correctly detect the location.
- This program was written in Notepad++, and was tested on a Pc with early windows 10 non-wsl with, Python 3.11.0 and Buffout/Buffout NG.
Requirements:
You must have this OS...
- Windows 7-11.
You must have these things installed...
- Buffout mod for fallout 4,
- Python 3 or higher.
You must have these things Enabled...
- Scripting Host.
Development:
The program represents a somewhat early release, there is currently an issue with...
- Determine if the `Buffout NG Fallout4 (1.10.984) PDB` optional esp for `Buffout NG` is having a different format of output, as it says something to that end "Needed for better debugging of crashlogs."
Structure:
.\Buffout_Scanner.bat
.\buffout_scanner.py
Warning(s):
- Enable scripting host if it is not already. You can do this through programs such as "AntiSpy-XP/10/11", or the likes, its the setting that enables script(s) to run such as written in, python or batch or powershell, but you probably have already done this I hope, but its covered in the video, but dont go "ExPeRiMeNtInG" with, `xp-antispy` or `system modification`, if unsure what it will do.