MarkG

[MarkG]

BTW, one possibly unusual thing is that I have two different Mod Organizer installs: one for VR, and one for flat games. Could that confuse your code that’s looking for the profiles?

[MarkG]

Yeah, looks like I’m running 1.3.11.

To summarize:

1. This worked (aside from the usual modded Skyrim crashes) just before Christmas.
2. It doesn’t work since Vorpx updated itself.
3. Unmodded Skyrim didn’t work after the latest VorpX update, but I did the ‘reset profile to default’ thing and it did start up after that.
4. Running with Mod Organizer just gets a flash of black, then crashes.
5. Running with Mod Organizer, no mods enabled, and the .ini files from the unmodded Skyrim still doesn’t work. So it’s Mod Organizer, not the mods.
6. Enabling ‘run as administrator’ doesn’t help.

Literally the only things that have changed on that computer are VorpX and possibly new Oculus software; I haven’t checked whether that’s updated lately.

So something’s changed in this version that broke something that was working fine before. Since you did explicitly made changes to support Mod Organizer, perhaps something you changed isn’t compatible with my Mod Organizer installation for some reason.

[MarkG]

So, I decided to try looking at this today. VorpX downloaded another update and… Skyrim no longer works at all, with or without Mod Organizer.

I just get a brief flash of a black window, then it shuts down with no error message. Skyrim works fine if VorpX isn’t running.

[MarkG]

I’ve never needed to run it as administrator before.

Do you have a working .ini file that I could try?

[MarkG]

I was just looking at the recent change logs, and I wonder if this could be related to the changes to detect game overlays? I believe SKSE may use the Steam overlay to load itself, so there could be some kind of conflict there.

I turned that option off in the VorpX config, but it didn’t stop the game crashing.

[MarkG]

I created a brand-new VorpX profile

That should, obviously, have been ‘Mod Organizer profile.’

[MarkG]

Yep, they broke it somehow.

Today I thought, ‘I know, I haven’t played Skyrim in ages, let’s have a go’. But, lo, VorpX must update, which is so often bad news.

And so, it turned out that VorpX no longer works with Skyrim and Mod Organizer. My Mod Organizer profile works fine without VorpX. Skyrim works with VorpX without Mod Organizer. I created a brand-new VorpX profile with only the default Skyrim files, and it still crashes on startup when run with VorpX.

Can you fix this, please? This is pretty much the only thing I use VorpX for, so breaking it has made the software pretty much useless for me.

Alternatively, can you give me a way to go back to a previous version, as I was quite happy with the working setup I had before this.

[MarkG]

I use one of the first-person body mods: I forget which one. That fixes the hands.

However, it conflicts with DirectVR, so it’s not an ideal solution.

[MarkG]

I found that actually enabling ENB graphics options made everything look flat. That’s why I disabled them all in the end and just used the memory manager.

[MarkG]

I didn’t do anything special and it works for me, except that the first time I start Skyrim, it comes up on the monitor instead of VR: I get the ‘TESV.exe is taking a while to start’ message, but VorpX never switches to VR.

The second time, it usually comes up with no problems.

I also run with the ENB Injector, but all ENB graphics options disabled, to get the ENB memory manager to prevent mod crashes.

[MarkG]

BTW, that did solve the problem. I’m getting 90fps (or close to it) in most interiors now.

[MarkG]

See my thread a few below this one for why Skyrim may be limited to 45fps in VR.

I’ve seen it get up to around 80 fps with a GTX970 and i7-3770, but it’s highly variable. Just turning a few degrees can take it from 80fps to 30fps.

[MarkG]

Thanks! I forgot that I reset the VorpX configuration to defaults when I was having trouble starting up Skyrim a while back, and maybe I’d had that turned off before.

I’ll try both and see which works best.

[MarkG]

I wondered whether this might be something related to ASW (which I don’t believe I have on Windows 7). So I downloaded the Oculus debug tool and set ASW to ‘off’ instead of ‘auto’, but that made no difference. Both fps and direct fps max out at 45 with the current version of Vorpx and the current Oculus software.

[MarkG]

Actually, there’s a .ini hack to make physics work at >60fps.

But Skyrim is CPU-limited, not GPU-limited. Even when I was running on a GTX 970, the Vorpx internal resolution scaling made no different to frame rates, but a huge difference to image quality.

[Author]

Posts