Forum Replies Created
-
Posts
-
vorpX works with DX9-DX11 (and older OpenGL) games. I’m not sure what DX version Warcraft III uses, but I’d be surprised if it was DX9 or newer.
If running in safe mode fixes the issue, the best you can do is check for everything that is loaded on start and runs in the background. Check the “Autostart” tab in your task manager to see what your PC loads on start. It doesn’t show everything, but is a good playce to start.
BTW: Until you know a bit better how vorpX works, it makes *A LOT* of sense not to mess with settings too much or apply custom settings. It’s quite easy to mess things up severely if you don’t know what you are doing. The default profiles usually work fairly well out of the box.
There isn’t that much you need in config app. All important per game configuration is done ingame in the vorpX menu. You can access it by pressing [DEL] while in the game.
In regard to your config app crash I can just, again, recommend to remove that highly invasive AV program from your PC and switch to Windows Defender, which provides good protection without the annoying invasiveness of some other AV programs.
If that does not help, there has to be something wrong with your DotNet/Windows install.
@ Sgt_Nick_Fury : The reason for the slowdown is that for Stereo 3D rendering everything has to be rendered twice, so a ~50% performance hit, usually a bit more due to some extra overhead for rendering to the headset, is quite normal for Geometry 3D.
You can trade 3D fidelity for speed by switching to Z3D in the vorpX config app. Doesn’t look as good/natural, but is a lot faster since it does not have to render everything twice.
In regard to Enderal specifically your best bet is probably to reduce draw distances. Try the “medium” quality preset in the Skyrim launcher. I don’t know Enderal, but if it’s anything like Nehrim, the prior Oblivion mod from the same team, they may show a lot more stuff per frame than the base game, which has a severe impact on performance.
The mirror display does not have any adverse effect. If Steam complains about that, you can safely ignore it.
@ Ragin666 : please check this reply to another thread, it applies here too.
Not all AV programs are really disabled if you disable them or they require to disable several modules until they really are. Yours might be one of them, it’s certainly known as a frequent troublemaker in regard to vorpX.
I would highly recommend to switch to Windows Defender for vorpX. vorpX does several things that more invasive AV programs do not like, you almost certainly will encounter other “inexplicable” issues too, e.g. games not hooking, failing Direct VR memory scans etc. Windows Defender provides good protection without being as invasive as some other scanners.
Please also try to reinstall vorpX and make sure that it has access to your Documents folder. Your AV program may have an additional feature that requires you to grant access to that folder for every program manually.
Also check whether maybe your DotNet installation is corrupt by running the DotNet repair tool from Microsoft.
If all fails in regard to the config app, you can follow the steps below to configure vorpX for your headset.
1. Go to C:\ProgramData\Animation Labs\vorpX
2. Open vorpX.ini with a text editor
3. Change the second line to sDeviceIniName=HTCViveCV1The C:\ProgramData folder is hidden per default. If you can’t see it, enable “Show hidden files” in your Windows Explorer options.
Setting both the coarse and fine distortion values to 0.0 entirely disables any image distortion. Mathematically that is 100% exactly the same as not applying the distortion algorithm. Distortion scale should be 1.0 in that case.
If afterwards the image still looks distorted, the game’s FOV does not fit the FOV of the phone/lens combo you are using, provided your own distortion algorithm works correctly that is. In cases where vorpX can handle the game FOV you can address that by changing the FOV for the generic headset in the vorpX config app. Once you have the right value dialed in there, the FOV will fit for any game that vorpX can handle FOV-wise.
A guaranteed perfect auto-FOV out of the box is only possible for Steam VR/Oculus since both runtimes provide the exact headset FOV. For phone based VR the correct value depends on severable variables, so you have to adjust (probably lower) the value in the config app until it fits your phone/lens combination.
The same is true for lens distortion BTW. Unless Daydream somehow provides information about the used lenses or distorts on its own, you won’t be able to provide a one size fits all solution in your app. So you might just as well use the vorpX distortion instead of rolling out your own. Users would have to fine tune anyway depending on their individual phone/lens combo, be it in your app or in vorpX.
As far as vorpX is concerned you can adjust the FOV on the DirectVR page of the ingame menu. The auto-calculated FOV is 100% guaranteed pitch perfect though, so changing it will cause warping instead of removing it.
If any mod you are using overrides the vorpX FOV, there is not much that can be done by vorpX unfortunately. If you suspect that might be the case, try without any mods and/or external FOV fixes you may be using.
That sounds rather odd. GTA V FOV adjustment is done via writing directly into the game’s memory, so changing the FOV should work in realtime. Still works fine here with the latest version of the game (just tested).
Three things you could check:
- Make sure you don’t have an extra FOV mod installed/running that may override the vorpX FOV, if in doubt try without any mods.
- Disable/uninstall your AV scanner if it’s anything else than Windows Defender. The more invasive ones may prevent vorpX from applying the FOV.
- Just in case (not suggesting anything): make sure not to use any ‘trainer’ or ‘unofficial’ copy of the game.
There is a 3D-disable hotkey to circumvent such issues. You can either press and hold it or tap it briefly for toggling 3D on/off. The default is ALT+X. To have it activated automatically whenever you aim down sights, you could change that to the game’s ADS key in the vorpX config app.
If the config app does not lauch, it’s quite likely that your AV scanner blocks it. That is by far the most likely cause of such an issue.
If you use anything else than Windows Defender, either disable your scanner or exclude the vorpX program folder (C:\Program Files (x86)\Animation Labs\vorpX) from scanning. Some particularly invasive AV programs don’t really allow their users to fully deactivate them, in such a case consider to switch to Windows Defender, which comes free with Windows 10.
Once you can launch the config app all you have to do is selecting “Steam VR” as your headset type in the config app and you are good to go.
Disclaimer in advance: Star Citizen is not officially supported due to it’s alpha state, the provided profile may break at any time. Hence the message in that regard on every game start.
The only profile that is capable of producing Stereo 3D with Alpha 3.0 is the semi official profile that is already activated when you install vorpX (or its equivalent cloud profile by author [vorpX]). All other cloud profiles are for SC Alpha 2 as far as I’m aware. You can restore the original profile in the vorpX config app on the trouble shooting page.
You can then switch between Z3D (‘less’ 3D, fast) and G3D (more natural 3D, slower) in the vorpX ingame menu. The option is called ‘3D Reconstruction’.
There currently are no trackers available for the generic headset mode, that is correct. This mode is meant for phone VR users who do tracking via an additional streaming app.
You can customize the distortion in the vorpX ingame menu while the generic headset is selected.
Just in case: if you are using the generic headset for a Vive (or other SteamVR compatible headset) right now, you should use the dedicated Steam VR mode instead.