Search Results for 'The Witcher 2'

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

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

[zarlor]

FYI, I’m running the 1.3 SDK with my DK2 right now and it works just fine so all you’d need to do is upgrade your SDK and the new version of VorpX, when it’s released, should work just fine for you. Probably better than what you’re used to even. DK2 isn’t going to be “officially” supported by Oculus (so you can’t get tech support from them on it) but nothing in it prevents the DK2 from working for you. In fact there are several new things you could probably get on Oculus Home for free right now, not to mention the new SDK generally works a lot better, I think. There’s also a switcher someone created allowing you, with a simple batch file, to switch between various SDK versions. I’ve used it when I was on 0.8 to switch to 0.6 for some of the older things that were not updated, but I have not tried the new version so take that for whatever it’s worth.

[Ralf]

Just a little bit patience, please. Thanks.

It’s barely three days since the Oculus SDK 1.3 was made available publically. vorpX will get updated as soon as possible.

For the time being DK2 owners who already installed the new Oculus software can simply use the runtime switcher linked below to use vorpX. CV1 owners: you won’t have to wait long.

Oculus Runtime Switcher (0.5/0.6/0.7/0.8/1.3) with GUI
byu/dr-kaii inoculus

[Electryic]

moujamouja wrote:

For DK2 users, that should help.

https://www.reddit.com/r/oculus/comments/4ckm38/oculus_runtime_switcher_0506070813_with_gui/

thanks thats what I was looking for, I saw it mentioned on the rift forum.

[Ralf]

There is a notable benefit, especially in situations with a too high GPU workload. It’s very difficult now to create severe judder, even with notoriously judder prone games like Witcher 3 for example.

And there *might* even be potential for a general performance gain, I’m hoping for about 15%-20%. But that will require changes to the vorpX render pipeline, so probably it will not make it into the next version.

We can agree on “before 2017”!

[vladfrenkel]

Hi,
Definetely need help installing for DK2.
History – used DK2 for sometime until last year (PC died) and was quite busy at work. Finally came back to it (used Oculus 0.6 back in the days).
Long story short, loved the application. Decided to reinstall on new Gaming Rig (just purchased). Bad day chosen – yesterday, 1.3 has been released.
Long story short…how do I get both to work – eg Vorpx and Oculuas 1.3?
You can easily guess what happens. Installing Vorpx breaks Oculus 1.3 so it requests to “repair”. Once repaired, vorpx complains it can’t start Oculus service…

Would that help?

Oculus Runtime Switcher (0.5/0.6/0.7/0.8/1.3) with GUI
byu/dr-kaii inoculus

Or what are my steps here?
Really want to have freedom on what to run in HMD (thanks vorpx) but also likes new home interface and some “official” programs from Oculus 1.3.

Thanks a lot.

[moujamouja]

For DK2 users, that should help.

Oculus Runtime Switcher (0.5/0.6/0.7/0.8/1.3) with GUI
byu/dr-kaii inoculus

[dotdog20]

shadowself wrote:

Laser wrote:

No im not talking about Vive, Steam vr added sdk 0.8 support a while ago.
So people are either using sdk switcher to run 0.5 sdk or the steam vr trick.

That works for the Horizons beta (and the Ships beta) but not for the main E:D, as far as I know. If you can confirm that it actually does, I will likely buy the game, it’s 50% off right now.

daytime wrote:

I figured out how to get it working, and I can confirm for others reading this that SteamVR does support the rift.

You got the main E:D working? Or are you playing Horizons?

E:D has always had native rift support every time I have tried, no need for VorpX or SteamVR. Under the Graphics settings, there’s an option for 3D which lists a few options with either HMD (Speakers) or HMD (Headphones) working for the rift.
This applies for both E:D and H as they are the same game but with different access. Worked in .5 runtime and still now in .8 for me.

I’d post a picture, but I still haven’t found a way to screenshot the rift in .8

[shadowself]

Laser wrote:

No im not talking about Vive, Steam vr added sdk 0.8 support a while ago.
So people are either using sdk switcher to run 0.5 sdk or the steam vr trick.

That works for the Horizons beta (and the Ships beta) but not for the main E:D, as far as I know. If you can confirm that it actually does, I will likely buy the game, it’s 50% off right now.

daytime wrote:

I figured out how to get it working, and I can confirm for others reading this that SteamVR does support the rift.

You got the main E:D working? Or are you playing Horizons?

[petokaske]

modelmode wrote:

<font><font>petokaske a écrit:</font></font>

<font><font>Vous devriez faire un commutateur à utiliser une ancienne version de vorpx. </font></font><font><font>
Il ya déjà un interrupteur pour passer à l’exécution 0,8 0,6 runtime pour l’oculus</font></font>

<font><font>?? </font><font>Je ne suis pas sûr que je comprends pourquoi voudrais-je utiliser une ancienne version de Vorpx pour Fallout 4? </font><font>Avez-vous un lien pour en savoir plus à ce sujet?</font></font>

it’s just to be able to record video in extend mod

Oculus Runtime Switcher v3.0.1
byu/micomer inoculus

http://image.noelshack.com/fichiers/2015/46/1447516090-sssss.png

[miamirice999]

I’ve purchased vorpx mainly for RFactor 2, however it seems to not work at all at the moment. I have a black screen in the Rift, but as others have mentioned, the warning banner does come up. Witcher 3 and Batman Arkham Knight seem to work fine (albeit in a large 3d cinema mode rather than full 3d – is this normal?)
I have tried the latest 2 Nvidia drivers and also Oculus 0.7 and 0.8 drivers.

Any help would be gratefully received!