Forum Replies Created
-
Posts
-
I’m not sure whether I understand the question correctly, but the easiest (and usually also the best) way to use vorpX with a Quest is selecting ‘Oculus’ as your headset type in the vorpX config app and using Oculus Link/Air Link for sending the image to the headset. Any additional tool added between vorpX and the headset just makes things more complicated.
@ PD: You have to make a copy first, no way around that. Each profile has a unique id, hence you can’t just re-upload someone else’s profile with tweaks as that would overwrite their profile in the cloud.
The only setting I’m aware of that causes a garbled depth buffer is the game’s ‘Color Precision’ option, Which has to be set to ‘High’. vorpX handles that automatically though.
It also sets a bunch of other settings. If you happen to have disabled auto settings, please first and foremost re-enable that. Automatic settings can often be vital for a profile to work correrctly. With default settings (in FullVR mode) vorpX also disables stuff like motion blur etc. for example. Not unlikely that one of these settings also affects the depth buffer heuristics.
Also please reset the profile to default, just in case.
If that doesn’t help, it would be great if you could send me a trouble shoot data archive (config app/trouble shooting) and your CP2077 config file ([User]\AppData\Local\CD Projekt Red\\Cyberpunk 2077\UserSettings.json) to support at vorpX com.
21/10/04
vorpX 21.3.0.1 has been releasedThis is a hotfix that addresses the issue below, no other changes.
- Switching between Z3D and G3D could cause a garbled image under some circumstances.
Awesome, thanks! Will do so for the next regular update (not today’s hotfix though, saw your post too late for that).
It’s FSR, but just in case you fell for AMD’s marketing and thus expect some miracle, please keep your expectations in check. FSR is actually CAS + Lanczos like upscaling + a dirty lttle mipmap hack. Together that makes a pretty good upscaling technique, but not more. There is nothing miraculous about it at all.
Glad you like it. Setting the option to full enables a hack that AMD recommends game developers to implement in addition to the upscale/sharpen shaders. Didn’t cause a problem for me in Bioshock Infinite, but whether the hack is an actual improvement or not in general depends a bit on the game and the resolution it runs with.
The hack basically tells the GPU to load a more detailed version of a texture from memory than it normally would for the current pixel. When game devs implement FidelityFX they are supposed to do that in addition to the upscale/sharpening. vorpX can enforce the hack for every texture read (if available for a game). In some cases it doesn’t make much of difference at all or even introduces some shimmering instead of improving anything, but in other cases it does actual improve things. Easily spottable examples that probably everyone has available to try are trees/shrubs/gras in Fallout 4 or Skyrim.
Yes, at least it should. When you do shader authoring for an official profile the changes are part of the profile’s user section. I haven’t actually tried that since implementing shader authoring for official profiles, but shader definitions are supposed to be exported/imported like all other user settings for official profiles. Let me know if that doesn’t work.
That’s just a coincidence. Although it’s understandable to suspect an update to be the cause of an issue that pops up shortly after that’s not necessarily the case.
There have been no changes that could possibly affect Bioshock Infinite in particular. Also it’s incidentally one of the games that I check regularly before releasing an update.
Not sure whether that can be fixed. Sounds like they made some changes to the their anticheat system. IIRC there is a ‘-insecure’ command line switch or something similar that disables anticheat. That might help. You won’t be able to join anticheat enabled servers that way though.
BTW: I have merged both threads concerning this issue. Ideally please avoid creating duplicate threads for the same issue. Just makes it harder to follow and reply.
@ Khaleev : If it’s the same issue as ususal (a certain shader having changed after a game update) you might be able to work around it by first switching to Z3D and then back to G3D later after the game loaded.
Either way I’ll take a look at the game next week. Almost certainly something that can be fixed with a profile update. Unfortunately ESO updates tend to break things for vorpX once or twice a year.
Please check whether the same happens happens when you switch to SteamVR. Also if you happen to have the WMR developer tools installed, please always make sure to NOT use the developer version of the OpenXR runtime. Always use the stable release build.
As far as Bioshock Infinite is concerned, please make sure to set the FOV slider to max in the game options as suggested by the message shown in the top/left corner of the game window. Otherwise vorpX can’t set the FOV right. The DirectVR scan may fail occasionally unfortunately. Scanning through a game’s memory to find single a addresses for head tracking is a fairly complex process. There is no 100% guarantee that it always succeeds. Hence the message in that respect that is shown during each scan.
Sorry guys. There seems to be some bug since ages that I just can’t wrap my head around. The bug occasionally makes the profile database update fail for unknown reasons, resulting in a reset of all custom profiles and settings. There are already a bunch of safety measures in place during the database update, but apparently there is still some issue that I can’t replicate here.
If you have profiles/settings that you spent a lot of time on, please upload them to the cloud, so you can redownload them later in case something goes wrong. Would be great anyway since that way others could also try them. If you don’t want to upload them to the cloud, you can alternatively make local backups in the config app, either with the ‘Export to file’ button or via drag/drop to the desktop.
@ Ovo: If you have improvements like that for an official profile, it would be great if you could send me a mail with a backup of your settings (see above) to support at vorpx com, that way I could easily intergrate them into the official version.
No, sorry. I have considered that, but overall the all AMD solution is the better one. Trust me, I didn’t make that descision lightheartedly.
I understand that occasionally it can be a bit of a nuisance to get used to some detail that is slightly different than before, but in this case having to maintain two things in parallel would have so little benefit that I decided to keep it simple instead. It’s just a new sharpening algorithm after all, others force a whole new OS user experience upon you every five years. ;)