Szabby

[Szabby]

Hard to find the solution, becouse I would have to see the issue with my own eyes in order to be able to find out what the problem is.

Would you please answer the following questions:

1. What version of SDK did you install?
2. Which lenses do you use, A or B?
3. Did you go through the settings demo in OR serivce software?
4. While in the game, did you try to alter IPD settings?
5. Is your VorpX 0.7.5?
6. What FOV do you use in Skyrim?
7. Do you use geometry 3D or Z-buffered 3D in Skyrim?

As a matter of fact, I don’t think you problem is hard to solve. Oculus Rift is still an experimental device, so it needs to be constanlty tested to get the experience you desire. For example, I had tons of problems with STALKER games, it took me about 2 weeks to make them run properly, but now everything is great. So don’t worry.

[Szabby]

One more note. Mods normally don’t have anny effect on your chances to play games on the Rfit. But since mods are different, sometimes it happens, that they affect the rendering methods pretty much, becouse they contain a deeper modification of the code and executables themselves (like for example some serious STALKER game mods). So you could try to uninstall your mod too (or make a fresh game install) and give it a try.

[Szabby]

Hi!

Since I never had any problems with Skyrim on DK2, assuming, that you have the latest Oculus SDK, runtime and VGA drivers installed, I must suspect, that your issue is due to some graphics settings, not particularly in VorpX but in Skyrim. For me it’s like an issue related to shaders by the way.

So I suggest:
– turn on “fix chromatic aberration” and “shader antialising” in VorpX.
– go through all graphics options in Skyrim’s menu, and try to switch them off one by one.

There were many cases, when switching off one single graphichs option ingame solved all my issues at ince. It must work for you too!

Apart from that, I’m afraid I don’t know anybody else trained in this matter, sorry.

Let me know, if you found the source of the problem.

[Szabby]

Well, if the latest Oculus SDK and runtime are properly installed, I suggest to refresh VGA driver, if possible. Make sure, you play in extended mode and try to pause Oculus service as well. If you still have the issue, you may try VR Game Manager too.

To be honest, this is a weird problem. I faced this issue only once with Alien Isolation. I reinstalled the game, I tried every possible solutio, but I just couldn’t get rid of the “3 coulour” thing. And the wildes part is, that after about 10 tries, suddenly everything went back to be normal, however, I didn’t try anything new, only desperately continuing to make it work on and on. If I remember well, I think at a point I tried to switch the Rift off and than back on before launching the game.

Sorry, but other than that I don’t have any more useful ideas at the moment…

[Szabby]

Is Skyrim the only software, where you face this issue?

[Szabby]

Hi!

This is an effect caused by the lenses of the Rift, that shifts RGB colours.

While ingame, press del to get VorpX menu.

There is an option to get rid of this effect (fix chromatic aberration).

Hope, it helped!

[Szabby]

Is your rift set to extended mode?

[Szabby]

Hi Kutter!

Let me help you with own experiences. When I got my DK2, I was in the exact same situation as you are now: nothing worked!

But I didn’t give up, I googled a lot, I e-mailed a lot with people, who had much more experience, and now, everything works fine and I’m satisfied.

So be patient, Oculus at this point is far not that easy “plug and play” as many people think. But if you make your time to learn, soon everything will be fine.

I mostly could help to you in certain FPS games, but one advise still can help: it’s far not only about “extended” or “direct”. So:

1. You have to set your DK2 properly in Windows control panel, such as the layout of the screens, forcing 75 Hz, making sure to set to 1920×1080, etc.
2. You have to have the important softwares properly installed, like Oculus runtime AND SDK (even if you are not a developer!).
3. Sometimes installing some additional softwares, drivers, making some settings in GPU control panel are also strictly important.

I hope it helped a bit.

However, if you have any questions, don’t hesitate to ask.

[Szabby]

Hi Ralf!

Thanks!

Like I said: all STALKER games work fine on DK2 and VorpX!

What I wanted to point out was, that Lost Alpha works only in “2D” and only in DX9. I suggested you to focus on Lost Alpha, becouse soon there will be Developers’ Cut version out, which will be the best graphics DX11 STALKER game ever made.

And please also consider this: Lost Alpha uses a bit modified engine of STALKER COP. According to the fact, that STALKER COP already has a VorpX DX11 and Z-adaptive 3D support, I guess that Lost Alpha would only require some minor further work from you!

Greetings: Szabby

[Szabby]

Hi!

Thanks for your kind trying to help!

In fact, in the last couple of weeks I have made a good progress in testing different methods, and now finally I am able to run all STALKER games on DK2. Thing are quite tricky though to organize, but after several experiments I found the “know how”.

Lost Alpha runs in DX9 only, for some reason R3 renderer crashes every time.

STALKER SHOC of course is the same, DX9 only, as it always was a DX9 game (however, a patch is already under developement by russian modders, which will add R3 to XRay of SHOC). I use SHOC with Autumn Aurura 2.1 mod, and the graphics quality is really remarkable, even in DK2, perfect!

STALKER COP seems to be the best choice for DK2, as it can be run in DX11, full quality, plus, the most important thing is,that VorpX adds “Z” type 3D to the game. I use COP together with Merge Mod, and it’s also great in DK2.

