- This topic has 18 replies, 10 voices, and was last updated Nov 3, 2019 3:20pm by
.
-
Posts
-
19/09/06
vorpX 19.2.4 has been released.This is a maintenance release with the below changes and fixes.
New/Changed:
- New D3D9 font renderer: fixes severe FPS degradation (up to 70%) during the first minutes (while the start hint is shown) with Half-Life 2, Portal, The Darkness II and possibly other D3D9 games.
- Improved D3D11 G3D heuristics (~30% G3D performance gain in Blair Witch).
- Improved binary settings file support for the DirectVR settings optimizer.
Bugfixes:
- G3D camera height modifier should now always work again without positional tracking. Please note that the setting may behave different with/without positional tracking enabled in some cases.
- Settings for official profiles could not be uploaded anymore in the config app.
- Final headset render target size re-evaluated when the game resolution changes. Fixes low render target size in games that open a small window on start before switching to full res.
New Game Profiles:
- Blair Witch: G3D/Z3D, FullVR, scalable 3D HUD, DirectVR: FOV, resolution, tracking.
19/08/29
vorpX 19.2.3 has been released.This is a maintenance release with the below changes and fixes.
This release contains the changes regarding ImageZoom being inconsistent between devices if set to a value below 1.0 with any other device than an Oculus Rift (details here). For this change to take effect, profile authors have to re-save and re-upload affected profiles to ensure they look as intended for everyone in the future.
If you encounter any issues while re-uploading your profiles, let me know.
New/Changed:
- Better left handed Touch/Index/WMR controller support: left/right mappings can be swapped
- Better handling of user profile uploads: profile creators can now always upload their profiles with the original profile ID.
- Various minor VRController improvements.
- Injection indicator and version string automatically fade out after two minutes.
Bugfixes:
- Profile cloud connection could time out too early and without any feedback in the config app.
- ImageZoom setting now always consistent between devices as intended. User profile authors will have to re-save and re-upload affected profiles for this to work. Only required for profiles with ImageZoom < 1.0 that were created on any other device than an Oculus Rift.
- Animated windows (e.g. the settings menu) could stay invisible when opening/closing them too fast
- Switching OpenVR controller types in the vorpX menu wasn’t entirely reliable.
- G3D camera height modifier was added in flipped direction without positional tracking.
- Under some circumstances in immersive screen mode the screen could disappear while EdgePeek was active.
New Game Profiles:
- Resident Evil 2: G3D/Z3D, immersive screen, scalable 3D HUD, DirectVR: auto settings
Game Profile Changes/Fixes:
- GTA IV: phone screen now part of the scalable 3D HUD
- GTA V: default play style changed to immersive screen mode since unfortunately the DirectVR FOV does not work correctly anymore with the latest game version.
Thank you Ralf for this update ! :)
after finishing leon playthrough months ago on flat screen, i stopped playing re2, so i still have claire playthrough to do, with that profile i’m going to have a blast ! thanks !
Time to start checking older profiles then 👍
Are the distance numbers supposed to read the same between headsets now in the menu? Or can a profiles store unique settings dependent upon which headset is active? My first test showed different numbers with different headsets, but they could be grabbing stored values from extra.ini.
How can I tell if I’m seeing the actual number stored in the shared profile or an alternate value I may have saved later for that exe into extra.ini?
Also, this may not be what you meant by:
“G3D camera height modifier was added in flipped direction without positional tracking”
,but height modifier functionality does not yet seem back to normal for cinema/immersive modes. Or it’s not working for me at least.Which version of RE2 does this work for? I just got the RESIDENT EVIL 2 / BIOHAZARD RE:2 version on steam and wondering if that will work with the new profile. thanks
@ dellrifter:
On your PC unique ImageZoom settings are stored for each headset, but the settings stored in the profile should always be the same now. If you publish a profile, I would suggest to always design them for ImageZoom smaller than or equal to 1.0. 1.0 is the reference point utilizing the full FOV on an Oculus Rift, so that is the largest value stored in profiles. If for example you design a profile on a Vive, which has a larger FOV than a Rift and thus allows ImageZoom > 1.0, you would ideally still design it for 1.0 (or below) to ensure it looks the same on the Rift.
If you want to reset all headset specific ImageZoom settings stored on your PC, go to C:\ProgramData\Animation Labs\vorpX and delete the extra.ini file.
Height modifier: that’s a different issue. I still have the other one on the list.
@ slydog43:
It’s for the remake relased earlier this year. The profile was also done with the Steam version, so that should definitely work.
Hi Ralf ! I’m playing Battlefield V and since I updated I have noticed a big drop in performance. What can I do? Can I go back to the previous version? Thank you!
@ Novaliz
No. It’s a false positive. Can happen after an update. Luckily Microsoft is usually quick sorting things like that out. If manually updating to the latest Defender-definitions does not help already, please exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) from your AV scanner.
@ angelayla
I can’t really imagine anything that might have had an impact on Battlefield V performance, but I’ll look into it.
Thanks for your attention Ralf, I don’t know if is a problem only with Battlefield V because it’s the only game that I’m playing now. I don’t know how explain the sensation, but when I turn my head the scene jump a few and it’s very uncomfortable, that’s didn’t happen before the update and my gpu is good, a 2080.
Please make sure to play the game with a gamepad and have “X-Box Gamepad Override” in the vorpX menu set to “Off”. If you are unsure, please reset the profile to default to ensure everything is set up as it is supposed to.
Using two mice (one is emulated by vorpX for head tracking) at the same time pretty much causes the issue you describe. IIRC there is an according hint shown when you start the game. This is unrelated to the new update, it’s a restriction of the game that always existed.
19/09/06
vorpX 19.2.4 has been released.This is a maintenance release with the below changes and fixes.
New/Changed:
- New D3D9 font renderer: fixes severe FPS degradation (up to 70%) during the first minutes (while the start hint is shown) with Half-Life 2, Portal, The Darkness II and possibly other D3D9 games.
- Improved D3D11 G3D heuristics (~30% G3D performance gain in Blair Witch).
- Improved binary settings file support for the DirectVR settings optimizer.
Bugfixes:
- G3D camera height modifier should now always work again without positional tracking. Please note that the setting may behave different with/without positional tracking enabled in some cases.
- Settings for official profiles could not be uploaded anymore in the config app.
- Final headset render target size re-evaluated when the game resolution changes. Fixes low render target size in games that open a small window on start before switching to full res.
New Game Profiles:
- Blair Witch: G3D/Z3D, FullVR, scalable 3D HUD, DirectVR: FOV, resolution, tracking.
loving those maintenance releases specially when they add more performance :D and other good stuff ^^
thank you Ralf for always pushing Vorpx forward, fixing, improving and adding new features/profiles :)
I just did a full play-through of Half-life 2 in VR on VorpX, such timing. Love the updates Ralf, really appreciate it.
- The topic ‘vorpX 19.2.4 Available Now’ is closed to new replies.