Forum Replies Created
-
Posts
-
The 0.43 runtime indeed almost certainly isn’t the problem. Please rename/delete the following folder: C:\Users\[Username]\AppData\Local\Oculus. This might solve the issue.
The AppData directory may be hidden, you have to enable ‘Show hidden files’ in Windows Explorer to see it.
if that doesn’t help, please try to uninstall/reinstall vorpX in case you haven’t done that already. You can keep the registry information when being asked while uninstalling.
The config app isn’t that important currently BTW. Almost all settings can be changed in-game through the vorpX in-game menu (press [DEL] to open it).
This looks like a problem with Microsoft DotNet installation. Both the updater and the config tool are using the DotNet Framework. Microsoft has a DotNet repair tool that might be something worth to try:
http://www.microsoft.com/en-us/download/details.aspx?id=30135
Also disabling your virus scanner temporarily is something you should try.
You can use vorpX without the config tool BTW. Certainly not ideal, but most things can be adjusted in the vorpX ingame menu (press [DEL] while in the game).
A short test looks positive. Everything seems to be OK when using the 0.43 runtime, at least as far as I can tell from shortly trying a handful of games. More testing will be done next week.
If you want to be on the safe side, I would recommend to create a manual system restore point in Windows before installing the 0.43 runtime. This way you would be able to roll back easily in case any issues do show up.
Sorry for the inconvenience. We had an issue with the e-mail server earlier today for a few hours, which should be resolved by now.
Please resend your activation requests, the old ones probably are lost unfortunately.
Thanks for your understanding.
Not sure whether the cockpit issue can be resolved. Currently I’m not even sure what causes it, TBH. My guess is that FSX renders the cockpits in a different pass that for some reason is not treated the same way as the rest of the scene.
I’ll take a look at it, bit without access to the source the code this might be hard to resolve.
Hi ph2001,
Wings of Prey is not one of vorpX’s supported games. Many unsupported games work (usually without S3D, but Rift related functions like head tracking, image warping etc. intact), but there are no guarantees.
I will take a look at the game, as always in such cases no promises though.
@ h8cru: If you still use a DK1, please get the latest Oculus runtime (0.42) from oculusvr.com . It should install automatically with vorpX, but maybe that failed for some reason in your case.
If that still doesn’t work, please send a mail to support |at| vorpx com to get a downgrade option to the last version.
Keeping a copy of the web installer is enough. It always fetches the latest version from the server.
My guess would be thst you inadvertantly exit Skyrim when pressing the space bar. Menu entries in Skyrim can be executed with it.
In regard to not being able to close the pos tracking dialog, please make sure to tip the space bar only briefly. Longer key presses may not get registered correctly. This is almost cetainly the issue here.
With the current vorpX version you’re best off using one of the Z-Buffer 3D modes. I would suggest to wait a little bit though, Geometry 3D with more game specific fixes will be available soon.
The game is not supported yet, it’s out for merely 12hrs.
However, it should work in 2D simply by starting it from Steam. Rift as secondary, “Show only on Rift DK2” in the vorpX config app works just fine here. As always setting the game to 1920×1080 beforehand is important.
Someone on Reddit mentioned he had to start the game windowed and then move the game window to the Rift and switch to fullscreen afterwards. None of that is necessary here though, but maybe that helps in your case.
Irrespective of possible starting issues I would strongly suggest to be a lttle bit patient. You probably won’t regret it, a profile is being worked on right now.
BF4 can be a bit tricky from time to time. Sometimes it helps to just try a few times, apart from that you could check the things below:
1. Disable the in-game overlay in Origin.
2. Switch from the 64bit to the 32bit version of BF4 or vice versa. Maybe one works better for you Using the 32bit version helped in many cases.
3. Go to offline mode in Origin. This circumvents Battlelog and might help with vorpX. However, you will loose online gaming, so do this as a last resort only.Never heard of that issue before, and you surely aren’t the first customer from Spain. Does this happen in all games?
The key code for the DEL key should be universal. Which DEL key did you try? Normally the one above the cursor keys is the right one (probably named “Supr”), not the one on the numpad.
You should also the see the game already in Rift view (warped split screen). Otherwise vorpX probably didn’t hook at all and the menu can’t be opened because of that.