Forum Replies Created
-
Posts
-
Won’t work in this quite unique case. The game uses DX11 with feature level 10 instead of the usual 11, which isn’t fully supported by vorpX since only a handful of games do that.
The supported Need for Speed – Most Wanted is the first one from 2005. nfs13.exe is the remake from 2012, which currently isn’t supported.
It’s not possible to ALT+TAB between the desktop viewer and a game vorpX is attached to. vorpX runs either ‘inside’ a game or the desktop viewer. It can not run inside two programs at the same time.
You can play windowed games using the desktop viewer though by disabling the vorpX watcher after starting the desktop viewer. That way ALT+TAB works, but since vorpX doesn’t hook into the game directly you lose all functionality that vorpX provides when it runs directly inside a game (most importantly stereo 3D), so that’s usually not something you should do.
Your license still is valid. You can simply request a new key if the old one doesn’t work anymore due to hardware changes.
NEVER use newer profiles with an older vorpX version. You can use older profiles with newer vorpX versions, backwards compatibility is usually ensured as far as possible, but the other way around in many cases will not work correctly. With the next release 19.1.0 for example new G3D profiles will contain various settings that older vorpX versions (obviously) do not even process.
Most new G3D profiles in 19.1.0 either won’t do anything or have severe issues in older vorpX versions since those lack the functionality that makes the new profiles possible.
BTW: If you are using a SteamVR headset, you have to update to the latest vorpX anyway, no way around that. Older vorpX versions do not work corrrectly with the latest SteamVR update.
Game performance is the same as before.
Judder wise there is no difference for Rift and with Vive you get less judder than before. Vive was broken before with the latest SteamVR version. Technically Vive and Rift work below 45fps, even 30fps seems passable, although that’s not exactly great of course.
For Windows Mixed Reality headsets there still is severe judder between 45fps and 90fps unfortunately with the latest SteamVR version. I’m testing additional changes for WMR headsets currently. Looks good so far, but WMR will still need 45fps minimum to be judder free, no way around that. The WMR related changes will be made available as soon as possible.
One more (last for today) test at 2560×1440 (Vive). Also buttery smooth 90/90 without any issues. Rocket League works perfectly fine.
As said above, I’ll do some more Rocket League tests including WMR next week. With a Vive everything looks perfectly normal and smooth as always. Would be quite a surprise to see WMR behave any different, but who knows. Everything is possible, of course. It’s Sunday evening here though, so sorry for being able to do more testing immediately.
Just in case: double check whether SteamVR is up-to-date (should be 1.1.4).
No problem to get buttery smooth 90/90 on a Vive with high details at 1920×1200.
As far as I’m aware the Pimax 8k has it’s own reprojection (‘Brainwarp’), it doesn’t use the SteamVR reprojection. If this ‘Brainwarp’ doesn’t kick in for some reason, you have to make sure that the game runs with xx/80 to work correctly with vorpX (IIRC the 8k’s native refresh rate is 80).
No measurable difference here in a brief test. 1080Ti, 1920×1200, high details.
45/90 with FluidSync, 62/90 without. Since the game’s frame rate is capped at 62fps exactly what one would expect. Without the cap (which is not vorpX related) it would probably run at 90/90.I’ll do some more in-depth tests next week, but judging from the brief check nothing seems to have changed for Rocket League.
Yes, it’s still supported. The option only has the described effect in Oculus mode hence it is hidden for SteamVR now.