In this release... - Logs will be re-listed before scanning, thus user can actually load the tool, open folder, delete irrelevant logs, then scan, without issue arrising of missing files. This enables session use as originally intended.
What I have been getting is a box popping up saying "process finalized, exiting in 3 s.." then closing. I have Python 3.13.3 installed and script hosting enabled. I have tried running the file from the game folder, log folder, f4se folder, and the desktop. I still get "process finalized, exiting in 3 s.." everywhere I have tried. So any idea what I might be missing? Thank you for the help.
[Error] (I don't know how to make these symbols but large lower case r, GBP sign, u with a ^ on top of it) Could not find buffout_scanner.py in: M:\Program Files Alternate\Buffout Scanner.
1. Remember to report bugs to `Bugs` section, this is the `Posts` section.
2. I have now made demonstration video, to cover the basics, ensure to cover the requirements, but there are some things to check if the issue persists ... - Possibly you have not, installed python or enabled scripting host, (see video if required). - Possibly, unusual system settings. - Possibly you tried to run the python script instead of the batch, the program is ran via the batch. - some issue elsewhere (its a simple program using built-in python features). - Are there error logs `crash_####_##_##.log` present in the `~\My Documents\My Games\Fallout4\F4SE` folder?
3. If issue persist still, some information I require... - Do you have custom location for `My Documents` folder or if you are using default one. - Where are you running the script from? Logs, FallOut4, Other? - Windows version (from my understanding any python over v3.00 should work).
2. I was using Version 1 which didn't seem to have the .py file in it, now that I have Ver 2 installed it's running.
3. The location for my documents is an odd one. I have my standard documents folder on my M: Drive, and then I still have C:Users\"Me"\My Documents\Games\etc which I think might be confusing it since it's saying that it can't locate the directory. Likely because the path its using is just %userprofile%\documents\my games rather than the one I listed above. I tried looking at the code and seeing if it was a simple line adjustment, but I am NOT familiar enough with Python to make said adjustment it would seem.
Oh, and to answer the last question, Windows 7 and Python 3.8.6.
Again much apologies for the packaging of v001 to all whom tried it, and am glad it is now working fine for other people on their system(s), thanks for confirmation.
Is there any way to make this run from within the same folder as the crash logs similar to C.L.A.S.? That way it doesn't have to search for the directory it could just scan files local to it?
Now on version 005... - If ran from logs folder, then will not provide option to open logs folder. - It DPO to the script folder at start, just to fool-proof things a bit. - It also makes sure the user did not run with Admin, again fool-proofing.
Now on version 004... - At user request; if put in Logs folder then will detect crash logs and know its in the logs folder, and so NOT then read the location from the registry, and just work in its own folder. - It will continue to work normally otherwise in other folders, for my preference its run from fallout 4 folder for, habit and convenience.
Thanks so much for creating this mod. I used something like it before the NG update and could never remember its name or find it so it was a __huge__ pain in the @ss combing through crash reports one at a time. Downloading it now with fingers crossed. This is a hugely beneficial tool for anyone trying to create a reasonably stable mod collection.
Update: This works fine in a custom folder - I use C:\Gaming\Tools for all of my modding tools. I ran it from there and it quickly told me what I already knew - Functional Displays causes crashes. In short - "it just works." I already have python installed and use the default locations for Buffout, so I had zero configuration.
15 comments
In this release...
- Logs will be re-listed before scanning, thus user can actually load the tool, open folder, delete irrelevant logs, then scan, without issue arrising of missing files. This enables session use as originally intended.
it works,
method followed:
1 - Copy the .bat and .py file in the folder that contains the crash files.
2 - Run the .bat file
Sorry for my bad english
Thanks to the Author
Also didn't work when I put it in the directory.
1. Remember to report bugs to `Bugs` section, this is the `Posts` section.
2. I have now made demonstration video, to cover the basics, ensure to cover the requirements, but there are some things to check if the issue persists ...
- Possibly you have not, installed python or enabled scripting host, (see video if required).
- Possibly, unusual system settings.
- Possibly you tried to run the python script instead of the batch, the program is ran via the batch.
- some issue elsewhere (its a simple program using built-in python features).
- Are there error logs `crash_####_##_##.log` present in the `~\My Documents\My Games\Fallout4\F4SE` folder?
3. If issue persist still, some information I require...
- Do you have custom location for `My Documents` folder or if you are
using default one.
- Where are you running the script from? Logs, FallOut4, Other?
- Windows version (from my understanding any python over v3.00 should work).
2. I was using Version 1 which didn't seem to have the .py file in it, now that I have Ver 2 installed it's running.
3. The location for my documents is an odd one. I have my standard documents folder on my M: Drive, and then I still have C:Users\"Me"\My Documents\Games\etc which I think might be confusing it since it's saying that it can't locate the directory. Likely because the path its using is just %userprofile%\documents\my games rather than the one I listed above. I tried looking at the code and seeing if it was a simple line adjustment, but I am NOT familiar enough with Python to make said adjustment it would seem.
Oh, and to answer the last question, Windows 7 and Python 3.8.6.
- If ran from logs folder, then will not provide option to open logs folder.
- It DPO to the script folder at start, just to fool-proof things a bit.
- It also makes sure the user did not run with Admin, again fool-proofing.
Note: Should be robust now, thanks for feedback.
- At user request; if put in Logs folder then will detect crash logs and know its in the logs folder, and so NOT then read the location from the registry, and just work in its own folder.
- It will continue to work normally otherwise in other folders, for my preference its run from fallout 4 folder for, habit and convenience.