Forum Replies Created
-
Posts
-
Try to reset the profile to default in the config app. There have been several changes from the preliminary profile. Among other things the profile comes with automated FOV and various tweaks for FullVR mode now.
I’ll upload another setup in a few hours that should fix the issue. Won’t bump up the version number though, so you’ll have to reinstall to get it.
Odd, the height modifier function shouldn‘t really depend on the loaded profile at all. Can‘t really imagine why it would right now, but I‘ll check with one of your custom profiles whether I can find something.
Think I found it: it’s only working (again) currently if positional tracking is enabled, which shouldn’t be the case.
Will look into that before the next regular update.No camara height modifier issues here as far as I can tell. In which games did you have this problem?
Special shaders should work as intended again. As part of the DX11 performance optimization in 21.1.0 there have been some changes that caused an issue with the ‚Special Matrix/No Transform‘ shader type, but that should work again in the latest version.
The second framerate depends on your headset, 80 is what Rift S uses, most other PC headsets do 90. The only way to change it would be your headset software if it has such an option. Unsure about the G2, other WMR headsets typically support 60 and 90, which can be changed in the WMR portal.
20/12/21
vorpX 21.1.1 has been released.This is a maintenance release with the below changes and fixes. If nothing comes up with it that requires immediate attention, that should be it for this year. Happy holidays to everyone!
- Improved: Cyberpunk 2077: DirectVR FOV added, .ini tweaks for FullVR comfort. If you played Cyberpunk 2077 before with vorpX, resetting the profile to default in the config app is recommended.
- Improved: DX12 changes to circumvent Cyberpunk 2077 crashes with Radeon GPUs
- Improved: Instead of dismissing them DirectVR now utilizes resolutions it considers too wide for the current situation and shows an according performance hint if nothing better is available, e.g. AMD VSR resolutions weren’t always used before.
- Fixed: Headset Sync ‘Fast’ could cause stutter since vorpX 21.1.0
- Fixed: TrackIR recentering did not work from the vorpX menu.
- Fixed: ALT key was ‘stuck’ after ALT-TAB to/from desktop.
- Fixed: Installing hook helpers could fail under some circumstances
- Fixed: Config app could become ‘invisible’ after disconnecting a second monitor if it was opened on the removed monitor before.
- Fixed: DX11: some special shader definitions weren’t applied correctly anymore.
- Fixed: Middle-Earth: Shadow of Mordor: scalable HUD didn’t work anymore.
Should not happen for the current vorpX 21.1.0.3 with the latest Defender definitions, but there will be another update later today, so it may happen again shortly until that is sorted out again in a day or two.
The best way to get rid of these false positives is excluding the vorpX program folder from your AV scanner, typically that is C:\Program Files (x86)\Animation Labs\vorpX.
I’m not entirely sure if these things weren’t actually “fixed” by a bug in the last vorpX. RE7 has always been a bit odd. In general 3D is fantastic in this game, but the few glitches it has are tough cases. Fixing one glitch causes another one somewhere else. E.g. with the current public vorpX build VHS tape sequences are broken due to the above mentioned bug. Fixing the bug fixes VHS tapes, but it could well be that other things will become glitchy (again) because of that.
vorpX handles TrackIR without any further setup now. For F1 2020 that’s enabled per default, you just have to enable it in the game options. In general vorpX can now detect TrackIR support in games and whenever it does, it shows a notification. Makes using TrackIR in games way more comfortable since you don’t really have to do anything manually anymore besides enabling it in the game (if necessary) and vorpX.
A little caveat: recentering TrackIR from the menu doesn’t work currently, ALT+SPACE however should. That will *hopefully* be fixed in the next vorpX update either later today or tomorrow. I’m working on that right now incidentally.
I can only imagine this to be caused by an unusual combination of graphics settings. I played quite a bit of F1 2020 while developing the recently added vorpX TrackIR feature. Provided your CPU is similarly powerful as your GPU you should even be able to play this game with 90fps at low/medium gfx settings in 1440p with G3D.
Use one of the game’s graphic’s settings presets. If you happen to have switched off DirectVR auto settings in vorpX (which is generally not recommended), also make sure that HDR is disabled.
The higher gfx presets should also work, but the game is truly awesome at 90fps, so try one of the lower ones too, you might find that more enjoyable than highest gfx settings at a reduced framerate. Personally I found medium settings + texture anisotropy at 16 (for sharper road textures) ideal with a RTX 3080.
Also make sure to reset the vorpX profile to default in the config app and then follow the instructions in the top/left corner of the game window for FOV and TrackIR head tracking. Works great in FullVR mode since vorpX 21.1.0.
Currently there is not much time to look into much more than Cyberpunk, sorry. I’ll take a look at the game after the holidays. There never have been any unusual performance issues with the profile though, and since there hasn’t been any update to the game for quite a while, it’s unlikely that there is some new issue suddenly. Your calculation above doesn’t factor in that vorpX raises the game FOV to match the FOV of your hedset, which usually has a pretty huge impact on performance since a lot more has to be rendered with a higher FOV.
If you didn’t try that already, I would suggest to first reset both the vorpX profile and all game settings to default. From there your main options in regard to optimizing performance are: game resolution, game detail settings, switching from G3D to Z3D. Find a combination of these factors that works with at least half your headset refresh rate or more on your PC.
As far as the forum in general is concerned: I answer as much as I can here, seven days per week, but in general forums – this included – are mainly tools for user to user communication.
Interesting find, thanks for the heads-up. If I can confirm this to be a general issue, I’ll automatically set that setting accordingly.
It doesn’t crash with vorpX, but unfortunately the depth buffer changes in a way during gameplay that makes the heuristics used for such cases fail. In layman’s terms: 3D switches on/off seemingly randomly, hence I had to pull the profile from the last release. I’ll take another shot at it later, but don’t expect anything in that regard before Christmas.
The keyboard handling has changed recently, which saves a quarter of a millisecond (every bit counts!) per frame. There seems to be some odd glitch in the new code that leads to the ALT key being stuck occasionally. I have that on the to-do-list.