Forum Replies Created
-
Posts
-
The game is not supported by vorpX. Has never even been checked so far here, so it might or might not work. Sorry for not being able to provide more helpful information in this case.
If you run a game windowed for example, using the DEL key might accidentally delete a file on your desktop. You definitely do not want that to happen, hence DEL is blocked as a safety measure while vorpX is hooked into a program. That is a good thing usually and not a problem since the block is only supposed to be active while a program is hooked.
A restart of your PC might also be enough to solve your issue in case vorpX is still hooked into a program that semi-crashed earlier.
You can see what programs vorpX hooked since the last start in the logfile. To check the logfile create a trouble shoot data archive in the config app.
If you can’t find the offending app, please change the vorpX menu key to something other than DEL as suggested above.
That can only be the case if vorpX is hooked into another program as a safety measure since otherwise in some programs opening the vorpX menu with DEL may have unwanted side effects. Maybe it did hook in some background process on your machine. If you happen to know which one you can add it to the exclude list in the config app.
Another option would be to change the vorpX menu key to something other than DEL. That can also be done in the config app.
No problem, the support FAQ answers that question.
Sounds as if the game update might have changed the GPU shaders that do the actual 3D rendering. In such cases the vorpX profile has to be updated to fully work again. I’ll take a look at that. Thanks for the heads-up!
The release notes usually have detailed information when a new profile is added:
http://www.vorpx.com/vorpx-18-2-0-released/Yes, pretty much the same.
G3D has the same severe issues as Origins und thus won’t be available. I might take a closer look at that on occasion, but since it’s too slow anyway even on a 1080ti that doesn’t have a high priority right now.
Z3D looks quite nice and is reasonably fast.
Just a heads-up that a new vorpX version is needed to hook the game, it requires a new method to hook D3D11 (or DXGI to be precise).
Will be released within the next few days after some additional testing.
Should not be an issue, but if you use multiple monitors, try to disable any extra monitor.
if you have a multi-GPU setup, make sure that both the headset and the monitor are plugged into the same GPU.
If you use a laptop, make sure that the internal CPU graphics is disabled. Otherwise the Windows desktop would run on the internal CPU graphics while the headset runs on the dedicated GPU. vorpX cannot copy from to the other GPU.
Please check whether you have the right headset type selected in the vorpX config app. Do not use the “Generic VR headset”. Its’s meant for mobile VR users that stream the image with an extra app.
For Oculus please select the Oculus headset you have.
For Vive (Pro)/Pimax/WMR and other headsets that support SteamVR, choose “SteamVR”
Windows 7? Make sure to install the DotNet framework 4.6.2. Normally the vorpX installer should have taken care of that, but maybe it was blocked from downloading the DotNet setup.
https://www.microsoft.com/en-us/download/details.aspx?id=53344
The FS2017 profile has been added quite recently (end of May). If you tried before that, it’s very different now: Geometry 3D, DirectVR FOV adjustment, scalable HUD.
I don’t remember why, but the MPV profile is OpenGL only. There proabaly is areason for that, but since I don’t recall it I’ll check that on occasion. Apart from that it’s not really tested well, so I would highly suggest to go back to MPC-HC or VLC for video playback. These profiles have the added benefit of a preconfigured gamepad mapping.
Are you trying to run the desktop viewer from the Oculus Home desktop? that probably would not work. If so, try to run it directly from your monitor without the Oculus Home desktop being active.
Just in case: also check whether you have the most recent vorpX version. It’s displayed in the config app (bottom left corner). Should show 18.2.5. There was an incompatibility with Oculus 2.0 earlier this year that lead to precisely this error, but that has been addresses since then.