Forum Replies Created
-
Posts
-
@Ralf The only weird thing I currently have going in me even wanting to bother with Cyberpunk. With the steam+Cyberpunk crash that I had going on fixed everything is good again. Cyberpunk just has some weirdness when pushed to my HMD through vorpX that I don’t experience elsewhere; like a complete unwillingness to give me 45fps. I can maintain 4K, RT on, DLSS off at 37.5/75 nearly everywhere in the game, but it won’t give me 45fps at 4K DLSS set to Ultra Performance and RT off! No kidding. It’s not vorpX specifically, as everything works just as it should pushed to my 3D display, and it’s not even vorpX + PiTool + HMD as I can push other titles very hard without this issue. It’s just Cyberpunk.
Bring up something like FPS VR for a couple of minutes and set cyberpunk to your actual display, now switch it to your virtual display at the exact same resolution and settings. I see an immediate 5% or so GPU usage jump. Of course, since Cyberpunk has problems with increasing GPU usage just by entering and exiting the menus, this could just be Cyberpunk itself. I have yet to test that particular issue with any other title.
Just a quick note that in my test with the virtual monitor over the weekend (Cyberpunk only again in this case) I noticed that with the exact same in-game settings I got slightly worse performance on the virtual display. No idea why, but it was absolutely repeatable. I may order a cheap 4K DP headless display adaptor and try it, just to see if there is a difference or if it is simply overhead due to there being a second display enabled; it’s something I was planning to do anyway before you came up with the virtual display concept.
@Tophness I found that Steam itself was crashing during Cyberpunk (only, all other titles were fine.) Try the Steam beta version, which resolved that issue completely for me. Also try this SYNC method: Slow + Multithreaded. Works very well for me on my 8K-X.
(Note and digression; I’m getting considerably better performance using the vorpX beta than I do using the stand-alone mod. But I’m only shooting for cinema mode, not full VR. Not a problem with vorpX, but rather a problem with the Cyberpunk engine being incredibly soft-focus. A title like FO3 looks incredibly crisp and detailed at full VR even clear down to around 2880×1600 pixels, and looks glorious at 4K. Cyberpunk looks eye-wateringly crappy at anything below 4K with DLSS OFF once blown up to full VR size. It’s probably that shit TAA. You can force that off but then it’s got all kinds of other issues because the devs appear to have used TAA to hide other issues. That’s happening with other Devs also at this point (Hubris comes to mind immediately). Running at 4K no DLSS to my HMD is 30fps for me, even on a 4090. I’ll need at least 60fps, or maybe 45 with Brainwarp – if Pimax ever fixes that (nope, not gonna happen), so maybe I’ll get to try Cyberpunk in full VR if Ralf gets DLSS3 Frame Gen working, or when the 6000 series cards become available (2030?)
(ARGH: Edit time has expired already! Please feel free to combine with my prior post!)
I forgot to ask one question: I’m playing Cyberpunk in cinema mode and made the mistake of allowing vorpX to install the little helper for Cyberpunk when the vorpX beta requested doing so. Could you please tell me what files I need to remove to uninstall that? I would like to revert to normal driving and riding cameras. Also, is there any way to disable that warning from popping up every time once I remove the additional package? Thank you!
@DanThePman & @Ralf (boy I wish those tags actually worked normally in this forum!) I managed to get Hogwarts Legacy to work. I put the solution that worked for me in this thread: https://www.vorpx.com/forums/topic/howgart-legacy/
I’ve played with the DLSS3 Frame generation quite a bit (mostly flat, no vorpX, no Reshade), and the results are *fantastic*. Now that we know depth is at least nominally functional (see my findings with Hogwarts above) lets all hope that Ralf can make vorpX compatible with it. It’s much more clear than the intermediate frames generated by PiTool (don’t know about other methods) and it doesn’t cause ghosting like vorpX does on fast movement when vorpX is set to run below the HMD refresh rate.
DLSS3 Frame Gen compatibility would *absolutely revolutionize the vorpX experience* and I for one very much hope it’s something Ralf can get working.
I have finally resolved the AFR issue I was having with Cyberpunk (at least, now I can play for over an hour without needing to restart the game or simple load a save.) The Steam client (not the Steam VR client) was crashing in the background ONLY while playing Cyberpunk. This was greatly exacerbating the long-standing ‘slow degradation of performance’ which has plagued Cyberpunk, causing it to kick-in the moment the Steam client crashed, instead of taking an hour+. This then caused significant spikes in CPU usage, which was causing the AFR sync to drop out momentarily. As Steam was only crashing during Cyberpunk, I had not put 2-and-2 together. Reinstalling Steam did not fix the problem. Neither did a clean install of Cyberpunk. Turning on the Steam beta fixed the issue immediately.
So, here are my actual findings with the Beta 23.1.0 now that I have that not-vorpX related issue fixed:
1) Performance in Cyberpunk is better with the 23.1.0 beta than it is with the stand-alone mod. It is very easy to hit 60fps at insane quality settings on my 3D display. It remains tantalizingly out of reach to hit 45/90 at sufficient quality in this particular title on my HMD however, so I’m stuck at 37.5/75 when playing in on my HMD. Ultimately I think DLSS3 Frame Generation is the going to be the killer feature to get such demanding titles to play well. Using Z3D to my HMD, not AFR. Note that normal things like turning off RT do not resolve this issue; it seems very-specifically related to the rendering resolution. Even when I turn quality lower Cyberpunk will cause the HMD-refresh to drop below 90, causing the in-game rendering to also drop and stutter to begin. I have to reduce quality by truly *massive* amounts to maintain 45/90 in that particular title.
2) AFR works on my 3D Display in Cyberpunk, but Z3D solutions are broken in all titles.
3) Performance in other titles seems very good. For example I am able to play Hogwarts at 4K, RT High, DLSS Off with nearly all quality settings maxed (lower quality on Fog and post-proccessing at this time) at 45/90.
4) The following vorpX sync setting work FAR far (far, you get the idea) better than any other combination on my Pimax 8k-x. You might consider making this setting combo the default for Pimax HMDs: Sync method: Slow, HMD Multithreading: ON (this provides not only the highest in-game rendering rates compared with the other methods, it also creates the lowest-judder experience.)Just realized there are 2 Hogwarts threads, I’ll try to stick to this original one:
I figured out what’s going on with it not working for me (and hopefully some others). The “Shader building process” Hogwarts has to do every single time is causing an issue in the vorpX process, tricking vorpX into thinking it has not hooked.
1) Be sure Steam VR is NOT running before launching – Steam VR will then launch as usual once vorpX is running and you launch Hogwarts. This seems to work.
2) Wait out the part where everything looks locked-up.
3) Allow vorpX to install the Hook Helper when it asks.
4) Relaunch and play game, again waiting out the “crashed” period while Hogwarts builds shaders.
It should now be running in vorpX. vorpX will believe it has not hooked every time, just hit the “do nothing” option.
Performance is excellent. I’m getting 45/90 on 4090 at 4K DLSS Off with RT on High and everything else maxed. It drops quite a bit only during dialog, but that’s not causing any other issues so far.
I too have been unable to get Hogwarts to launch with the available cloud profiles unfortunately. The profile that says it was created with the beta will not even download. I expect these may be beta issues (Ralf did very clearly warn us that his beta is really a beta.)
OK, I think I have the 3D Display loss of depth / sync figured out in the beta. It appears to be an additional symptom of Cyberpunk’s long-standing issue of losing performance over time (until you fix it with a restart, or if you are lucky by just loading a save). In the HMD this has just been a minor annoyance. Start out easily maintaining 45fps and 10 minutes later you’ll get 40fps in exactly that same scene (unrelated to GPU temp/throttling.) But when that gets bad enough it causes additional issues on my 3D display. Anyway, that what seems to be currently going on.
@Tophness I had a similar issue over a year ago with my 8k-x. Absolutely nothing resolved it until I finally gave up and did a full clean install of Windows and started from scratch. That resolved everything.
If you have a spare drive hanging around I suggest you try creating a clean install on that and see if all your problems go away. Pretty sure it was related to PiTool updates, but with all the dependencies and variables on Windows systems I have no way to be sure.
I’ve played with the beta quite a bit now, with the following results:
Cyberpunk: AFR works on my 3D Display! That’s fantastic! I’m having a few issues where the depth will flatten out and then turn back on a frame or two later, but this does not appear to be performance related, or at least not entirely. I can sit there with settings that cause a scene to run at, say, 57fps, or 55fps instead of 60, and all is good. But other times the stereoscopy will flip off very briefly. I think it may be micro-stutters on texture loading. If this can be fixed then this is a fantastic solution for those with 3D Displays as AFR looks fantastic at only 60hz/fps on such a display, whereas AFR is almost unusable (to me, anyway) below 90hz/fps on an HMD. I have tried HAGS both ON and OFF to try and resolve the micro-flattening issue, but without success.
Universal: Neither Z3D solutions work on my 3D display with the beta, in any title. It’s just completely flat and Z3D does absolutely nothing. Bummer. Sure hope that can be fixed before the final release as I use vorpX with my 3D display almost as often as I use it with my HMD.
Cyberpunk: Running the HMD sync mode as follows for my Pimax 8k-x seems to provide the most consistent experience (and also provides the highest in-game fps): Sync method: Slow, HMD Multithreading: ON, vorpX frame-rate limiter: 50%, HMD refresh 90. (That is with the standard beta vorpX, not the Cyberpunk-specific mod.)
@luka2099 Ralf will probably write something concise when this is out of beta, but in essence this creates a “fake” monitor that you can assign a game to run on. There are similar hardware solutions that are widely used to provide ‘monitors’ to computers which don’t have any physical monitor at all; I actually considered using one of those solutions for exactly the reasons Ralf built this virtual one; to make it far easier to access higher resolutions than your actual monitor supports.
My example usage: My physical monitor is only 1080p. With NVIDIA super-sampling (DSR) this means the maximum I can *easily* set a game to run at is 4K. Anything above that becomes a PITA.
If a game supports being assigned to a secondary display (most modern games, in my experience), then you can turn on the vorpX virtual monitor, set “Goat Simulator” to run on “Display 2” rather than “Display 1” (you actual screen, assuming you have only 1 physical monitor), and choose any resolution Ralf has programmed the vorpX virtual display to support. Alternatively you could plug in something like this (see Amazon link) and achieve a similar result; the downside being you could easily lose your mouse on the secondary display, since it does not actually exist. The vorpX virtual display is a nice idea since you can turn it on and off in software rather than plugging in and unplugging a physical device: https://www.amazon.com/FUERAN-DP-DisplayPort-Emulator-4096×2160/dp/B082J671N2/ref=sr_1_1_sspa?crid=3JILL2N19V3IF&keywords=dp+headless+adapter+8k&qid=1676921150&sprefix=dp+headless+adapter+8k%2Caps%2C84&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUExV1ZRNlVLM1NTVUZJJmVuY3J5cHRlZElkPUEwMDA0NDE2MkhPSlRHNjVKQTBFWSZlbmNyeXB0ZWRBZElkPUEwNzg5MjIyMVREMk1ZTkpLQVNLUSZ3aWRnZXROYW1lPXNwX2F0ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=OK, not all of these are tested through vorpX at this point but I’ve found the following thus far:
1) In Witcher 3NG there is no depth in the generated frames at all – OR the depth is there but something else need to be tweaked before it will work. Every generate frame goes flat. (ReShade method.)
2) In Hogwarts there IS depth in the generated frames, however something will need tweaking before it is really usable as it causes significant issues with the halo artifacts. (ReShade method.)
3) Cyberpunk – Untested at this point as the moment I turn on frame generation the title crashes – most likely due to the vorpX Cyberpunk mod. I plan to try testing that soon another way.But the good news is that Hogwarts shows that if the issues with the halo artifacts can be resolved then it will likely be possible for this to work. Still have the HAGS issues to deal with as well of course.
The virtual display is a display driver like any other, adding it is the same as adding another physical monitor to your PC. I have zero idea how scaling of your primary display can be affected by adding a secondary monitor, that’s just not supposed to happen. Also it’s not something vorpX does directly, stuff like that is entirely handled by Windows.
As of the latest NVIDIA driver 528.49 this problem has resolved. I’m now running the beta as my primary vorpX install without many issues.