Please check whether you have set a 4:3 resolution like e.g. 1600×1200 or 1920×1440 as suggested by vorpX. That is not only vital for a flicker-free image, but also for the weapon hide feature in Black Mesa.
I’m having the exact same issue with the new weapon fov/hide feature with Black Mesa. I tried reinstalling the game, restoring settings and profiles, even restoring Vorpx to factory default settings and it didn’t work. The only way to get it to work is by lowering Image Scale in Vorpx to exactly 0.90 from its default 1.0. It doesn’t appear to be impacting the world fov too much whilst still using the cached directVR. There is still a slight positional flicker with the gun, but it’s a hell of a lot better than having a 6 foot gun.
I’ve just finished Black Mesa, that was a cracking game in vorpX.
I have been playing Black Mesa and am using the official Vorpx profile. The game was working fine and I got about halfway through the game when all the sudden the head tracking stopped working. When I move my head the screen barely moves. Also all of a sudden when I turn with my controller the screen moves super fast and is uncontrollable. Not sure if I accidentally pressed something wrong. I tried doing a direct scan but that did not fix the issue. I set the settings to default and then imported the profile again, but the problem still persists. Any ideas?
checked all of that and still wont work for me in fullvr mode in black mesa
would have to reinstall titanfall 2 again to check that one
ok maybe i missed something in the original release details as just tried black mesa again after resetting the profile and i can see auto hide works in immersive screen but not fullvr mode. does it not work in fullVR?
does this auto weapon hide feature actually work for anyone.
have tried it now with Titanfall 2 and Black Mesa and it does nothing, and the games are unplayable in vorpx as they are due to the giant hands and weapons.
I’m getting random crashing to SteamVR home lately, I thought it was only Deus Ex MD but it just did it to me twice in Black Mesa. It does it as well when in the VorpX menu in Oblivion, just wondering if anyone else is encountering this or if I should trouble shoot something I recently maybe did.
Just a heads-up that the feature has to be enabled on a game-to-game basis since it rquires some game specific settings. It doesn’t work automagically. Currently it’s enabled for the following games: Half-Life 2 (+episodes), Portal 2, Black Mesa Source, Titanfall 2, Fallout 4, Crysis, Skyrim Special Edition, Aliens: Colonial Marines.
Below is the list list of games that this feature will be enabled for in vorpX 21.2.0 (release tomorrow).
Tweakable options include the feature mode (off/auto hide/size and position only/always hidden), the auto hide timeout, the position of the weapon in 3d space, and weapon FOV and 3D-Strength for tweaking its size. Shouldn’t really be necessary to tweak anything though. Each profile has carefully chosen individual defaults that work just fine.
Games for the first release:
– Half-Life 2 (+episodes)
– Portal 2
– Black Mesa Source
– Titanfall 2
– Fallout 4
– Crysis
– Skyrim Special Edition
– Aliens: Colonial Marines
More games will follow shortly, I’m fairly confident that adding the feature will be possible for about 4 out of 5 potential candidates, i.e. first person G3D games.
Note that in this first release there is no UI for changing gamepad/key assignments, will also follow shortly. For the time being make sure to use a game’s default bindings, otherwise vorpX might not be able to reliably detect when the weapon is supposed to be shown/hidden under all circumstances.
Try to run the game windowed. There currently is an unfortunate bug where vorpX can sometimes lose connection to the headset if a game gets minimized (e.g. via ALT+TAB). Will be fixed shortly in the next vorpX update.
If that does not help, it might me a hooking conflict with some program your PC that also hooks into games. Portal and Black Mesa ar both DX9, Arkham Knight is DX11, so maybe there is something that gets in the way with DX11. The trouble shooting guide on top of this sub-forum has more details on the matter.
So, I’ve got VorpX working with the first couple games I tried. Works in Portal and Black Mesa, direct VR. I’m now trying Arkham Knight. I use the same process — Mixed Reality Portal is running but not SteamVR, I run the game, VorpX appears to hook, and the game opens with VorpX text on top. But when I put on the headset, I’m stuck in this dome looking at mountains and stars. Does anyone know what is happening?
Dear Ralf, thank you very much for your quick responds. I could not get it run that way but found a solution by start the game without steam. I made a link of bms.exe on the desktop: “C:\Program Files (x86)\Steam\steamapps\common\Black Mesa\bms.exe” -oldgameui.
This runs perfect now! What a fantastic game and what a fantastic tool vorpX is! And what a very good support here. Thank you so much.
Hi Experts,
I’m using Black Mesa via Steam, VorpX on Control and get the info that BM will start on the Desktop AND in VR-Headset. On desktop it looks than OK but my Valve Index is black. The complete Message (German) from Steam is:
“Black Mesa wird sowohl in einer Umgebung in Ihrem VR-Headset als auch auf Ihrem Desktop getartet. Die Leistung in diesem Modus ist eventuell nicht akzeptabel. Um dieses Spiel nur auf ihrem Desktop auszuführen, beenden Sie bitte SteamVR, bevor Sie das Spiel starten.”
I have Ryzen 7 and Nvidia RTX 3070. Is this known to anyone or has an Idea to solve this?
Thanks in advance. Northo
hello, I am using black mesa from steam and I use this link for the viewer, I do not use virtual dekstop, as mentioned I tried with all the vorpx settings but nothing to do, I continue to see the scene in a low resolution, the scene I see it in a square and not in full screen, the only way is to zoom in but obviously it blur everything