Forum Replies Created
-
Posts
-
It’s not so much about performance, but about having resolutions available that your actual monitor does not without fiddling. With the virtual monitor you can skip the whole tedious task of adding custom resolutions to your display driver manually.
In regard to the desktop viewer also about not having to do refresh rate conversions from e.g. 60 on your actual monitor to e.g. 90 on your headset, which causes subtle microstutter. With the virtual monitor the desktop and the headset always run smooth at exactly the same refresh rate.
1.
Sounds as if everything works as it should. With the desktop viewer vorpX now switches to its new virtual display, which supports all vorpX specific resolutions per default, let’s you easily add even more in the config app, and for a uniquley (at least I think so) smooth desktop experience runs at the refresh rate of your headset. Other displays are blanked out on purpose since 1. mirroring the virtual display on them is unlikely to work due to resolution/refresh rate mismatch, 2. that way games only see the virtual display, which makes using it in games hassle free.
If you don’t need/want that, e.g. because you want to show others what you do in VR, you can easily revert back to the prior behavior by disabling the virtual display in the config app. However, the virtual display is so useful in so many ways that I’d heavily recommend to only disable it if you absolutely need your other displays while in VR.
2.
That sounds weird. The desktop viewer should launch in immersive screen mode. Try a factory reset in the config app (trouble dhooting page).
Just realized that the issue might have been caused by a small change in the installer I made yesterday, will probably work now if you try again.
If not:
If you didn’t keep your web installer, you can get one from the link below.
If the issue is caused by your antivirus, that might not work either though. If you use something else than Defender, really just get rid of it. There is zero reason to use some extra annoying third party AV since many, many years.
That is definitely not supposed to happen, should return to the prior state normally. If that happens often, disable the virtual monitor in the config app.
Would be great if you could answer the following question so that I have a starting point for replicating the problem: how do you invoke the virtual monitor? By switching your physical monitor off manually or by launching the desktop viewer and then putting on your headset?
If you happen to use any other antivirus than the built in Windows Defender, try to
- Disable it (might be hard for the extra annoying ones)
- Exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX
- By far the best option: get rid of it. Windows Defender for all intents and purposes is more than good enough since more than a decade and I usually make sure any new release gets whitelisted by Defender if necessary.
Not really, that’s sheer luck with the default hooking mechanism. When using a hook helper or alternative hooking both hooks probably always occur in the same order, but if that’s the wrong one, trying default hooking until it works is your best bet.
Interesting. I’m surprised it hooks at all. May be related to some game overlay and depending on whether vorpX comes first it works or doesn’t (or vice versa). Just a guess though.
If you mean head tracking mouse emulation not working currently in desktop viewer: next update. That’s a bug, not sure yet why it happens. Either next week, or if that doesn’t work out, in a couple of weeks.
I see. Vulkan is not supported. The desktop viewer is the only option in that case.
Your actual monitor should come back after a while when something goes wrong with the virtual monitor. At the worst about 30 seconds after taking off your headset.
You can also disable the virtual monitor in the config app. It’s quite useful though since it comes with many vorpX specific resolutions predefined and runs at the refresh rate of your headset for a uniquely (at least I think so) smooth desktop experience.
Probably related to nVidia drivers 580.88+ causing a black screen in DX12 games with any vorpX version prior to 25.1.0. Fix here: vorpX 25.1.1 Available Now
Disclaimer: I have not tried the profile, and can’t say anything about its quality. Just got curious since profiles disappearing from the cloud might have indicated some server issue.
There is a profile named ‘Final Fantasy VII REMAKE (OLDDONT USE)’. Probably that’s the one bjr84 meant.
The game has a bug where beyond a certain FOV it doesn’t render all world geometry/messes up some LODs, hence vorpX caps the FOV at that bug-threshold. It’s either an FOV sightly below what would be possible on a Q3 or glitchy graphics. Probably not considered a bug by CD Project since the threshold lies well above the max FOV allowed in the game options, so it’s unlikely that they’ll ever change that.
All good, glad you got it sorted. Always a good idea to use a VR headset when checking a VR app, I guess. :)
I have updated the profile with the new HUD shader definitions. Should work again with a scaled HUD now, at least until some TESO update breaks it again.
An updated profile database should download automatically when you launch vorpX next time. If not you can grab the profile on the cloud profiles page of the config app, it’s named ‘The Elder Scrolls Online [vorpX]’, the [vorpX] indicates that this is the official profile you want for updating the shaders.