Forum Replies Created
-
Posts
-
Immersive screen is the default for most third person games. Playing third person games in FullVR is possible with the right FOV, but feels a bit odd since rotating your head rotates the third person camera around the player character. Fun to try and maybe you like it after getting used to it, otherwise immersive screen mode is the right choice for third person games.
FOV tweaks are always game specific, for about 150 games vorpX can do that automatically though. Can’t remember currently whether that’s the case for Batman:AA. If so, you can find an FOV setting on the DirectVR page of the vorpX menu. Please note that you don’t have to do anything if DirectVR handles FOV for a game.
BTW: If you haven’t done so already, I would strongly recommend to read the “Essential Hints Guide” in the help, which among other useful things contains further information regarding FOV in general.
SteamVR would indeed be the right device type for ALVR.
You can find then device selection option on the „General“ page of the config app.
Can‘t replicate this issue. First please try to enable ‚Alternative Hooking‘ in the config app. Note that this option should only be used in case of hooking issues with specific games. It‘s not better, just different. If in doubt always try both regular and alternative hooking.
If that does not help, get rid of Avast. Some AV programs falsely consider each and every new vorpX version malicious. If you want to avoid such problems entirely, exclude the vorpX program folder and the game folder in question from your AV scanner.
Please note that some more invasive AV programs may not allow you to really disable them or may require you to disable several modules and/or options.
A good alternative to invasive third party AV programs is Windows Defender, which comes free with Windows 10. It kicks in automatically when you remove your third party AV program. Unlike some other AV vendors Microsoft at least reacts fast and reliable when being made aware of false positives.
There have been no other changes in the last update than the ones mentioned in the changelog, none could have lead to more frequent crashes. I understand that it may seem to you as if the last vorpX version is the cause of your problem since it happens just now, but considering that noone else reports this that seems rather unlikely.
All I can really recommend is disabling any potential background programs, updating drivers and making sure no CPU/GPU overclocking is used while vorpX is running.
If you happen to have the Windows system restore functionality eanbled (unfortunately it‘s not per default on Windows 10 anymore), you could also try to go back to an earlier restore point from before your issue started to occur.
VorpX does a lot more than Tridef. Not only does rendering to the headset imply some extra work, in this particular case there is also the larger FOV applied by DirectVR. the larger the FOV, the more rendering work, which obviously costs performance.
For a 1:1 comparison you have to compare both programs with the same workload, which means vorpX in ‚Generic Headset (Desktop)‘ mode and without any DirectVR features enabled. And not even that would be correct since Tridef only renders half the horizontal resolution in SBS Mode while vorpX always renders two full res images.
That said, 20fps still sounds too low.
Alternative hooking can be enabled in the config app (‘General’ page).
IMPORTANT: Only try this in case of hooking issues with specific games. It is not better than the normal hooking method, just different. If in doubt always try both methods.
I just want to make sure that you aren’t caught by surprise one day, hence I’d like to let you know the current state of affairs every now and then: Microsoft ends official support next January, Oculus officially requires Windows 10 now (7 still works, but they don‘t actually care anymore), and Valve‘s current official stance you get in support replies regarding Index is that they don‘t actively prevent Windows 7 from working, but anyone using it shouldn‘t be surprised about ‚unexpected behavior‘. In other words, they don‘t really care anymore either.
I know you have valid reasons for disliking Windows 10, but using cutting edge tech like VR with an outdated OS will obviously not work forever.
Please check with the latest version and ideally not with Windows 7 (although it should still work). As mentioned above the game has been tested with 19.2.4. Quite rigorously actually since 19.2.4 contains a performance related change for Half-Life 2.
BTW: Neither Oculus supports Windows 7 officially anymore nor does Valve for the Index headset. Anyone still on Windows 7 should slowly start to consider the possibility of both runtime vendors finally phasing out Windows 7 support completely. The only remaining question in this regard is when it will happen. My guess would be sometime next year after the official Windows 7 end of life.
With all due respect, that is not a good advice. Half-Life 2 works terrific. Full 90fps practically guaranteed + perfect 100% memory scanner DirectVR with FOV and full tracking support. One of the games that even have basic roomscale support.
To avoid flicker you just have to follow the on-screen instructions shown in the top left corner of the desktop window and use a 4:3 resolution, eg. 1600×1200 or 1920×1440. With other aspect ratios (like your 16:9), the FOV will flicker.
For better readable menus (like always with small font menus) simply switch to EdgePeek mode while using the menu. No problem at all. Alternatively you could scale up the HUD, of course, but switching to EdgePeek for using menus is the better solution.
Try a factory reset in the config app. And if that doesn‘t help try a full uninstall/reinstall of vorpX (you can keep the registration info to avoid having to re-authorize)
Also try both windowed/fullscreen. Sometimes one may work while the other doesn’t in case of odd issues. There is definitely no general issue with these games.
If you disable the override, gamepads work natively.
However, the override exists for a reason, and if it is enabled per default it’s usually enabled on purpose. Some games do not allow mouse and gamepad to be used at the same time. If the override is enabled per default, the game in question probably is such a game. Using a gamepad with the override disabled in a game that does not allow mouse and gamepad to be used at the same time typically breaks mouse based head tracking.
If by any chance you are using a gaming laptop, please make sure that the games run on the dedicated GPU, not the integrated GPU. With some luck you might be able to disable the integrated GPU in your BIOS.
Not a known issue. Half-Life 2 and Black Mesa were both checked with the latest version before release.
If vorpX does not hook into the games, please first try to enable (or disable if you currently have it enabled) alternative hooking in the config app. Please note that the alternative method should only be used in case of problems with a specific game. It‘s not better, just different.
If that doesn‘t help, please check for anything that may prevent vorpX from hooking into games. The pinned trouble shooting guide above lists potential candidates.
It might also be worth noting that in SteamVR mode you can change the controller type manually in the vorpX menu. Per default vorpX tries to detect the controller automatically, but I could imagine that ALVR doesn‘t report a controller name vorpX recognizes. In that case switching the SteamVR controller type to „Oculus Touch“ in the vorpX menu should do the trick (provided ALVR handles it correctly).