Open LostDragonist opened 4 years ago
Something to note is that it worked once on initial install of everything and then not again (restarting PC did not help). There might be some file that was created during the first run that broke all subsequent runs.
Same for me. When I extract MO2 2.3.2 into a new folder, it works until I close the program. After that, the game doesn't start at all with NVAC enabled. No error messages or anything, and the NVAC log doesn't say anything.
It works with 2.2.2.1, though.
Some users who report this say it's related to a Windows 10 update. So for me, I was able to play with NVAC on 2.3.2 for a couple weeks, before some update happened and it stopped working.
EDIT: I should also mention I am on the Steam version of Oblivion, so it is happening there as well. (Not just GOG)
It's possible, I recently updated to 2004.
Oh wait this looks like the issue I've been having with #1228 I'm getting the spinlocks, but it works for some reason when I launch via the launcher rather than directly via oblivion.exe
I've been able to reproduce with no mods enabled aside from nvac crashDumps.zip mo_interface.log usvfs.log
What's really confusing is the fact that by launching the game via OblivionLauncher.exe
, it works, and I have the obse force loading setting configured as seen in 1228
Maybe usvfs handles subprocesses differently to the directly launched process
Is there any update on this bug?
No, I don't have a setup to reproduce the issue or time to set one up.
I reproduced it with a virtually completely clean setup. You just need to set up OBSE, and then install the NVAC plugin
I've actually run a pretty modded setup with NVAC a couple times successfully. Oblivion still crashes sometimes because it's Oblivion, but I can load the game even with massive texture packs, multiple OBSE mods, and an ENB/ReShade preset.
That being said I'm running a pretty 'new' build which should be similar to the nightly builds in Discord. Maybe give those a try and see how it works. I'm not sure why the latest release would be different though, USVFS was not changed since then.
@Silarn what OS are you rocking? And are you using the GOG version or the Steam version of Oblivion?
Just coming back about ~1.5-2 months later to report this is still an issue in 2.4.0 alpha2, Windows 10 build 19041.5722 (version 2004) and NVAC 7.5.1.0 (from 2016).
I am willing to help in any way I can, testing custom files/versions of MO2, getting any additional logs, whatever. Hit me up on Discord if you need me, Night Thastus #6641. Or on reddit, /r/Night_Thastus
This may be fixed in the latest dev build, 2.4 Alpha 3.2. It is for me at least.
It's broken for me in 2.4 Alpha 3.3.
It's broken for me in 2.4 Alpha 3.3.
Odd, it's working for me in alpha 3.3. What version of Windows are you on? I'm on 20H2.
Can anyone test 2.4.0alpha5+?
Still is broken. Tested on 2.4.1RC2. It says it is running but nothing ever opens. The process eventually must be killed.
Can confirm that it's still broken even with v2.4.2rc1.1. Just switched to WIndows Insider build and now my Oblivion doesn't launch with NVAC enabled, process just gets stuck. Bug Fixes in v2.4.2rc1.1 patch notes mention Windows Insider improvements but this issue is still there.
Reported by Night Thastus on discord
MO 2.3.2 GOG Oblivion OBSE NVAC 7.5.1.0
Trying to launch the game with the above stuff results in a spinlock and the game never launches. Note the recursion/looping in nvac.log.
mo_interface (24).log usvfs-2020-09-02_03-30-37 (1).log nvac (1).log