Search Results for 'The Witcher'

[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.

[fsp48]

Same here with Win 10, 980ti, DK2 latest Oculus. Did the web installer so latest VorpX intalled and everything else is up to date. Could actually having the other runtimes intalled with the switcher be the cause? I kept having Oculus Version 6 start at boot untill I disabled it a while ago. I have been using the runtime switcher since Oculus Home was released. Just can’t use VorpX desktop/theater yet. Would removing OVR and Oculus from the ignore section of the setting do anything?

[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!

[Electryic]

NipOc wrote:

Electryic wrote:

Ralf: I used the switcher to run 0.8 runtime and ran vorpX. Right after finishing the download, it immediately rolls back changes.

The update is saved in C:\Users\(Username)\AppData\Local\Temp\vxs-(numbers), just copy the content to a different location after the update finished (you have to be quick) and run the setup.

I ended up just using the installer. As long as you don’t delete the registry files your license remains intact.

[TechnoHunter]

Received this from Vorpx if these first instructions do not work:
vorpX 16.1.1 has been released.

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.

If you don’t own vorpX yet, you can buy it here:

This is a major release that introduces long awaited features like custom profile creation and authoring, support for the consumer version of the Oculus Rift, as well as cloud sharing for settings and user profiles. The success of the latter depends on you. Share your settings!

This release requires you to own a Oculus Rift DK2 or CV1, the DK1 apparently is not supported anymore by the current Oculus software. DK1 owners who find vorpX rendered useless after an auto update to this version should contact support |at| vorpx com for a solution.

HTC Vive support is planned but not yet implemented.

Important note for vorpX owners:

vorpX 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.

[Link removed – Please contact support |at| vorpx com if you need an older vorpX version]

[NipOc]

Electryic wrote:

Ralf: I used the switcher to run 0.8 runtime and ran vorpX. Right after finishing the download, it immediately rolls back changes.

The update is saved in C:\Users\(Username)\AppData\Local\Temp\vxs-(numbers), just copy the content to a different location after the update finished (you have to be quick) and run the setup.

[Tony Spaniels]

No I didnt change any settings in vorpx config since the update to 16.1.1, except to use the game optimizer. The weird thing is the headtracking works fine if I go into edge peek mode, its only when I go back out of edge peek that I get issues. And more confusingly if it was a setting then why would it be inverted one way (pip boy view) and correct orientation but doubled values the other way (normal view) ? Doesnt add up.

Also there wasnt this head tracking issue with 0.8. I was using the runtime switcher up until yesterday night, at which point once 16.1.1 dropped I uninstalled it and all the oculus runtimes in a clean wipe, and reinstalled runtime 1.3 so its a fresh install.

[Electryic]

Ralf: I used the switcher to run 0.8 runtime and ran vorpX. Right after finishing the download, it immediately rolls back changes.

[Ralf]

Since there were a few question about how to use this: here’s a video tutorial:

Disclaimer: Neither the video nor the runtime switcher is related to vorpX in any way. This information is provided for your convenience only. Make sure to read the instructions if you want to use the runtime switcher.

[Electryic]

Definitely DX9… nothing has changed from when it worked fine, aside from now I’m using the runtime switcher. Game loads up everything is fine…the crash happens as soon as you start a game and the load screen would come up.

[Electryic]

Everything worked before but now I’m using the RUntime Switcher.

All worked well, I had to rename the intro videos. Now everything comes up fine but I am crashing as soon as the load screen would come up when starting a saved game.

Any ideas appreciated.