Forum Replies Created
-
Posts
-
This was a DK2 issue, and you can apply a fix immediately if you want. I will release an update later today.
To apply the fix manually please
1. Close vorpX if currently running.
2. Browse to C:\Users\[User]\AppData\Local\Animation Labs\vorpX\Devices
3. Open OculusRiftDK2.ini with Notepad
4. Search for iTimewarpMode
5. Change iTimewarpMode=0 to iTimewarpMode=10
6. Save the file
7. Restart vorpXThe AppData folder may be invisible. If so, please enable “Show hidden files” in Windows Explorer
This was a DK2 issue, and you can apply a fix immediately if you want. I will release an update later today.
To apply the fix manually, please
1. Close vorpX if currently running.
2. Browse to C:\Users\[User]\AppData\Local\Animation Labs\vorpX\Devices
3. Open OculusRiftDK2.ini with Notepad
4. Search for iTimewarpMode
5. Change iTimewarpMode=0 to iTimewarpMode=10
6. Save the file
7. Restart vorpXThe AppData folder may be invisible. If sou, please enable “Show hidden files” in Windows Explorer
It was a DK2 issue, and you can apply a fix immediately if you want. I will release an update later today.
To apply the fix manually please
1. Close vorpX if currently running.
2. Browse to C:\Users\[User]\AppData\Local\Animation Labs\vorpX\Devices
3. Open OculusRiftDK2.ini with Notepad
4. Search for iTimewarpMode
5. Change iTimewarpMode=0 to iTimewarpMode=10
6. Save the file
7. Restart vorpXThe AppData folder may be invisible. If so, please enable “Show hidden files” in Windows Explorer
vorpX 0.9 also has async timewarp. The new thing in 1.3 is that Oculus now does async timewarp in the driver.
If 0.9 worked for you, and you want an instant solution, rolling back is what I can offer you.
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 that works with runtime 0.8. This solution is only viable for DK2 owners.
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.
The importtnant part of my above post was the first part, not the Win 7 hint:
If it takes longer than a few seconds, the Desktop Viewer almost certainly hangs for whatever reason.
This may very well be an injection conflict. Please check the trouble shooting guide for possible causes of injection conflicts. That’s something that has to be diagnosed on your machine. No way to provide a solution without that unfortunately.
You have to enable free look / mouse look. IIRC the default shortcut is “U”. If not, please check the game’s options menu. You should be able to find it in the key assignments.
If it takes longer than a few seconds, the Desktop Viewer almost certainly hangs for whatever reason.
This may very well be an injection conflict. Please check the trouble shooting guide for possible causes of injection conflicts. That’s something that has to be diagnosed on your machine. No way to provide a solution without that unfortunately.
Just in case: the desktop viewer only works on Windows 8+. It should show a warning though if you run it on Windows 7, so that’s probably not the problem.
I need to see something before I can even imagine what this issue may be. If possible please create a video, fake something in Photoshop or at least make a sketch in Paint.
Please also make sure that your Rift is connected via Oculus compatible USB 3 ports (use the compatibility tool on the Oculus homepage to make sure your USB3 ports are Oculus appoved). In another thread that seemed to have cured the issue for someone else. For the CV1 USB 3 is a requirement, maybe also for DK2 with the new Oculus runtime.
Please make sure that the game uses the DX9 renderer in it’s config utility. Also try switchings between windowed and fullscreen.
BTW: If you don’t absolutely have to use rFactor 1 for some reason, I would highly recommend to play rFactor 2 instead, which works a lot better with the current vorpX version.
Doesn’t Dirt Rally have native support? I bought it during early access and back then it worked natively.
@ 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.
If I understand the issue correctly, it’s something that can happen now when a game either hangs or loses input focus.
In prior vorpX versions the screen would just freeze in such a case. But now with Oculus having time warp in their driver you would get something that looks similar to your description. The game freezed, but you are still able too look around the plane that the game is rendered on.
Long story short: probably not a head tracking issue, but an issue with the game either hanging or losing input. The latter might be resolvable by clicking in the game window (in case you run it windowed).