Forum Replies Created
-
Posts
-
Please make sure that vorpX has write access to the game’s install folder. If you installed the game under ‘C:Program Files’ you may have to run vorpX as admin for that. IIRC vorpX creates an autoexec.cfg in the game folder if everything works as it should.
The flashlight is working fine here with the savegames you sent, so there is no problem with the 3D-profile.
Resolution is handled by DirectVR, you can change it on the DirectVR page of the vorpX menu after successfully adding the 4:3 custom resolutions to you PC or setting the game’s display mode to windowed.
I can’t really do anything else than recommending what I recommended in the Reddit thread a few days ago already, sorry again.
In a nutshell: reset everything to default, DO NOT tweak anything afterwards, setup 4:3 custom resolutions for your PC and let vorpX do its job. The Black Mesa profile automates everything, it works out of the box.
If by any chance you had used some other 3D-software before with the game or maybe some image enhancement shaders or similar things, it might also be worth a shot to empty the Windows DirectX shader cache.
I’m really out of ideas now.
If the game crashes while you select a 4:3 res, you can do that before launching it with vorpX. Shouldn’t crash though, at least it doesn’t here, sorry.
As said above, using a 4:3 resoution like 1600×1200 or 1920×1440 is mandatory, hence the according hint when you start the game.
16:9 resoltions do not work. You should see a hint in the top left corner of the game window that suggests to use a 4:3 resolution (e.g. 1600×1200, 1920×1440 etc.) whenever you start the game with a non 4:3 res. Please take this hint seriously, it’s shown for a reason.
Using a 4:3 resolution is ABSOLUTELY MANDATORY for any Source 2 engine game, otherwise the DirectVR FOV does not get applied correctly.
Such things usually are related to special shader definitions not being applied, e.g. when they become invalid after a game update. Hence using the latest official (non-beta) version is important. If you havn’t done that already, please also try to reset everything to default. vorpX as well as the game options (aside from the 4:3 resolution).
There is no need to apply any tweaking at all for this game aside from using a 4:3 resolution. The default profile with default settings is perfectly fine.
If that still does not help, I’m happy to check your savegame(s) here.
One more thing: if by any chance you are currently using one of the game’s beta branches, please opt out on the ‘BETA’ page of the game’s properties dialog in Steam (right click the game name > Properties > BETAS).
If the issue still occurs after thoroughly double checking everything in the trouble shooting guide, please send your trouble shoot data archive via e-mail to support |at| vorpx com. Maybe I can spot something you overlooked.
The most likely cause of an issue like that is a conflict with some other software on your PC that also hooks into games and thus creates a conflict with vorpX.
For more detailed informations please check the trouble shooting guide, especially the part about potentially interfering programs.
First please make sure to use the latest paid Black Mesa on Steam. The right graphics API would be DX9, but I don’t think that can be changed anyway. Older free versions are unlikely to work correctly.
If you already use the latest paid Black Mesa, it would be great if you could send a savegame to support |at| vorpx com. The flashlight works fine here at the beginning of the game after getting the suit, but who knows.
Whether DirectVR is available for a game and if so to what degree heavily depends on the game. E.g. the memory scanner can only work if it’s possible to figure out camera properties in the game’s memory, automatic .ini edits are only possible in games that have .ini files vorpX can understand, and so on.
You can find the C API documentation including sample snippets in the vorpX help.
How did I learn to code for VR? The best answer to that is probably: by doing it. Work on vorpX began with a do-it-yourself headset before consumer VR as we know it existed. I had some experience in coding plugins for 3D-software and renderers before though, which was a good foundation.
It’s not supported officially, but you should be be able to do that by adding ‘-output all’ (without the quotes) as parameter to the shortcut’s ‘Target’ field. If you want to display a specific monitor in the headset, use ‘-output n’, with n being the monitor number (starting with 0).
Note that all monitors have to be connected to the same GPU as your headset. Won’t work across multiple GPUs.
If by any chance your using a laptop with two GPUs, please make sure that the games actually run on the dedicated GPU, not the integrated GPU. vorpX apparently hooking into games, but not showing in the headset sounds a lot like that kind of problem.
The way best to make sure you are running games on your dedicated GPU would be to disable the integrated GPU. Not all laptops allow that, but you might find such an option in your BIOS.
Red dead redemption
Cyberpunk 2077Too niche. ;)