search

rollingrock / EngineFixesVR

Port of SSE Engine Fixes for Skyrim VR
MIT License
67 stars 9 forks source link

v1.20: enabling MemoryManager causes CTD when pressing 'E' key #14

Closed kjack9 closed 3 years ago

kjack9 commented 3 years ago

I am running into a CTD with SkyrimVR near-vanilla, with only USEEP and EngineFixesVR v1.20 enabled. Launching the base game (no SKSE) from ModOrganizer 2. All EngineFixesVR settings are default.

To reproduce:

To prove MemoryManager is to blame:

Other actions also seem to cause this, including named saves, quicksaves, and setini console commands.

Hardware:

I am happy playing without MemoryManager installed for now, but let me know what I can do to help troubleshoot.

Thanks!

kjack9 commented 3 years ago

Attaching a log taken with VerboseLogging enabled. EngineFixesVR.log

rollingrock commented 3 years ago

that's odd. That's basically the exact test I use often for stability.

Can you coc anywhere else? Also are you able to attach windbg and get the crash call stack?

Drakonas commented 3 years ago

Might I add that this thread has a lot of people talking about E crashing SkyrimVR, even before the 1.20 release. https://www.nexusmods.com/skyrimspecialedition/mods/16514?tab=posts

I don't think this stems from the 1.20 release personally.

kjack9 commented 3 years ago

Might I add that this thread has a lot of people talking about E crashing SkyrimVR, even before the 1.20 release. https://www.nexusmods.com/skyrimspecialedition/mods/16514?tab=posts

I don't think this stems from the 1.20 release personally.

I actually suspected DSN at first, since my game was crashing when I used certain voice commands. Also rolled back to the previous version of DSN and it made no difference. Turns out it was DSN making calls that were being crashed by this EngineFixesVR issue, I believe.

@rollingrock, I will learn how to use windbg to get a crash call stack, hopefully tonight. Already have it downloaded, but I'm in new territory.

Thanks for being so responsive.

rollingrock commented 3 years ago

so just so i can understand you guys think that DSN is causing crashes with engine fixes with or without memory manager? I have never heard of that and use DSN myself so I find that strange.

Yeah if you can get a crash stack that would be awesome. All you have to do is after you load your game is run windbg and attach it to SkyrimVR.exe. The only thing that might trip you up is you cannot be using skyrim refocused or whatever it is with it as it will slow you down to a crawl.

Once it crashes windbg will break on where it crashed and you should see the call stack in the window.

kjack9 commented 3 years ago

No, I don't think it's being caused by DSN. The thread that @Drakonas linked to shows a bunch of DSN users saying that their game crashes when you push 'E', or when certain voice commands are used. It is possible that people are using DSN commands that are crashing the game because of EngineFixesVR, but it sure seems to them that DSN is the cause. "I said a command out loud, and the game crashed. Must be a DSN bug!"

It's possible that a lot of people updated EngineFixesVR that week and then started experiencing the crash. Just a theory at this point, but it mirrors my thought process when I first ran into it.

Regardless, I will get the stack trace tonight in a vanilla game and post it here. Thanks again.

rollingrock commented 3 years ago

that is very very weird. I cannot imagine what in engine fixes would cause that. I might have to try to reproduce myself.

I look forward to your crash stack!

kjack9 commented 3 years ago

I am...at a loss. I got WinDbg installed correctly, figured out how attaching to a process works. I figured out that after attaching I have to hit "Go" or the game hangs indefinitely. Great, ready to capture.

The issue stopped...in the middle of me trying to get the crash stack. In fact, I was able to reproduce it 3-4 times while I was figuring out how the debugger worked. Even once with the debugger attached to the process! Then it just stopped happening. Now it doesn't happen with WinDbg, or without, or after a reboot.

Since I can't reproduce this, feel free to close the issue for now. If I figure out how to make it happen again, or if it crops up in my upcoming playthrough, I'll comment back here.

Sorry for the fire drill.