Search Results for 'The Witcher 3'

[dellrifter22]

Witcher 3 probably defaults to cinema mode because it is 3rd person game.

Push Delete key in game to open the vorpX menu. Turn Cinema mode to off if you want to play fullVR. There is also the option to change/disable 3D also. You’ll probably want to keep in on Z-Normal for best results.

handy hotkeys:

Delete to open and close menu
Mousewheel click to edgepeek/zoom out
Alt+Spacebar to recenter screen
Alt+F to display frame rate

[ourbase]

Okay, got it to work – had to go to general settings and make sure Vive was the selected hardware as it defaulted to Rift.

However, I’m still having issues with The Witcher 3 which is a supported game. It doesn’t launch in 3D mode…just a big screen?

[ourbase]

Just bought VorpX because it said there is HTC Vive support. However, after installing, and trying to run The Witcher 3 in Steam, vorpX message box comes up and says “vorpx could not initialize your oculus rift. It reported:” And it didn’t report anything…I don’t own a Rift, it’s the HTC Vive. I just downloaded it, so it should be the latest version which has Vive support.

Any help here would be great.

[rtrski]

I had killed the 2 running processes using task manager not tray icon since I thought it was why DS wasn’t executing properly, but it was unrelated. So if not running it won’t even try to run when you launch games? (e.g. hasn’t connected itself at the registry level to execute first?) Also…didn’t even know there was a tray icon at first. Stupid W10 hiding icons unless you set them on…sheesh. Got it visible now.

Also figured out if it is running I can prevent it autostart with applications (watcher?) at the tray icon. The menu pick wording didn’t quite match what the help page said about enabling/disabling which confused me, but all is good now. Did notice it gets stuck with applications in a ‘can’t find HMD’ text notice loop if the Vive isn’t actually plugged in but watcher was on…prevented me actually getting the focus into Elite until I disabled the watcher and tried again. And of course might not actually use in Elite since it has its own (currently buggy) VR support built in.

Wanted to buy the second I saw Vive support but waiting on new glasses without bifocal lens to really use my Vive for evil <grin>) so might not test again for a week or so. Couldn’t resist the very first day but not worried if it take a few tries to get the right sequence. Probably start with 3rd person games first like Dead Space, Alan Wake, Witcher 2 and 3, to test my nausea response.

Thanks again for the program and look forward to much more time with it.

[red]

The Oculus Runtime Switcher is possibly the cause of your problems. Going from v1.3.x to v0.x and back again has never worked on my systems and has required an uninstall of both (along with manually removing /ProgramFiles(x86)/Oculus directories) and a few restarts to get v1.3 working again.

Try a clean install of Oculus Runtime v1.3 (after uninstalling v0.x, v1.3 and VorpX and restarting). Don’t install Runtime v0.x.

Then try an app (without VorpX installed) from the Oculus Store… they all work fine with the lastest Oculus Runtime and DK2. If you’re not getting any errors then install VorpX v16.1.2.

If you’re still getting the same error I’ll eat my hat.

[onyxlee]

The same here. I use the oculus runtime switcher to switch back from 0.8 to 1.3. And I got the same error.

[onyxlee]

Hello guys, I recently updated my DK2 to Oculus Runtime 1.3. I am also using the runtime switcher to switch back to 0.8.

But every time when I tried to launch VLC or Rise of Tomb Raider or anything, I got this error message saying:

vorpX could not initialize your Oculus Rift. It reported:
Client version too old to connect to service

Here is my Oculus runtime 0.8 info:

Display Driver Version: 1.2.8.0
Positional Tracker Driver Version: 1.0.14.0
NVIDIA GeForce GTX 970
Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz
HMD Firmware: 2.12
Connected to OVRService server.

Any suggestions? Thanks.

[raron]

I also got the in-VR error message “Sorry, we’re having trouble loading vorpControl.exe” etc. No error message in windows ofc.

However, if I just close that Oculus home VR/store-thing, and leave vorpControl.exe *32 and vorpControl64.dat running (task manager), and then start a game, in my case I’ve only tried Fallout 4 so far, it seems to work. Poorly though. In all 3D modes, and especially 3D geometry.

I did run the Game settings optimizer from VorpX Config btw, for Fallout 4. The VR visuals is pretty good in geometry mode, just saying. But performance is just useless. Too bad really.
I don’t know what exactly the FPS is, as EVGA precision (v. 3.0.1) can’t display the FPS counter in FO4. I guess it’s 10-15-ish, give or take. Usually (non-VR) it’s butter smooth.

Using Oculus Rift DK2, latest runtime 1.3 (0.1.3.1.10809 as reported by Bilago’s VR manager, since I couldn’t figure out where I find this info from Oculus home).

