Forum Replies Created
-
Posts
-
As far as vorpX itself is concerned the biggest performance impact comes from rendering everything twice for creating Stereo 3D in Geometry 3D mode. Luckily vorpX has also has a second 3D mode named Z3D, which has a far lesser performance impact. Also dialing down a game’s graphics settings always can help quite a bit, of course.
To answer your question in one sentence: your rig will work in general, but with more demanding games it might make sense to dial down settings and/or switch to the faster Z3D method.
Thanks! No problem with changing resolution here in SW:Battlefront 1, incidentally I checked that earlier when I fixed the startup issue. I’ll take another look later.
For the time being please use one of the options from my post above.
Please either change the resolution before you run the games in question with vorpX or check whether setting the ‘New Headset Sync’ option in the vorpX menu to ‘Original’ helps.
BTW: It would be helpful if you could let me know what game you have a problem with whenever you report an issue. I can only check your problem if I know what to check. :)
20/08/13
vorpX 20.3.1 has been released.vorpX 20.3.1 is a small maintenance release mainly addressing a few bugs that have been discovered since the last release. Also two new profiles have been added.
Changed/Fixed
- Fixed a start problem with Star Wars: Battlefront 1 (and potentially other games) related to the new headset sync.
- DX9 64bit games didn’t work under some circumstances.
- Adding programs to the exclude list in the config app did not work anymore.
- Installing hook helpers did not work on Windows 7
- DX12/Oculus warning was not shown for Horizon: Zero Dawn
New Game Profiles
- Grounded: G3D/Z3D, FullVR, scalable HUD, DirectVR: tracking, FOV, resolution, tweaks
- F1 2020: G3D/Z3D, immersive screen mode, scalable HUD, DirectVR: tweaks
@ Eychimo: If you happen to use an Oculus headset, please set vorpX to SteamVR mode in the config app (General page). DX12 Steam games currently don’t work in Oculus native mode due to the Steam overlay getting in the way.
Totally forgot about that. I’ll add an according warning message or something similar to the next update.
try the ‘Install hook helper’ button instead of ‘Do nothing’. It will install a file to the game folder that can help with hooking conflicts. No magic bullet, but worth a shot.
Quake IV does indeed require to run vorpX as admin like the message suggests. Since the game requires admin rights to run, vorpX also requires admin rights to hook into it.
It would be just for two or three days. I’ll release a small maintenance update later this week that will work again with the 64bit version.
Have to wait for an update to download currently, but checked Fallout 4 which is pretty similar in that regard. All OK there, so for now I would say it *should* work. I’ll let you know if the actual FO76 check says something else later.
For now the only thing that comes to mind is that maybe you accidentally changed the ‘Override X-Box Gamepad’ setting on the ‘Input’ page of the vorpX menu. Should be ‘Full’ before the DirectVR the scan and ‘Off’ after the scan.
Edit:
FO76 also working fine, so the above is more or less the only thing I can think of. Alternatively you could try to reset the profile to default in the config app.
@ ChrisNonyminus: please check my reply in the thread you made in ‘Technical Support’
@ Kalell: You can ignore the VSync message. You shouldn’t see it if Vsync is off in your GPU control panel, but it’s not really critical. The other issue sounds like a corrupt install. Best to try a full reinstall. If you need another installer, you can get one here: CLICK.
Unrelated to the headset sync, just a stupid typo at some other place.
I’ll release an update with a fix later this week. Until then you can fix the issue by switching to the “The Sims4 32Bit Legacy Edition” (click on the gear icon > Game Properties > Advanced Launch Options).
I’m not an expert, but I’m pretty sure the only diference that makes is running the game in 32bit instead of 64bit.
Try to run the game at 1920×1080 or alternatively try to run it windowed and drag the window size around until things fit. Just discovered this myself earlier today. Not quite sure yet what causes it, but under some circumstances the depth buffer has a different size than the actual rendering. Can’t promise anything yet, but I’ll try to figure out what’s going on tomorrow.
Thanks for letting me know. There has been some minor refactoring regarding the logic that decides when to show the vorpX cursor. I wasn’t quite sure whether it helps with the issue you reported earlier since I never could replicate that. Good to know that it’s fully working as intended now apparently.
There have been no changes to how the screen aspect is handled in immersive screen mode. You can work around your issue though by switching to cinema mode and setting the background to ‘None’. That’s largely the same as immersive screen mode. In cinema mode there is an option to override the automatic aspect ratio manually.
vorpX “injects” other programs which some AV programs may classify as malicious behaviour without really being sure about it. In other words: they guess, and they guess wrong. Can unfortunately happen with each new vorpX update.
You should report this as a false positive to your AV vendor so they can fix the issue. In the meantime please exclude the vorpX program folder (Usually C:\Program Files (x86)\Animation Labs\vorpX) from scanning.
Alternatively you might want to consider switching to Windows Defender, which provides excellent protection without being as invasive as some other AV scanners. It kicks in automatically on Windows 10 when you uninstall redundant third party AV programs. The same might still happen occasionally with Windows Defender, but unlike others at least Microsoft usually reacts fast and reliable in such cases.