Forum Replies Created
-
AuthorPosts
-
tomba4Participant
FYI, turns out that the issue was only with that particular game – when I tried another one, everything worked without any problems (at least using Link, haven’t tried Virtual Desktop yet)
tomba4ParticipantI’ve disabled the second GPU and have no apps that I can think of that could hook into games. I’ve disabled HIPS from Eset’s Smart Security AV (together with other types of protections) and that helped with CPU usage from the vorpX drivers (i.e.., they are no longer using 100% CPU), but that didn’t change anything either…
Is it possible that some games simply won’t work? I only have one title that I can test at the moment…
tomba4ParticipantThanks for hints, unfortunately still no luck. I still feel something is really wrong with the drivers’ CPU usage: Ralf, you say that they should take 5% on a quad core – I’m on 24 core here, so 5% is A LOT: the processess actually use 100% of their assigned CPU cores (I assume they are both single threaded)
Can you just tell me if I’m doing something wrong?
1. I set up vorpX to Oculus device
2. I connect Quest with Oculus Link, I can see my Oculus home in the headset
3. I set up a vorpX shortcut to the game executable
4. I load the game profile from the cloud (profile created with vorpX 18.1.5), I confirm that the executable name is the same as the one in the profile
5. I start the game with the vorpX shortcut – nothing happens in the headset, the game starts on the main monitor as usualHave I missed a step?
I tried alternative hooking method and running vorpX as admin – no difference. If I alt-tab from the game (running in the full screen), I can see the vorpX window saying that it’s trying to hook to the process, but nothing is really happening…
(ps. I haven’t tried disabling the second GPU, it could be a bit of a problem for me)
tomba4ParticipantThe headset is not connected to the GPU in my case (it’s either USB or wireless). Normally games always launch on the same GPU (the one on which the main monitor is connected to), but how does vorpX work in this case? In the task manager I can see the game assigned to a specific GPU engine, but that field is always empty for vorpX…
How did you make it so that correct GPU is chosen most of the time? And do the vorpX processes eat all CPU in your case as well?
-
AuthorPosts