And Windows 7 ultimate 64-bit, GTX 970 with nVidia driver 364.72.

Also, that Oculus home thing starts when I quit vorpX. Also when I start vorpX, but then that error message pops up after a while.

Now I won’t rule out that I’ve managed to mess something up while installing a runtime switcher, since I discovered that runtime 0.7 somehow didn’t get installed properly (missed the OculusConfigUtil.exe), so I had to reinstall that, twice, and then reinstall the newest 1.3.something. But it seems to work now. Except with the vorpX performance being very bad.

[Saunders]

I can not get VorpX to load anything. I was just get a black screen. Fully updated drivers, VorpX is latest version. Not sure what else to try…. I just purchased VorpX wanting to use it for Witcher 3 and Fallout 4.

Now I see Oculus Home… when i launch a game, I get the screen for loading, then the game launches on my desktop and Vorpx just crashes. When I mouse over the VorpX icon it disappears.

[Ralf]

That usually means that another runtime version is present than 1.3, or (the other way around) vorpX was not fully updated.

Please uninstall vorpX (keep the license when asked about it), reboot (important!), and then reinstall using your web installer. if you don’t have it anymore, send a mail to support |at| vorpx com.

If you by any chance have the runtime switcher installed, please make sure that it is set to use the 1.3 runtime, or ideally remove it completely.

[vladfrenkel]

Just wanted to share. Perhaps may help someone.
I have DK2
Have 1.3 Oculus Sdk installed and use Oculus switcher to switch from 0.8 sdk(insalled) to 1.3
Original update via vorpx 0.9.1 with 0.8 sdk chosen would result in start of installation and immediate rollback. So I have read the forum and Ralf’s comments. Here is step by step instructions which worked for me.
Used the runtime switcher to allow 0.8 run side by side with 1.3
https://www.reddit.com/r/oculus/comments/4ckm38/oculus_runtime_switcher_0506070813_with_gui/Make sure you are on 0.8 and vorpx is started to update.
Remember where update is download in C:\Users\(Username)\AppData\Local\Temp\vxs-(numbers)
Quickly copy update file onto desktop or other place before system has deleted it.
Now vorpx will go through and say it rollback changes no problem.
Next in oculus switcher switch to 1.3 sdk
Now vorpx will update normally (may complain that chrome or Cortana open, but should be ok)
Basic trick is that update is downloaded if you are on 0.8 sdk and installed when you are on 1.3

Hope it helps.

[Ralf]

vorpX 16.1.2 has been released.

This is a maintenance release that mainly addresses a few DK2 related issues with the last version. List of changes:

• Fallout 4: 15-20% performance gain when using Geometry 3D
• Some OpenGL games only displayed horizontal bars instead of the game
• Oculus Rift CV1: 3D mode controls weren’t always shown in settings UI.
• Oculus Rift DK2: head-tracking did not work correctly in some DX11 games
• Oculus Rift DK2: fix for severe performance degradation in some DX11 games
• Oculus Rift DK2: potential(!) fix for Desktop Viewer not showing in headset on some configurations

For information about the last big release please click here.

If you already own vorpX, it should auto-update when you start vorpX Control next time. If it doesn’t for some reason, simply use the web installer that you received when you purchased vorpX. It will download the latest version available.

Important note for vorpX 0.9.1 users:

vorpX 0.9.1 will only auto update if you have the Oculus runtime 0.8 running. vorpX 0.9.1 cannot start otherwise and initiate the auto update! If you already installed runtime 1.3, please try this:

Workaround 1: Use your web installer to install 16.1.1 manually
Workaround 2: Use the runtime switcher linked here to allow 0.8 run side by side with 1.3:

If the runtime switcher does not help and you don’t have your web installer anymore, please contact support |at| vorpx com.

[Ralf]

Maybe it’s a DK2 SDK1.3 issue on some machines. Please send a mail to support |at| vorpx com to get an older vorpX version, which you can use with the 1.3/0.8 runtime switcher.

[Ralf]

@ edo : Seeing the grey Oculus room before a game starts for a few seconds is perfectly normal. That’s how Oculus chose to handle things from now on.

@ modelmode : After the update vorpX uses runtime 1.3, switching to 1.3 in the runtime switcher should solve this. If you don’t need 0.8 anymore for other purposes, you can now remove it entirely.

[modelmode]

Hmmm. Ok, I installed the switcher and can confirm that it works between 0.8 and 1.3. I was able to install Vorpx 16.1.1 but when I try to start it I get the o’l Oculus Runtime init failed Please check if you have the Oculus runtime installed. Is this just because Vorpx can’t find the runtime? We had to use some specific folders for the runtimes. On a side note, I’m so happy I get to have my cake and eat it too! Thanks Raif!