Saika

[Saika]

It was working fine for me too before.I’m trying to figure out if is a permission issue, as I tried to change too many things when I had a conflict between mod organizer and vorpx that Ralf fixed for me.

What do you have on allow for the injector?

Might be a oculus bug maybe, since I did reinstall the software recently and before I never had to relaunch at least 3 times the game for it to work and not be stuck on “tesv is taking too long to load”.

[Saika]

Those lines are repeating hundreds of times when trying to use the injector :
INF: D3D9 Manager: Buffer Resolution: 1080×1200
INF: Display Adapter Description: NVIDIA GeForce GTX 980 Ti
INF: Display Adapter Device Name: \\.\DISPLAY1
INF: Display Adapter Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_674733509ab83d72\nvd3dum.dll
INF: Display Adapter Driver WHQL: 0
INF: Nvidia Driver Version: 37290, r370_00
ERR: D3D9 Manager: initDevice Exception

It’s still working, I can even open the ENB menu while inside the rift.But it is zooming only 75% or so of the screen and then rescaling those 75%.I can see it when I press the middle button.When I zoom into the screen, it ignores a portion of it when going in.

[Saika]

So Ralf did send me the solution and it worked flawlessly :)

I am so happy right now!
It would be good for people who use MO to check if they too have the same issue.I am sure that a lot of people may have that bug but just think the issue is because of mods lowering frame rate!

Thank for you hard work on a Sunday man.You are amazing.I thought all hope was lost because as soon as I mention Skyrim and mod organizer in the same sentence people assumed I was an idiot who couldn’t manage ini’s and just didn’t know how to mod properly :(

[Saika]

Well, usually things differ from games to games, so it’s quite complicated to give basic rules that would work for everything.
First, after installation, you might want to open Configure Vorpx and read the help you will see there (Essential Hints, 1-2-3 game setup, advanced troubleshooting etc).

Then see if the game you want to try has optimized settings, and if yes, click optimize settings and apply.

From my experience, what you should avoid is starting for the first time with too high settings/resolution when the FOV isn’t fixed yet.It made me sick for 2 days the first time (launching a game with 28 fps and 65 fov was the worst idea of my life).
So yeah, try to fix fov issues (usually higher than 100) beforehand and try low settings/resolution too, this way you can get max FPS for your first time and then can press delete in Game to open the Vorpx menu to try and optimize your experience (I recommend internal resolution settings maximized to 2 when you have enough FPS to spare) and image zoom to 1 (usually I see it at 0.95).
You can start to optimize graphical settings after you are done with Vorpx settings in game.

[Saika]

Email sent :)

[Saika]

Thanks you a lot for your hard work :)

I will be looking forward to this.Please don’t tell me the update is months away though because the wait might be unbearable ^^

[Saika]

Well, I was already ready to accept that there is no solution :)
But I will never quite figure why it is only me.

[Saika]

With the right settings and right mods it is possible to mod Skyrim even for VR.
When I didn’t have the issue in june, I had 45 mods running flawlessly on 1280/1440p with Vorpx, with a 55 to 60 fps outside in Whiterun for example and 75 to 90 in interiors.

[Saika]

I immediately checked and the compatibility mode wasn’t checked to begin with.
I did check Windows 7/8 mode to see but it didn’t change anything sadly :(

The thing is, MO is a program that doesn’t change any file in the computer.It supposedly doesn’t touch the registry or anything, it’s just there, inside the game folder.I tried many older versions but it didn’t fix anything.
This is weird, almost unfair that only I have this insane issue.

[Saika]

This is weird, because in May it was working still (at least before I started Skyrim again in September) and I guess I am one of the very few that has an issue launching MO with vorpx since there is absolutely nobody else making topics with that same issue.

The only change that may have happened was the anniversary update from windows in august.

This is devastating news to be honest, because any mod manager that isn’t MO, is, to my frank opinion, pure garbage and should never be considered.From what I’ve read in their forum Nexus Mod Manager is barely working if at all since the new version…

[Saika]

I’ve been checking lots of logs from MO or SKSE but found nothing.
I checked vorpx logs this time, and found differences when launching between skse only and when launching through MO.

Basically, I did find error lines (and other additional lines) from the log when using MO, that aren’t there otherwise if I don’t use MO to launch SKSE.

ERR: _IsWindowsVersionOrGreater Error: GetFileVersionInfo failed.
ERR: MultiMonitorGetConfig not supported in OS < Windows7

ERR: _IsWindowsVersionOrGreater Error: GetFileVersionInfo failed.
INF: D3D9 BufferGrabber initialized. Grab mode: 0 (when I don’t use MO it says Grab Mode: 1)

INF: SettingsUI: Init (this is the end line, it doesn’t appear when not launching through MO).

[Saika]

Thank you for your reply.Actually I made a mistake in the title, it is Mod Organizer of course that I am using, not NMM.Shadows seem to work fine with Mod Organizer though?

As I said, I am killing myself since now 10 days to try and fix it.I have reinstalled everything many times (including Vorpx).So now, it is a completely vanilla game and vanilla Mod Organizer.

Without the rift, the benchmarks I do give the exact same fps and gpu/cpu usage between vanilla launcher/skse and vanilla skse/launcher through Mod Organizer.And absolutely no ctd (I could play for 10 hours straight and have 0 ctd).
But when I use Vorpx, skse/launcher will give me 50 to 60 fps, and then when I launch skse/launcher through MO I get 30 to 40.

I have tried so many things, and can’t find out why Mod Organizer is conflicting with Vorpx.Plus it seems that the more I launch through Mod Organizer, the more likely I am to get CTD’s inside Vorpx, while I will never get CTD’s playing on my monitor.And to fix the CTD’s I have to reinstall Vorpx every-time.This and strangely, my settings for in game skyrim never save after I close the program even though I did the vps save and reload trick.

I want to fix it so bad, Skyrim without Mod Organizer isn’t an option sadly.

[Saika]

I did write that the Ini’s were the same.
Launching skse or the launcher normally will give me around 50 to 60 fps inside the rift.But launching the skse or launcher through MO (we are talking about a vanilla MO with the same INI files) will give me 30 to 40.

[Author]

Posts