Fatal Exception When using BodySlide as Exceptionable in MO2

[dakotaraptorsaurus]

I've had Bodyslide downloaded in MO2 for a while and used it as an exceptionable but now it says that Fatal Exception has occurred. I've tried redownloading it multiple times to no avail. I made sure that the path leads to the Data Folder of my main Skyrim folder but I don't know what to do at this point. I also excluded the Bodyslide folder from my Antivirus. But I'm not sure if a mod is somehow related to it as I have not heard of any mods that can inhibit Bodyslide's functions.

Edited November 14, 2022 by dakotaraptorsaurus

[traison]

Post the app crash entry from the windows event viewer, it may contain more info.

[dakotaraptorsaurus]

4 hours ago, traison said:

Post the app crash entry from the windows event viewer, it may contain more info.

I try redoing the crash but it doesnt show up on the Event Viewer. It does however, show up on the Bodyslide Log file, which created a deug Report somewhere Else. I cant make sense of it myself though. But When I look at the data section of MO2, it says that the virtual path is /Data/CalienteTools/Bodyslide/Bodyslide64.exe and the real path is everything that came before /Data/. Could this have anything to do with it always reaching fatal exception?

 

[traison]

Don't know. I was hoping the app crash entry would have contained the error code, or anything else really. If you found something related to this that you can't make sense of, post it here.

Edited November 15, 2022 by traison

[dakotaraptorsaurus]

15 hours ago, traison said:

Don't know. I was hoping the app crash entry would have contained the error code, or anything else really. If you found something related to this that you can't make sense of, post it here.

Here is the .xml Debug file that I was talking about. 

Also, in the Log File it said something about "Process Context Description" under "A debug file has neem made under /yadda/yadda/yadda"

BodySlide x64.xml

Edited November 16, 2022 by dakotaraptorsaurus

[traison]

Unfortunately I can't get close to the exception address with a debugger because of how the mo2 vfs works. I can't get it to locate the presets etc. However, I did get some strings out of it:

 

LoadSliderSets

OutputPath

OutputFile

 

With that, my guess is that you have an outfit (or other bodyslideable object) that is causing issues. I can't say which file this would be, so you'll have to go through them and disable them one by one.

 

Edit: Considering this may have something to do with paths. Maybe start with mods that use a foreign language, such as if you're on a western version of Windows but you have chinese mods, this may be an issue.

 

Edit again: Path length may be an issue too, I think Win 10 is still in some situations limited to 255 characters (MAX_PATH constant). Though I don't think that produces an error with code 0x5 (ERROR_ACCESS_DENIED). Also in case you're wondering, 0xc0000005 is translated to 0x5 and ACCESS_VIOLATION basically means the same thing.

Edited November 16, 2022 by traison