Forum Replies Created
-
Posts
-
As dellrifter suggests the profile might have been made for an earlier version of the game and not work anymore with the release version.
In general it’s best to consider unofficial profiles made by users “might or might not work”. Most will, but there is no guarantee.
Looks like I didn’t remember correctly. I uploaded a profile to the cloud that uses the new method. A brief test including entering/exiting various menu screens a dozen times and loading a savegame worked here now without losing depth a single time.
Feedback welcome.
IIRC I checked Mankind Divided without success after implementing the new method, but I’m not 100% certain anymore. Will look at it early next week to be sure.
If I understand OculusRiftRocks correctly, you need to download and install the renderer from the site he linked above, enable DX9 and use the Halo profile in vorpX (or rename the game’s exe).
Never tried that myself though, so I don’t know whether it really works.
Just a guess, but maybe using vorpX in SteamVR mode helps (selectable in the config app). Sounds like some odd sync issue, which might not occur when using SteamVR instead of Oculus natively.
The only recent gamepad related change was a fix for gamepads not working correctly in some Direct VR titles (e.g. Portal 2). Didn’t have a chance to check yet, but incidentally I got another remotely similar sounding report yesterday, so I will check whether that fix maybe had any unwanted side effects.
Unfortunately I can’t give you any other answer at this point than the one I gave you above already.
I’ll check whether there may be circumstances that don’t allow to disable the gamepad override, but TBH I have no idea how that may be possible. Also haven’t heard of anything like this until today.
This still works as it always did. Automated settings have nothing to do with the gamepad override. I’ll check whether there may be circumstances that don’t allow to disable the gamepad override, but TBH I have no idea how that may be possible. Also haven’t heard of anything like this until today.
For now all I can suggest is to do a full factory reset. Maybe that helps for some odd reason.
I’d also like to reiterate that there always is a good reason for the override being enabled per default in a profile. Otherwise it wouldn’t be enabled in the first place.
@ xrc6: vorpX only changes the way the gamepad is handled while the gamepad override is active. That hasn’t changed recently. With the gamepad override disabled the gamepad is handled by the game itself. Keep in mind though that there always is a reason whenever the override is active per default, usually related to mouse based head tracking.
@ nieda: your guess is wrong. Also again: please stop suggesting things at random that make configuring vorpX more difficult unless you are 100% certain that actually helps in a given context. I know you are just trying to help, but without checking whether your suggestion makes sense this is not helpful in any way. Thanks (again) for your understanding.
If you use the Steam version, running vorpX as admin is required since Steam launches the game with admin rights. Besides that I can only recommend to check for other programs that also hook into games and might cause a conflict.
Typical candidates are virus scanners, GPU/CPU utilities of any kind, chat programs, video recording/streaming software and generally everything that can show notifications in games.
Enabling/disabling FluidSync on the display page of the vorpX menu is worth a shot. Maybe one option works better than the other.
DX12 won’t work with vorpX for the time being (and probably doesn’t really bring any substantial improvemnts for a game as old as WoW anyway).
In regard to the beta client: please use the regular client for vorpX. Unfortunately it’s not feasible to keep track of and adjust vorpX profiles for a beta version game client.