Forum Replies Created
-
Posts
-
Super weird. Can’t replicate the ‘ESC’ key issue, but get the ‘E’ key problem in New Vegas too. No idea why yet, but will be looked into ASAP next week.
When swapping versions be aware that while great care is taken that vorpX stays backward compatible to older profiles, it is obviously impossible to guarantee forward compatibility. I.e. profiles/settings saved with 25.1 may not work correctly in older vorpX versions.
Please try the above suggestions. My guess is that your antivirus interferes with finishing the installation, e.g. starting the vorpX service.
Might be some antivirus program feeling the need to be annoying. Windows built-in Defender works fine curently, just checked to be sure. If you happen to use something else, consider getting rid of it. Defender does the job perfectly well. No need for invasive third party antivirus programs since about a decade.
Alternatively try to disable your antivirus during the install and exclude the vorpX program folder, which per default would be C:\Propgram Files (x86)\Animation Labs\vorpX.
In FullVR mode game FOV and ImageZoom belong together. There is only one correct ImageZoom value for a given game FOV value and vice versa, so that game FOV and headset FOV match like in native VR games.
That’s actually the purpose of the ImageZoom option. Allows you to play pretty much any game with a headset matched FOV, even if a game doesn’t let you adjust its FOV high enough to match the headset FOV when filling te entire screen.
If e.g. you encounter a worst case scenario game with a fixed FOV of let’s assume 75° that can’t be changed at all, you simply lower ImageZoom until looking around doesn’t give you a fisheye/warping-feeling anymore.
In case of Cyberpunk (and many other games with official profiles) vorpX automatically ensures that game FOV and ImageZoom are in sync.
Cyberpunk has an issue where a camera field of view above a certain point causes visual glitches in the form of missing/borked LOD models in some places. Hence the FOV (and thus the ImageZoom) is capped at a value slightly below the graphics glitch occurs. Better than glitchy graphics.
The Cyberpunk devs probably don’t consider that a bug since it occurs above the FOV the game allows to set normally.
If you still encounter your issue after letting vorpX do its job without tinkeríng, please send an e-mail with a trouble shoot data archive to support at vorpx dot com. You can create a trouble shoot data archive in the config app.
To tilt the screen, make sure Play Style is set to ‘Immersive Screen’, click on ‘More Immersive Screen Settings’ and then use the ‘Screen Tilt’ option. That always works and has nothing to do with your game’s ultrawide issue.
Please still don’t disable automatic settings, which you apparently did when you dialed in the FOV manually. Just don’t do that. The according huge warning displayed by vorpX exists for a reason.
Also reset the game’s graphics settings to default. Doesn’t matter what you did or did not before, I can only consider your issue a bug if it occurs wben things are set up as they are supposed to be set up. Thanks for your understanding.
If you still encounter your issue after letting vorpX do its job without tinkeríng, please send an e-mail with a trouble shoot data archive to support at vorpx dot com. You can create a trouble shoot data archive in the config app.
Try both the game settings and the profile settings at default and DO NOT disable automatic settings.
FOV in FullVR mode is calculated to perfectly match your headset with auto settings. No need to guess it manually. You can’t guess better than the calculation.
That aside:
I’ll look into it.
The left grip button on the Quest controllers acts as mapping-shift. while pressed the triggers are LB/RB. You can check the badges displayed on the controllers to check what each button/axis does.
I’ll look into. Might be some depth buffer issue.
In the meantime check whether resetting the graphics settings to default helps. I didn’t encounter something like that, so there’s a fairly good chance that some graphics setting triggers the issue. Also make sure not to disable vorpX’s automatic game settings. These often ensure that 3D works as intended.
BTW: At least for me there was no 3D at all with the FS22 profile in FS25. To get that simply turn off 3D in the vorpX menu.
You can do that by checking the ‘Allow manual activation’ checkbox in the config app. Afterwards you can enable/disable the virtual display from the vorpX tray icon’s right click menu.
*VERY* IMPORTANT CAVEAT:
Having an invisible display attached as an additioal monitor introduces various pitfalls, which is why things are handled like they are handled per default. Only do that if you have a very good reason and know what you are doing.
… Thinkable that the game you try takes the display’s default res to determine its aspect ratio instead of the actual res …
… or maybe its highest, its lowest or whatever.
That aside:
If you are in any way unhappy with the result you get using the virtual display in a specific game, and you also don’t want to use the alternative suggestions others took the time to lay out for you, then simply don’t use the virtual display for that game.
There are plenty of games where ultrawide resolutions work perfectly fine with the virtual display. Your issue very obviously is related to something your game does, whatever that may be.
Again for your convenience, in case you missed that before:
- A monitor driver is just a monitor driver. All it does is reporting its list of resolutions to a game. What a game does with that is entirely up to the game.
- Setting the default res for the virtual display, which might or might not make a difference re your particular game, is already on the requested features list, not with high priority though.
Hope that helps.
As said above the virtual display is just a display. How games handle ultrawide resolutions is up to the games obviously. A display driver couldn’t even affect that if it wanted to.
Thinkable that the game you try takes the display’s default res to determine its aspect ratio instead of the actual res, is fixed at 16:9, or, or, or. A game can do a million things to break ultrawide resolutions if it wasn’t developed with ultrawide in mind. There are entire websites dedicated to nothing else than ultrawide patches for games that can’t do ultrwide correctly per default.
If this particular game doesn’t handle ultrawide like you want it to, instead simply stick to a slightly higher 16:9 res, move the screen a bit closer and if possible set teh FOV a bit higher. Then you get exactly what you wanted to achieve with the added benefit of more vertical screen space.