Forum Replies Created
-
Posts
-
Interesting. Might be yet another case of ‘game update breaks shader fixes’ then. I’ll check it, thanks for the heads-up.
Can you provide a savegame? The issue didn’t occur at the beginning of the game when the profile was done, playing through entire games to catch all potential shader glitches is unfeasible unfortunately.
Please send the savegame to support |at| vorpx com.
For the time being you can switch to Z3D in the vorpX config app.
1. The server session ends after a few minutes. You should be able to login again when that happens.
2. Adding Opera.exe to the exclude list in the vorpX config app will solve your issue with Opera.
I’ll take a look at the other things.
Are you sure that the .exe actually is in the exclude list? It is only excluded if you can see it in the list.
You have to add it to the list by clicking either the ‘Add File’ or the ‘Add Process’ button. It does not get added automatically.
There are dozens of reviews and comparisons on the internet from people who do these things professionally and way better than I ever could. Probably better to check these reviews for more in-depth information. I just wanted to point out the one thing above since it directly affects vorpX.
@ FrostWarrior: I’m not really sure whether I understand the issue. If you created a custom resolution of, let’s say 2240×1680, and select this resolution in the Half-Life 2 video options, you are set.
All you need to do is making the game run with your added custom resolution. In case of Half-Life 2 that has to be done in the game options.
In other supported games you can do do it from the vorpX menu, which is what moadepht is refering to. Doesn’t work for HL2 though.
As high as your PC allows without losing too much performance. Higher game resolutions are vorpX’s equivalent of supersampling for native apps, so the higher the better. 1680p is roughly 1:1 pixel mapping for an Odyssey+, resolutions above are supersampled.
Source Engine caveat: a 4:3 aspect ratio is not only recommended but mandarory in this case to avoid FOV flicker.
BTW: If you haven’t done so already, check the ‘Custom Resolutions’ section of the help. It explains how to add resolutions that your monitor does not support normally.
… GTX 1050 Ti Display (that thing for switching what GPU games run on)…
Sounds like you are using a gaming laptop. If possible try to disable the integrated GPU entirely. Not all laptops provide such an option, but maybe yours does (e.g. in the BIOS).
I also wouldn’t rule out BitDefender, which is a known troublemaker in regard to vorpX and diffcult to disable since you have to disable several of its modules separately. IIRC a BitDefender function called ‘Advanced Threat Protection’ or similar could cause hooking issues.
Index controller support will be added as soon as I have an Index. Should arrive tomorrow, so you can expect an update with Index controller support soon.
Directly supporting less popular hardware like Cybershoes or similar accessories is a more difficult topic, I would assume though that such hardware probably comes with its own gamepad/keyboard mapping software.
This is a false positive.
vorpX “injects” other programs which some av programs may classify as malicious behaviour without really being sure about it. They literally guess and these guesses aren’t always very good. Unfortunately this can 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 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. Windows Defender gets enabled automatically on Windows 10 when you uninstall redundant third party AV programs.
I’ll take a look at it. Unfortunately not uncommon for games in constant development that a game patch breaks G3D. I’ll proabably have to redo the G3D profile.
There is no way to get G3D working for Just Cause 3 with an existing profiles. I tried to create a G3D profile from scratch two times and gave up both times. My guess is that the engine was extended over a rather long time by multiple programmers with noone really paying attention to any kind of uniformity. Not uncommon for in-house engines, but in this case it’s so convoluted that there was always something left not working correctly no matter what.
Touch controllers are only handled in Oculus mode curretnly. I’ll have to revisit the SteamVR controller code shortly anyway though to add Index controller support. Since the Index controllers are rather similar to Touch (plus a bit of extra stuff), re-using their logic for Touch controllers in SteamVR mode probably won’t be not too hard. No promises, but I’ll see what I can do.
BTW: You can do the same with ALVR. Not sure whether there are any advantages over using VD if you already have that, but might be worth to check anyway,
DOn’t recall whether that may be necessary, but please try to run the game windowed by adding -windowed to its launch options in Steam. You can also set the resolution that way with -witdh x -height y.
Playing the game in Full VR mode is not really feasible since it’s third person and also rather UI heavy. You would at least need a field of view mod and a mod that provides mouselook without having to press the right mouse button for head tracking. Both existed for old WoW versions, but I’m not sure whether that’s still the case
Immersive screen mode is the best compromise for an actually playable VR WoW. If you want, you can pull the screen a bit closer for even better immersion.
Geometry 3D should have been selected per default. If that is not the case, please check whether your game executable is called wow.exe or wow-64.exe. Should be the case when you launch the default game through the Blizzard launcher.
I’ll check whether a recent patch has broken 3D. Unfortunately that’s always a possibility for games like WoW that are under constant development.