Forum Replies Created
-
Posts
-
There is an option in the config app that let’s you enable the virtual monitor manually from the vorpX tray icon. That way you can treat it as (invisible) normal second display.
BIG HUGE CAVEAT:
Windows restricts resolutions when mirroring displays to the resolutions supported by the less capable one, which obviously largely defeats the purpose of the virtual monitor. What you would have to do instead is extending displays and then use the Oculus/SteamVR mirror window on the actual monitor.
Since the virtual monitor is meant to simplify things, not making them more complicated, that’s not the default behavior, but with a bit of tinkering you *might* be able to make it do what you have in mind too.
I think you misunderstood. He’s just asking about playing a Steam game without loading Steam VR
If that was indeed the question:
SteamVR is not supposed to run at all when using a Quest with Link. Make sure that vorpX is set to Oculus mode in the config app. Do not launch SteamVR, it not required and should not be running. SteamVR is only supposed to be used with native SteamVR headsets (e.g. Valve Index).
For “bypassing” Steam to launch your games you have to ask elsewhere. For obvious reasons there is zero tolerance when it comes to discussing such matters here. so don’t even try. :)
As far as the Oculus PC app is concerned, that’s just how things are. vorpX uses the Oculus PC runtime, and that doesn’t work without the app being open. They want you to see their store whenever you use the headset. Kind of redundant since Quest, which has its own store obviously, but that’s how it is.
You don’t really have to worry about performance though. While games are running both the Oculus app and Steam just sit there doing nothing except costing memory. If you happen to have only 8GB, consider a RAM upgrade. That’s insanely cheap these days. If your PC has 16GB or more, you don’t really have to worry about memory consumption either.
@ Austint:
Try the vorpX beta. It has a rewritten desktop viewer and comes with a new virtual monitor. Together these should resolve most performance issues with the old desktop viewer.
The desktop viewer itself is now a lot better at handling high GPU load, while the virtual monitor helps with otherwise inevitable micro stutter by running at the same refresh rate as your headset. Provided you can make a game run fast enough (at the headset refresh rate) that’s the best desktop capture you ever experienced.
For convenient usage per default the virtual monitor kicks in when you launch the desktop viewer and then switch off your actual monitor (requires the actual monitor to be connected via display port). You can further configure its behavior in the config app and also enable it manually.
That’s not gameplay recording. That’s a photomode camera mode doing this:
…multiple perspective views with a smaller FOV at the same time and then stitching those together and convert them to spherical projection…
also:
…entirely out of vorpX’s realm.
Games only render the field of view that you actually see, they don’t provide the means to render a 360° spherical projection. The perspective projection used in games also only works up to 180°, and even that – quite literally – is already a stretch.
If you would render a game with the maximum per view 180° FOV instead of the correct headset FOV the image would be heavily warped/zoomed out in your headset while playing. Also you would have to convert the recorded video to a (semi-)spherical projection in post, which – to make matters worse – wouldn’t even work well from a single image rendered at 180°.
What you would actually have to do is either reimplementing a game’s renderer so that it does spherical projection directly or rendering multiple perspective views with a smaller FOV at the same time and then stitching those together and convert them to spherical projection. Both things are entirely out of vorpX’s realm. Also both would be quite slow.
@ kurry:
The beta comes with a new virtual monitor that is also useful if you just want to play in immersive screen mode. Massively simplifies handling of resolutions larger than your actual monitor allows since it has all relevant resolutions predefined. The virtual monitor also always automatically runs at the refresh rate of your headset, which as an added benefit reduces judder when using the desktop viewer.
BTW: For DX9 games on Windows 11 the beta is more or less a must. The regular build has severly reduced DX9 performance on Windows 11.
Not sure if I understand te problem. Normally using the controller buttons shiuld work just as using keys, i.e. a key is registered as down as long as you press the button.
Also also not sure why you want to use the keyboard emulation in the first place. The mod works perfectly fine with the default gamepad emulation.
Sounds like the game can’t handle simultaneous gamepad and mouse input. Without DirectVR head tracking, which only works for Halo 1, vorpX emulates a mouse.
To deal with that vorpX comes with a decently feature rich gamepad > mouse/kb mapper built in. You can enable it with the ‘X-Box Gamepad Override’ option on the input page of the menu.
If you’re lucky, a partial override of the sticks will suffice. If not, you probably have to adjust some button mappings.
The Game Pass version might be compiled as Windows Store (UWP) app, which can’t be hooked. Not all Game Pass games are, but Halo MCC might.
If Game Pass allows you to select between a moddable .exe and one with anticheat, try the moddable one. vorpX definitely won’t be able to hook the anticheat version. Part of usual anticheat mechanisms is preventing other apps from hooking into games.
The Steam non-anticheat .exe definitely still works. You should be aware though that only Halo 1 is officially supported. I know for sure that Halo Reach also works, but I never tried Halo 3 myself. Individual games in Halo MCC are unfortunately handled in a way that makes it difficult for the vorpX profile to cover potential technical differences between the games. So I can’t guarantee that everything works as expected in all campaigns.
BTW: Make sure to run the game windowed. I just noticed that important things like FOV and other settings might be off if the game in running fullscreen.
Can’t replicate that here. Please try to reinstall the mod and don’t make any changes to input related settings.
BTW: In general be *very* careful with changing settings. The only things you should adjust in the menu are the resolution quality according to your PC’s performance, potentially headset sync related settings, amd maybe image enhancement/sharpening. There isn’t really much of a reason to change other settings than these.
No problem here. Just checked to be sure.
Unreleated but important: If you are on Windows 11, use the 23.1.0 beta. The last regular build has severely reduced DX9 performance (-50%) with Windows 11.
As far as your issue is concerned: Hooking issues with games that are known to work well in general almost always means there is a conflict with some app on your PC that also hooks into games. More information in that regard can be found in the troubleshooting guide on top of this sub forum.
ME1+2 should work fine, can’t recall what the issue was with ME3, might just have been some .exe naming conflict.
That aside, ‘better’ is a fairly individual term here. ME2+3 are basically the same games with higer res textures and slightly better lighting, but in turn much worse performance. ME1 on the other hand received a significant gameplay overhaul for the Legendary Edition.
One could very well argue that because of the much, much better performance the original games are generally better suited for VR, just for ME1 using the LE is actually worthwile due to its modernized gameplay.