Forum Replies Created
-
Posts
-
Unfortunately this cannot be resolved on the forum.
Please send an e-mail to support at vorpX com with something that helps to verify your order. Either the MyCommerce order id, the name or the mail address you entered into the purchase form would suffice.
Upping this thread since nVidia still hasn’t fixed the issue. Judging from their changelogs they seem to be aware of it as since it also affects their own ‘FreeStyle’ post effects. No sign of a fix yet though…
If you play any game where vorpX changes settings and are greeted with a vorpX message that suggests a restart on each launch due to settings changes, please use the last known working nVidia driver linked below. That will probably fix the issue:
https://www.nvidia.com/download/driverResults.aspx/199654/en-us/
If nVidia doesn’t fix the problem soon, I’ll implement a workaround for vorpX.
The mono/stereo settings are on top of the image page in the vorpX menu i profiles that expect stereo input.
To create an individual SBS profile for a game/app you can try the Basic SBS profile from the cloud. Won’t work with Yuzu though. In that case the destop viewer is the only option.
If it’s a normal screensaver, the executable has the extension .scr. You’d have to search for a .scr file in the install folder of your screensaver. Adding it to the exceptions might be a bit tricky though since the ‘Add exception’ dialog only displays .exe file. You’d have to browse to the folder that contains the .scr file and they type in the file name manually.
Probably a good idea to always exclude .scr files unless there is a dedicated profile for them. I’ll add that for the next beta release.
That’s something I can’t really wrap my head around unfortunately, The desktop viewer actually loads vorpX itself, so failing to attach *should* be next to impossible… Can’t really imagine much more than something getting in the way that also hooks into other programs.
The only suggestion I have is to rigorously disable/uninstall any background apps/tools/utilities. If you happen to have multiple GPUs/monitors, please also check whether the issue occurs with just one GPU and/or monitor.
If you want, send me a trouble shoot data archive. With some luck logfiles help to spot something, I wouldn’t count on it on this case though. You can create a trouble shoot data archive in the config app. Please send it via mail to support at vorpx com.
Try to reduce graphics details a notch, especially things that take a lot of GPU memory. Texture resolution will probably have the biggest impact. Display resolutions in/above the 4K range also start to become a serious factor in that respect.
vorpX as well as the VR runtimes use extra GPU memory. When your GPU memory is fully used, games start to use system memory as virtual GPU memory, which is *much* slower.
Depending on how much memory a GPU has, newer games may almost max out your GPU memory when playing normally already, playing in VR might just be a tad bit too much. Even the 10/12 GB of a 3080 may become tight if you crank everything up in some newer games. By reducing memory heavy graphics settings like texture resolution you can make sure that doesn’t happen. Applies to any game that may potentially max out your GPU memory.
vorpX reads (and later sends) Windows virtual key codes for keys you assign in the gamepad mapper. For the arrow keys that would indeed be 37-40 decimal.
Just a theory: maybe KOTOR directly evaluates hardware scan codes and somehow mangles the virtual key codes into something else. Really just a guess though. Maybe there is an external gamepad mapping app that can handle a (fairly weird) edge case like this, but for vorpX that would be a bit too much.
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.