Forum Replies Created
-
Posts
-
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.
@ angelayla :
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.
Also it would be great if you could not post your issue in totally random threads to keep the forum in a usable state for everyone (you included). Thanks!
@ 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.
Technically that would work, but for a decent framerate you would have to use vorpX’s fast Z3D stereo method. For the better “true” Geometry 3D method your rig would be too slow in many games unfortunately, definitely in case of Skyrim SE, but probably also in case of Fallout NV.
I’m also not entirely sure whether the DK2 still works with the latest Oculus Home software, so please check that first. vorpX does not work anymore with the old 0.8 beta Oculus runtime.
Holy shit. And I still didn’t add DirectVR features to any of the user profiles as promised when you reported the last record number. Haven’t forgotten about it though!
You can always find current release infos in pinned posts on top of this forum. In this case here.
I‘m not 100% sure whether I understood correctly what you need, but if you need a new download, you can get one here:
http://www.vorpx.com/request-new-download/
Make sure to enter the same mail address into the form that you used to activate vorpX originally. Otherwise the request will not be processed.
If that was not the right answer to your question, please let me know.
Unfortunately vorpX cannot change how the internal control scheme of a game works. The closest you can get to what you have in mind is playing games with ‘Play Style’ set to ‘Immersive Screen Mode’ instead of ‘Full VR’ with the virtual screen moved closer towards to you.
@ 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.
If you are lucky there may be user profiles for your games in the cloud. You can search for user profiles in the config app (‘Cloud Profiles’).
If there is no cloud profile for your games, you can also try to create your own profiles by making a copy of an existing profile, ideally using a game using the same graphics engine. No guarantee that it will work, but worth a shot. A litle introduction how to do a custom profile can be found in the vorpX help in the ‘User Profiles’ section.
The full list of officially supported can be found here:
http://www.vorpx.com/supported-games/@ User: if this started with yesterday’s update, it’s probably an antivirus problem. Unfortunately some AV programs produce false positive detections with almost any new vorpX version. Try to exclude the vorpX program folder (normally C:\Programs Files (x86)\Animation Labs\vorpX) from your AV scanner to get rid of this problem.
Please try to exclude the program folder (C:\Program Files (x86)\Animation Labs\vorpX) from your AV scanner. That’s the most likely cause of such an issue.
@ d0kt0r : You can already do that in the current shader authoring menu. vorpX already has various options to treat problematic shaders. The new feature will work on top of that and allow things currently not possible.
@ Jarilo : Everything else will stay the same. All current special shader options will still be available and only get overridden when a replacement shader is found. So the whole thing works transparently on top of the current shader tools.
If there was a Windows 7 issue, I would have been roasted already since releasing the last version. Also despite its dwindling user base it’s still tested here on a semi regular basis here. There definitely is no Windows 7 issue.
For the DirectVR FOV in Bioshock Infinite to be correct make sure to set the game’s FOV slider (graphics options) to the rightmost position. There should be a message about that when you start the game.
The cursor location in Bioshock Infinite is only correct in EdgePeek mode. That has always been the case.
Also please do a factory reset in the config app to ensure everything is set to default.
In regard to your hooking/crash issues first try to enable/disable alternative hooking in the config app. Only use the alternative method if the normal method does not work for a game. It’s not better, just different.
if that does not help, check for potential hooking conflicts on your PC. The trouble shooting guide in the help lists a bunch of potential candidates.
On Windows 10 you need to to install 2.0/3.5 by adding it to your active Windows features. Unfortunately Microsoft chose to disable it per default on Windows 10.
Official instructions:
https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10