STALKER CS I haven’t tried yet, but I’m sure, it also works fine on DK2.

Biggest challenge was to find solutions, how to increase FOV in these games, becouse vanilla FOVs are around 55 and 67.5, which make the games unplayable on the rift. there are some FOV changer mods as well, but these also don’t fit, as the highest FOV these offer is only 90, which is still way too low. And Lost Alpha is the only STALKER game, that includes console FOV command. In all other STALKER games you can not change fov nor in console, neither in ltx files, becouse to do that you have to alter the engine dll files. Of course, with shift+scroll you can change FOV ingame with VorpX, but this solution isn’t good, becouse it’s only a “false” solution, that takes screen further in front, and to be honest, seeing the edges of the screen spoils all 3D experience of immersion.

I would highly recommend for Ralf to pay serious attention to Lost Alpha. Dezowave team will release Lost Alpha Developers’Cut soon, with higher resolution textures, improved light and shadows and extra nature content. So when released, Lost Alpha will be the best graphics quality STALKER game out there. According to millions of fans, I assume, making this game VorpX ready with at least “Z” 3D support is more than justifiable!

thanks: Szabby

[Szabby]

Are you playing on ultra settings?

[Szabby]

Hi Nargorn!

No, your rig is absolutely OK, the stuttering problem is caused by poor porting and not becouse your PC is weak.

First I recommend you, to download all available fixes to the game.

The stuttering in most cases is due to mouse acceleration and/or buffer setings. You should search for GameProfile.xml file in FC4 folder, and open it with notepad (but before saving changes make a backup of the original file).

There you should disable mouse acceleration and mouse smoothing options. Sometimes DisableLoadingMip0=”1″ GPUMaxBufferedFrames=”1″ settings also help, but please note, that some of these settings can reduce texture wuality as well. Anyway, turning off mouse acceleration and smoothing worked fine for me.

In fact, there are great posts to be found in this theme for example on reddit or other channels.

Hope, this helped.

[Szabby]

Hi Adam!

Don’t give up, it will surely work!

The main reason, why the game crashes at startup, use to be, that you are online! Please note, that when I say “offline mode” it doesn’t only refer to choosing “launch the game in offline mode” on the HUD when you are already in the game, but it also refers to Uplay! So, before launching Far Cry 4 exe file, launch Uplay first, and switch online mode to OFFLINE! VorpX won’t work otherwise and the game immidiatelly crashes in online mode.

To those, who either have a startup crash problem OR the problem, that you can not make the game run on the Rift’s screen, again, please make sure, that all the following parameters are set OK:

1. Make sure, that the rift is properly installed. I use the rift the way, that in my desktop/VGA settings:
– DK2 and my monitor are side by side (monitor is the first and next to it on the right there is the DK2),
– DK2 is in portrait mode and NOT landscape
– In resolution options DK2 is set to 1920X1080 AND 75 Hz (this is essential!)
– My DK2 is set to be secondary screen (apart from some rare cases as exceptions, I think DK2 doesn’t need to be set as primary screen!)

2. WITHOUT launching VorpX you must launch the game first and make the following settings properly:
– aspect ratio: auto
– resolution 1920×1080
– screen: FULLSCREEN (NOT borderless or windowed!)
– refresh rate: 60 Hz (as there is not an option for 75 Hz, but if anybody knows, how to upscale this to 75 Hz, please, tell me)

Before exiting the game, SAVE the changes!

3. Set the rift to extended mode and disable OR Service.

4. BEFORE launching FC4 exe, launch Uplay and switch it to OFFLINE mode! Disabling the overlay can not hurt either.

5. BEFORE launching FC4 exe, launch VorpX and enter general configuration. The most important thing there is to set “SHOW ON RIFT DK2” and NOT “use system settings”! This is highly important, otherwise you can run into the same problem, that the game won’t show up on your rift’s screen, only on your monitor!

I also use the following settings turned ON:
– Disable Aero on game start
– Restore desktop windows

I also had the problem, as some other commenters mentioned too, that in the game everything was “too close”, and it made me a headache quite soon. To avoid this you can create optimal view by harmonizing the following settings:
– Increasing FOV in VorpX Game Settings Optimizer menu (for my taste, FOV 130 worked much better, and resulted a more comfotable gameplay, than FOV 120)
– Altering vignette scale and image zoom settings ingame through VorpX control panel
– Switching between lens A and lens B settings

I hope, that the guide above helped in solving FC4 – DK2 problems to all of you!

Keeping all these instructions I think there is no way to fail playing FC4 on DK2.

Please, write some feedback, how you succeeded.

Greetings!

[Szabby]

Hi Ralf!

I think it would be extremely usefull, if you wrote an official quide to all VorpX settings one by one (and perhaps integrate this quide into VorpX control panel itself): in fact what these settings alter, what setting what effect has got, and how the settings have an effect on each other. I know, that there are settings which are quite obvious, but there are also several, which aren’t.

Thanks!

[Szabby]

Hi!

Is your DK2 set to primary or secondary screen in desktop/VGA setings?

[Author]

Posts