Search Results for 'sk'

[CupeDeNoodel]

I managed to get in using Hook helper at generic mode.
The d3d 10/11/12 mode just says incorrect video.

Once I am in the game all the characters on the menu looks black.
No texture whatsoever.

But in game i can see everything clearly.

But the game crashed in under a minute.

This happens every single time.

Replicated it maybe 6 times. Crashed to desktop all 6 times.

Specs:

Core Ultra 265k
RTX 5080
64GB 6000mhz cl30
980 pro nvme

[Ralf]

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.

[Ralf]

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).

[Ordalix]

Hello,
I have 2 problems since the last update.

1. When I launch Vorpx Desktop Viewer, my PC screen simply turns off (this wasn’t the case before).

2. The display in my VR headset is stuck in “head-tracking mode” (sorry, I don’t know the technical term). That means I can see my desktop, but when I move my head, the desktop moves as well. Whether I switch to VR mode, immersion, cinema, or anything else, it doesn’t change.

Thanks for the help

[Ralf]

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?

[Benedict81]

For some reason, when using the virtual desktop now (and my monitor is shutdown), after exiting the virtual desktop, my actual desktop goes to some really low resolution, sometimes so low that I have to reboot the whole system coz I can’t see what I am trying to do (change the desktop resolution back to normal). A small weirdness, but a strange thing nonetheless.

[vintager]

Thank you! Would be great if you could fix head tracking –> mouse look in the Desktop Viewer then :) Thank you in advance!

[Ralf]

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.

[vintager]

Any chance we can get head tracking working in Desktop Viewer? It doesn’t translate into mouse movements.

[Ralf]

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.

[vintager]

Thank you! With the new version, luka’s Indy profile doesn’t hook at all–but if you open the Desktop Viewer and start the game from there, it opens in Full VR mode! No stereo, of course, but that’s to be expected. The problem is, the Desktop Viewer kinda crashes, and the monitor remains in sleep mode, so you can’t exit & restart the game if needed.

But since Indy works (sans stereo), how does one go about creating a proper profile? It’s Vulkan, etc.

[ENBSeries]

@Ralf
I’m very sorry for wasting time, false alarm. Didn’t wear helmet before, because usually skip while games are in the menus, so didn’t know about new behavior of the Vorpx, which requires to press some buttons in the new vr windows and until then input is partially locked.

[ENBSeries]

@Ralf
Uninstalled, rebooted then installed again – no luck. Also noticed with SpaceEngine (running in windowed mode) after game is loaded height of the game window is reduced maybe by 10-25 pixels (can’t tell for sure about width). Also vanilla game allow mouse cursor go to any area, while with Vorpx it’s limited to client area where game front buffer is displayed.
Here is the list of the process in the task manager, as you can see I keep pc clean as much as possible, so there are no other apps which could mess with input or hooking graphics:

View post on imgur.com

[ENBSeries]

@Ralf
Regarding issues with non functional input. If I keep old version of vorpControl64.dat, then issues do not happen. Maybe there is another combination of files, didn’t test more.
The same problem happens in A Hat in Time. Reinstalling Vorpx via web setup multiple times – no difference. Even Vorpx own ctrl+alt+shift popup message ignores keyboard in A Hat in Time game. The only thing suspicious to me is when first time after long break started Vorpx and it initiated an update, at some stage of installation terminated it manually because was busy with other pc tasks. Still, that don’t explain why problem remains after executing web setup later, after reboot as well. As mentioned earlier, in the SpaceEngine some actions do work in certain moments, like game first popup warning with Esc button to hide it fails, then main menu works for cursor and mouse buttons both, then in-game cursor works but mouse buttons and keyboard are dead. I know some of the last patch(es) of Win11 (I’m on Win10) have changes to GetAsyncKeyState, breaking some apps, maybe workaround was done on Vorpx and it do not works in my case.

[Ralf]

Yes, it’s supposed to resume after exiting a game. Also the auto recentering every 5 seconds is not supposed to happen, only once when the desktop viewer switches to the virtual monitor. For the lack of a better suggestion, try a uninstall/reboot/reinstall. Maybe the background service didn’t update correctly for some reason. Both the not-resuming part and the recenter issue point at something being wrong service wise.