Forum Replies Created
-
Posts
-
Thanks for the heads-up. An oversight on my end. The game dislikes gamepad and mouse input at the same time. Before running the DirectVR scan vorpX emulates a mouse for head tracking.
Please either
Run the DirectVR scan. After a successful scan vorpX doesn’t have to emulate a mouse anymore. Problem gone.
or
Set ‘X-Box Gamepad Override’ to ‘Full’ on the input page of the vorpX menu to enable vorpX’s internal gamepad mapper.
I’ll make sure that this is handled automatically for the next update, i.e. gamepad override automatically on without DirectVR head tracking and off with DirectVR head tracking.
vorpX uses a new frame syncing method for Oculus headsets since the last release that is a bit of a double edged sword. While it is about 10% faster than the original one (that is still used for SteamVR), it’s choppier with very low framerates. Sounds very much as if that is what you are experiencing.
You can go back to the original method on Oculus with an .ini tweak that makes your headset behave the same in native Oculus mode as with SteamVR.
1. Navigate to C:\ProgramData\Animation Labs\vorpX\Devices\Display
2. Open Oculus.ini with a text editor
3. Change iDmBufferGrabberSyncDX11 from 1 to 0 (near the bottom of the file)Do NOT change the DX12 value! DX12 will not work correctly with the original method.
I might go back to the original method for DX11 per default in the next release, still in the process of deciding. Maybe the FPS gain wasn’t worth the side effects with very low FPS.
If you can’t see the C:\ProgramData folder, enable ‘Show Hidden files’ in Windows Explorer.
That explains it, F1 2019 still has a DX11 render path. DX12 support in vorpX is currently only available for Read Dead Redemption 2. You could try that profile, but I highly doubt that you will get any 3D at all with it in GRID.
Just a heads-up that there should no need to any of this. Since two versions ago there is an official profile that should work without any workarounds.
The link is sent automatically, usually within a few minutes. Please make sure to enter the same mail address into the download form that you used to activate vorpX. The system ignores unknown e-mail addresses.
Also check your spam folder, just in case.
In a few days.
You can quite easily work around the glitch until then by changing the resolution twice after launching the game. The first time to a resolution with a different aspect ratio and then back to your desired res.
Should even suffice to select e.g. 1024×768 and then, after the game applied the change, cancel when you are asked whether you want to keep the new resolution.
You can get a new key when you change hardware or get a new PC, so licenses aren’t bound to your current PC.
We haven’t done that yet, but at some point there may be a paid update for a new vorpX version, just like for most software that is updated regularly. If you choose not to update at that point, your then current version will of course continue to work.
MPC-HC is better quality wise, that comes at price though. In MPC-HC vorpX grabs the image before the player processes it. That has numerous advantages, but also means subtitles aren’t shown in vorpX.
In VLC the image gets grabbed when it is sent to the monitor, after the player processed it, so you get full subtitle support.
So in general MPC-HC is the better choice for vorpX, but if you want subtitles, VLC is the way to go.
Try to run Max Payne 3 windowed (‘Fullscreen’ set to ‘Off’ in its graphis options). That should fix it.
There currently is a bug that affects a handful of DX11 games when run in fullscreen mode. The bug is already fixed in my current dev build, that’s why I didn’t encounter the issue when I checked the game first.
Running the game windowed helps until the next vorpX later this week.
I’d like to take a look at your logfiles and system config. Please try to run the game a few times, create a trouble shoot data archive in the config app and send that to support |at| vorpx com.
Checked both Max Payne 3 and Arkham City, could not reproduce your issue though.
Arkham City ideally should be run with DX9 (DX11 off in the game launcher). I’ll automate that for the next vorpX. Also make sure to disable 3D-Vision if you happen to have that enabled, in the game launcher and in your nVidia control panel.
Also ideally use the Arkham City GOTY edition on Steam. That’s the one that the profile was made with. Shadow/HUD etc. definitions might fail with other editions if the game’s shaders were recompiled for different editions. That might explain the glitches you got.
For Max Payne 3 it’s the other way around. Best to run the game with DX11. vorpX should already do that automatically, but if that fails or you have disabled auto settings, make sure DX11 is set in the game’s graphics options.
Unrelated: For Arkham City you might want to download the ‘Batman: Arkham City [vorpX]’ profile from the cloud. While I was at it I made a few minor changes.
Great. I also implemented a fix for the underlying issue in the meantime. One of those little code changes that are an improvement in general, but have a negative side effect in one or the other unusual case. With the next update Arma 3 will run fullscreen again.
I’ll take a look at Batman Arkham City, haven’t checked the game for some time. It used to work very well, also no other reports of such an issue so far. Still posssible of course that something has changed, I’ll check that.
On your I would suggest to try a factory reset (config app > trouble shooting) first to ensure all profiles have their default settings. Maybe you changed some settings that can cause glitches.
In regard to hooking/start issues please try the usual things suggested in the trouble shooting guide pinned on top of this sub-forum, i.e. primarily checking for potential hooking conflicts.
Running vorpX as admin is only necessary for games that require admin rights. Better to not do that unless required.
There is no difference between official profiles and user profiles in regard to the hooking process. Almost certainly a coincidence that this happens just now for you.
Try to disable the Origin overlay in the Origin options. Shouldn’t be necessary, but may help. Also enabling alternative hooking in the config app may be worth a shot. caveat: switch back to default hooking later even if that helps, some games require default hooking.