Forum Replies Created
-
Posts
-
Sounds like the profile database may have been corrupted. Try a factory reset: config app > trouble shooting page.
Must be something getting in the way on your machine. Steam version works fine, checked 2 minutes ago with vorpX 25.1.5.
Thanks. The desktop viewer/virtual display combo has indeed a few tricks up its sleeves that make it truly unique. Glad you noticed.
Definable virtual monitor default res:
Already on my radar, will come with the next release.
Over/under in FullVR:
I’ll look into it. Sounds like a bug indeed.
Monitor enable hotkey:
The monitor should always come back on after a while (max 30 secs IIIRC) when you take off the headset. There are several safeguards in place to ensure that. A hotkey is a bit of a double edged sword here as you wouldn’t want to hit it inadvertently while playing. Still noted, some unlikely key combination may be a good idea for this.
Crosshair:
If crosshairs are seperatable from other HUD elements, you might be able to disable them yourself with shader authoring (requires expert settings enabled in the config app). Not possible for all games though, lots of games use the same shaders for HUD and crosshair.
Force cap at 60 fps:
That is already possible via the Frame Sync options in the vorpX menu. You can cap the game framerate at a fraction of the headset refresh rate. If e.g. your headset is set to 90, choose 2/3 for a 60 fps cap.
Windows joystick device:
Sounds nice-to-have, but lots of stuff with higher priorities, so no promises in that regard.
Desktop Viewer VLC/MPC
Normally vorpX should should hook the players and then come back to the desktop viewer after closing them, just like what happens when hooking into games. I’ll check whether I can replicate your problem, never heard of an issue with that until now though. As a workaround you can disable hooking from the vorpX tray icon right click menu. That way you can use MPC/VLC without vorpX hooking into them.
In case you upgraded you PC you may need a new key. To get a new key simply follow the instructions in the license dialog that pops up when you lanuch vorpX.
The game has special gamepad handling. It actually does not act like mouse and keyboard, just turning works somewhat different to how gamepad turning works flat. That is a requirement due to how vorpX works in this particular game.
If you happen to already have made any input related changes in the vorpX settings, reset the profile to default. Everything is preconfigured as it is supposed to be.
—
BTW: I have removed your other post. Please do not post about the same issue in multiple threads. Thanks! Just makes it harder to reply.
As said above, the desktop viewer should not, must not (and as you noticed actually can not) be excluded.
If vorpX can’t attach to it, something is very, very wrong. Most likely candidate is some invasive third party antivirus program that gets in the way. If you happen to use anything else than the built-in Windows Defender, get rid of it.
While usually everything is supposed to work with normal user rights, running vorpX as admin might also be worth a shot. Should not be necessary, but just in case.
Nothing to suggest otherwise. There must be something on your machine that gets in the way.
Try thorugh a native API (SteamVR in your case). Virtual Desktop might clash with vorpX’s virtual monitor. Exit the VD Streamer entirely.
If that does not help, and your laptop has a dedicated GPU (most gaming laptops do), the issue is probably caused by your desktop running on the integrated GPU while your headset is connected to the dedicated GPU. Disabling the iGPU in your laptop’s BIOS might help in that case.
The desktop viewer should not, must not (and as you noticed actually can not) be excluded.
The game engine has an insane amount of D3D draw calls per frame, I think the highest I ever encounterd. Since draw calls are essentialy doubled with G3D and on top of that some work is done on the vorpX end per draw call, this is the absolute worst case scenario CPU wise. GPU doesn’t really matter much here. G3D performance in this game is CPU bound.
Try to reduce everything in the game’s graphics options that affects how much stuff is drawn on screen. View distance, NPC density, things like that.
BTW: Lot’s of work has been poured into micro-optimizing CPU performance in the last months, so the next vorpX will likely run a bit better in this scenario, but don’t expect wonders. AC:Unity’s engine just isn’t well suited for any draw call doubling stereo algorithm.
The gamepad override affects actual gamepads as well as emulated gamepad input.
Its main purpose is to ensure mouse based head tracking can work while using a gamepad in games that can’t handle simultaneous mouse and gamepad input. This issue exists for both actual and emulated gamepad input in affected games.
In case of Fallout 3 simply leave everything at default (Really!). After running the memory scanner vorpX does not use mouse emulation head tracking anymore in these games, so that gamepads works natively and motion controllers work in gamepad mode.
There is no need to tweak anything at all in this respect for Fallout 3/4/NV. Reset the profile to default, run the memory scan and you are good.
Sounds like maybe vorpX‘s virtual monitor kicks in. Should per default only happen when you use the vorpX desktop viewer, but to make sure that‘s not the issue, you can try to disable it entirely in the config app on the Virtual Display page.
You can try a little trick to exclude narrator.exe by creating an empty textfile (or use any other file) and rename it to narrator.exe. Caveat: displaying file extensions in the Windows Explorer options has to be enabled, otherwise you might end up with a file named narrator.exe.txt.
Yep, no DirectVR 3D without the connection mod. vorpX needs to communicate with the game. That’s also why camera mods almost certainly will interfere.
Always a bit difficult to assign time for something purely cosmetic as this. Will probably take about a full week to make the app themable in the first place and then finalize and tweak everything.
Already moved up the priority though, considering how common dark themes are these days at some point it clearly has to happen. Thanks for the reminder.
Will cost quite a bit more time than one may think, hence on the nice-to-have-list for quite a while. But I guess it’s about time…
Will *probably* (meaning 80% sure) be in the next update.