Forum Replies Created
-
Posts
-
You could try to scale up the HUD on the image page of the vorpX menu, but that doesn’t really solve anyting sinve then it will move out of sight and you need EdgePeek anyway.
You have to raise the game resolution somehow. If you are using an nVidia GPU, you should be able to add the 1920×1440 resolution. If that’s the case, please double check that you followed each single step in the instructions precisely.
If for some reason it still does not work or you have an AMD card, you can enable a feature called “Dynamic Super Resolution” (nVidia) or Virtual Super Resolution (AMD) in your GPU control panel for higher resolutions. That’s not as good as adding a 1920×1440 custom resolution, which would avoid rendering unnecessary pixels, but will at least also allow to create resolutions higher than your monitor allows.
Did you actually read my reply above? if the game has a scalable HUD (I’m not sure, but I think it has), vorpX makes it smaller so you can fully see it in the headset.
You can switch to EdgePeek (mousewheel click) to have it shown at full size.
Also check the “Custom Resolutions” section in the help (or here) like suggested above to learn how to add higher resolutions (provided you have an nVidia GPU). 1920×1440 makes the game better regardless of HUD issues.
DirectVR takes care of that in both games. In HL2 via the memory scanner, in case of the Bioshock remaster via auto editing the game’s ini file. You should have seen a message in the top left corner of the game window and in the headset that prompted you to restart the game when vorpX adjusted the FOV setting in the .ini.
BTW: if possible use the original Bioshock in DX9 mode, that’s the best way to play Bioshock with vorpX
BTW2: To learn a bit more about FOV (field of view) and why it is important, check the “Essential Hints Guide” in the vorpX help, or alternatively here
Maybe your antivirus or firewall blocks the update. Excluding the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) from your AV program may help.
if not, reinstalling like steph12 suggests will help. You don’t have to uninstall first. If you need a new installer, you can get one here: https://www.vorpx.com/request-new-download/
Run the game at a higher resolution. 1920×1440 is usually a good resolution for vorpX. If your PC does not support this resolution, check the “Custom Resolutions” section in the help for detailed instructions how to add it.
Apart from that: If the game supports a scalable HUD (can’t remember currently whether that’s the case here), switch to EdgePeek mode (mouse wheel click) for using menus. That’s good advice anyway since it’s more comfortable for using menu.
Just in case: If you have any mods installed, try without mods.
Apart from that: 4:3 resolutions are a must, but you already did that apparently. if the FOV still flickers, try to rerun the DirectVR scan. Shouldn’t be necessary, but who knows. You can empty the cache on the DirectVR page of the vorpX menu and then run a new scan (after entering an actual level, doesn’t work in the menu!).
If you want to watch Youtube in your web browser, you can use the vorpX desktop viewer (Windows 8+). Alternatively The Oculus software also has a desktop viewer built in, probably also Windows 8+.
If you want to watch movies downloaded to your PC, you can do that the same way, use MPC-HC or VLC with vorpX (supports 3D movies) or use one of several dedicated VR video players. You can probably even find some free ones in the Oculus Store.
I can only give you the answer I gave you above twice already. If you want vorpX to behave like before, turn FluidSync ‘Off’. That is what happened before even if you had selected ‘Auto’.
Again: in contrast to most other headsets, which mostly work fine without FluidSync, WMR headsets don’t really like uneven framerates, hence FluidSync in now on per default for WMR. I highly recommend to leave it that way, but if you prefer the prior state, ‘Off’ gets you back to that.
The ‘Auto’ setting didn’t really do anything in the last version on your headset. ‘Auto’ basically was the same as ‘Off’. Now ‘Auto’ checks whether a game can reach 90fps and based on that decides whether FluidSync should be turned on or off. If you want the old behavior, set it to ‘Off’.
For the reasons explained above I would highly recommend not to do that though. While Oculus, Vive, Index etc don’t really need FluidSync, WMR headsets never worked well with uneven frame rates. FluidSync on is best for WMR, always has been.
In a nutshell: best to leave everything at default, but if for whatever reason you don’t want that, ‘Off’ gets you back to how things were with the last vorpX version.
For WMR headsets like your Dell vorpX now turns on FluidSync per default since that provides a better experience on WMR headsets. Oculus, Index, Vive etc. don’t really need it for the most part, but for WMR FluidSync is usually the better choice, hence it is the new default for WMR. WMR headsets just don’t work well with uneven frame rates, they never did.
FluidSync being on per default now is the only change in regard to your WMR headset and I would highly recommend to leave it on. The numbers may tell you your game runs slower, but the actual experience is (and always has been) considerably better and smoother with FluidSync enabled on WMR headsets.
Dir auch frohe Weihnachten! Ich antworte mal auf Englisch, damit es jeder lesen kann:
I don’t really have an exact number, but my guess would be that scalable/3D HUDs are available in about 200 or so official profiles, probably more. Also in many user profiles if the profile author took care of it. That has to be manually defined per game though, so it does not automagically work for every game.
Thanks for insisting that there has to be an issue. I checked several OpenGL games before release, but apparently never checked EdgePeek with them. The issue is already identified.
I’ll update the setup without bumping up the version number in an hour or so, so no auto-update. Please use your web installer to reinstall. If you need a new one, you can get it here: https://www.vorpx.com/request-new-download/
It’s not up yet, but will be in an hour or so.
Settings are stored in a database, no ini to edit.
BTW: You can save profile settings to your PC by dragging the profile name entry from the ‘Local Profiles’ list to your desktop.
You can cancel the Oculus reinstall. Seems to be related to the game using OpenGL. I’ll check what’s going on in detail and prepare a hotfix ASAP.
Not a supported game, but I’ll check it tomorrow. Sounds like some really weird head tracking issue. When you press the EdgePeek button what actually happens is that the camera gets pulled back. Nothing really changed in that regard. Probably a coincidence that you have this issue just now.
If you have any other software running besides vorpX that potentially affects head tracking (e.g. OpenTrack or something similar), please also check what happens without that.
Please also try to re-run the Oculus headset setup to ensure everything is OK in that regard and also check whether recentering tracking helps in vorpX (ALT+SPACE).