Forum Replies Created
-
Posts
-
In several ways the best solution to your issue would be switching to the original DX9 Bioshock, for which vorpX provides better DirectVR support.
If you only have the remastered version:
Sounds like something is getting severely in the way if not even a hook helper helps. Try to disable everything you may have running in the background that potentially also hooks into games. E.g. any kind GPU utility, chat apps and generally everything that show overlays in game.
Try to enable/disable V-Sync in the game. If you happen have a G-Sync/FreeSync compatible monitor, it also make sense to try with and without.
Please try to reset the game‘s graphics settings to default. Since in general vorpX is able to hook the game, I‘d suspect this to be an issue with e.g. DLSS or some other graphics setting.
BTW: If you happen to have F1 2020, try that too. In contrast to F1 2021 it still supports DX11, which for vorpX means it still had true Geometry 3D. Slower than the post effect 3d in F1 2021, but looks a lot more natural.
In FullVR mode the game‘s camera field of view and the headset FOV have to match, otherwise the image will look distorted. For many supported games vorpX can handle that automatically, but for others you have to do it yourself.
The help that comes with vorpX contains two guides that explain how to do that. the first one is the ‚Essential Hints‘ guide, the second one the ‚1-2-3 Game Setup‘ guide. Read both, the first one is a bit more theoretical, the second is a practical step-by-step guide.
While vorpX tries to hook into any game, it might not be able to to so for unsupported titles for this or that reason.
Check whether maybe a user profile exists for your game in the config app on the cloud profiles page. With some luck someone got them working earlier and uploaded a profile.
SteamVR is not required for a Quest 2. Please follow these steps:
1. Make sure ‘Oculus’ is selected in the vorpX config app as your headset type.
2. If you want to use the wired version of Oculus Link, connect the Quest via USB
3. Launch the Oculus PC App.
4. Launch Oculus Link (wired) or AirLink (Wi-Fi) in your Quest.Afterwards your Quest is connected to the Oculus app and vorpX can send images to it via the Oculus PC runtime.
Caveat: AirLink requires a fast Wifi 5/6 connection with low latency. If you are unsure about that, better use wired Link via USB.
@ Demuse :
Could you briefly describe how to replicate the melee FOV glitch? As far as I can tell the FOV is only different during melee fighting while ADS is active. The game always changes the FOV during ADS, how much depends on the weapon. I thought about overriding that and keeping the FOV the same with ADS, but that would make sniper rifles and scopes in general pointless. During melee without ADS the game seems to use its normal FOV, at least I couldn’t trigger any glitch in that respect.
Unless you encounter some issue I don’t get here, you just have to release the ADS button for melee fighting, the FOV will then snap back to the game’s normal non-ADS FOV.
@ bakterius :
In case of Cyberpunk G3D is implemented by rendering each eye at a different frame, so per eye you effectively only get half the FPS the game runs with. If e.g. the ALT+F FPS counter shows 60/90 (the second number shold be the refresh rate of your headset), each eye effectively only has 30fps. Some motion can look a bit stuttery due to that. This can be partially tricked away, e.g. for head or controller rotation, but the effect can’t be eliminated entirely.
If you are willing to reduce graphics details more, you could try whether by setting the ‘FPS Cap’ to ‘Small Delay’ you can reach more than 60/90. The higher the FPS, the less obvious becomes the stuttery motion from the alternate frame 3d.
Thanks for the hints. The melee combat FOV change eluded me entirely, more of a stealth player myself… If there’s a way to detect melee, I’m fairly confident that can be addressed. Will check that one ASAP.
Unless the game does something weird when evaluating the start/menu buttons, you should be able to open the menus with long presses on start/menu after changing the mapping. Using your VR controllers would be another viable method for avoiding the doubly assigned gamepad buttons. On VR controllers that’s not the case.
Not sure about the scanning/highlighting glitch. Will take a look at that too.
For now I‘d like to ensure that defaults are enforced on update. Hence currently settings are overwritten. Will change in a couple of releases when things have matured enough.
There shouldn‘t really be anything you need to change in the mod settings menu aside from the resolution anyway.
2022/01/08
Version alpha 3 is now available for download with the following changes:
- Pitch (look up/down) auto-leveling added. If you prefer to play with unlocked pitch, you can disable this on the DirectVR page of the ingame menu.
- Keyboard shortcut for switching between G3D and Z3D (ALT+K).
Switching between AFR 3D and Z3D will be possible with the default vorpX G3D/Z3D hotkey in the next release (ALT+K).
Also pitch (look up/down) auto leveling will be available with the next release. If you prefer to play without, you’ll be able to disable it on the DirectVR page of the vorpX menu. Was a bit more complicated here than it normally is with DirectVR games, but now it’s finally working without unwanted side effects.
I actually considered auto switching based on player velocity, but that comes with its own oddities, so in the end I discarded the idea.
Like said above, the hotkey is a good idea though, at least for mouse/keyboard players.
As usual no comment on future development aside from that there will be future development. I just can’t tell you things I don’t know myself yet.
Big yes from me, but that’s subjective, of course. Neither Z3D nor AFR 3D are pefect. Both have their strengths and weaknesses.
Z3D can only do so much until its own artifacts become too strong. Hence the scale of objects close to the camera is off, at least if one wants to avoid that half the image becomes a glitchy mess. For everything more than two meters away or so Z3D is just as good as G3D. This kind of unrealistc 3D at close range is something one has to get used to. On the upside Z3D doesn’t come with any time related issues.
AFR 3D realistically shifts the camera for 3D and thus produces realistic 3D even at close range, but its major downside is that it can become fairly uncomfortable with fast motion since the images for both eyes aren’t rendered at the same time.
You can create a trouble shoot data archive with logs and system infos in the config app and send that via mail to support at vorpx com.
That should definitely not be the case. I’ll check tomorrow whether maybe a recent game update has broken some shader definitions and let you know. That can happen potentially when shaders are changed in a new game version.
What you could check right now if you have mods installed is whether the issue also occurs without mods. A mod causing the issue is another possibilty.