Forum Replies Created
-
Posts
-
For your convenience in case the ingame hint that gets displayed each time you launch the game isn‘t clear enough. Please read carefully.
Quote from the release post for the last beta:
Concerning The Last of Us there is a little caveat: the game’s renderer apparently works heavily asynchronously and on top of that switches between different depth buffers often, which makes it quite hard for vorpX to figure out which is the right one to use for which frame. I implemented a bunch of workarounds to deal with that and things look stable with a few savegames I checked, but if you encounter heavy depth flicker or weird distortions on your machine, you may have to resort to playing in 2D.
Please try to reset the game’s graphics settings to default. When I checked the FC6 profile and added the scalable HUD shader definitions I played for a while beginnining in the city (starting on a rooftop) without encountering this issue.
That aside please keep this in mind.
I uploaded a new build that *may* improve the depth buffer flicker situation in TLOU. Haven’t test it much (Sunday), but you may want to give it a shot.
Sounds as if vorpX can’t load the profile for the game.
Might also be this extremely weird issue that popped up a few times recently:
Third time within a few weeks that this error pops up. Super weird. The first user with this issue could track it down to their C:\ProgramData folder being inaccessible for some apps/games for whatever reason, so that games tried to load the vorpX config data from a hidden virtual store folder that Windows creates in some cases instead of loading the actual file with the stored config from C:\ProgramData.
You can check that by browsing to ‘C:\Users\[Your User]\AppData\Local\VirtualStore’. If this folder contains a subfolder named ‘ProgramData\Animation Labs’ something is severly wrong. Move the ‘Animation Labs’ sub folder to C:\ProgramData in that case. It should only exist in C:\ProgramData, not in the virtual store.
IMPORTANT: ‘Show hidden files’ MUST be enabled in the Explorer options to see any of the folders mentioned above.
No error in the logfiles and also nothing in the system info that looks as if it could potentially get in the way. So not much I can say unfortunately.
Try to uninstall vorpX. Then manually delete the C:\ProgramData\Animation Labs\vorpX folder and reinstall vorpX afterwards.
CAVEAT: If you have profiles that you put some effort into, back them up first in the config app by dragging them from the local profiles list to the desktop.
Probably this:
Third time within a few weeks that this error pops up. Super weird. The first user with this issue could track it down to their C:\ProgramData folder being inaccessible for some apps/games for whatever reason, so that games tried to load the vorpX config data from a hidden virtual store folder that Windows creates in some cases instead of loading the actual file with the stored config from C:\ProgramData.
You can check that by browsing to ‘C:\Users\[Your User]\AppData\Local\VirtualStore’. If this folder contains a subfolder named ‘ProgramData\Animation Labs’ something is severly wrong. Move the ‘Animation Labs’ sub folder to C:\ProgramData in that case. It should only exist in C:\ProgramData, not in the virtual store.
IMPORTANT: ‘Show hidden files’ MUST be enabled in the Explorer options to see any of the folders mentioned above.
Please update to the latest beta. The last regular vorpX release doesn’t work right for DX9 in Windows 11 22H2: beta download
Alternativly wait until tomorrow. I’ll upload a hotfix for the last regular build that will address this issue.
You did read what I wrote about TLOU depth buffer detection in the release post and/or the message that vorpX displays when you launch the game, did you?
Let the game build its shaders before you launch it with vorpX. Compiling the shaders maxes out every core of your CPU entirely. Unless you have a highend CPU with many cores that will probably interfere with vorpX heavily.
General hint 1: always keep in mind that both vorpX and the VR runtime use additional GPU memory. So with a mid-range GPU you may have to dial back graphics details in newer games compared to playing flat. Especially dialing down the texture resolution may help when GPU memory gets low.
General hint 2: rendering games to the headset not only uses additional GPU memory, it also taxes your GPU in general. As a rule of thumb consider the additional workload similar to what Oculus/SteamVR/OpenXR require when they render their empty environments. Hence even with Z3D (which in itself doesn’t cost much) there is a considerable impact on FPS when you display games in the headset.
It’s DX12 only. The ‘-dx11’ start parameter tip floating around the internet is bogus. The game still uses DX12 when you add that. I encountered this with several games in the past already. Apparently some people try that for every game and then think games run with DX11 just because they added a launch parameter without actually checking whether it does anything. Or maybe just some AI bots are inventing nonsense-hints for clickbait sites. Who knows.
You need the vorpX beta for The Last of Us. Even if there was a way to make the game run with DX11 (which is not the case), the vorpX profile would be DX12 only anyway.
Not possible, sorry. The Last of Us requires the DX12 changes mentioned in the release post above.
Don’t want to nitpick, but you gave that advice about two weeks ago in the techincal support forum: click. Again, just in case: never, ever mess with the service! Among other important things the service ensures that the display driver only gets enabled when it is supposed to. Disabling the service breaks that and a lot more.
Anyway: the display driver should uninstall when you uninstall the vorpX beta. However: it does not uninstall when you just install the last regular build over the beta without uninstalling first! So please try to install and then uninstall the beta directly afterwards. That should do the trick.