I just installed VorpX to play games like HALO on my game computer, after some fidling around I got vorpx working for me, so far so good. But I noticed that after I installed Vorpx and included Microsoft flight simulator in the exclusion list. I can still fly msfs2020 but after a while (and landed somewhere) I suffer from a CTD. I have tried several flights, every time the same effect. after I remove VorpX the CTD’s a gone. does anybody have the same problem or know how to solve this? Thanks. PS I use HP equipment for my computer and VR.
Turning off TAA (ini tweak) does indeed eliminate (or at least greatly reduce, there is then so much aliasing it’s hard to be absolutely sure) the halos that direct VR brings to the table. It’s also *vastly* sharper at any given resolution of course, although the decrease in resolution necessary to run without DLSS means that distant detail suffers greatly as there just aren’t enough pixels to work with. Combined with
Unfortunately turning TAA off means DLSS won’t work, as it is for some reason tied the the single worst form of AA ever invented. I think TAA simply stands of Terrible Anti Aliasing.
I was also unable to turn the in-game AMD upscaling on, although I have not really tried to troubleshoot that issue yet. It may be that it won’t work with RT on, I seem to remember reading something about that.
No doubt cyberpunk is a tough nut to crack. At this point I could almost certainly achieve sufficient performance to run Direct VR 3D in cinema mode with TAA and DLSS off, but with no way to inject a different AA method it’s unplayably aliased and shimmery.
Solution (again) that comes to mind first is working to make sure vorpX plays well with ReShade. It’s just the simplest solution out there for fixing recalcitrant games.
Cyberpunk with regular G3D in VR is not something you should even think about in 2021. This uses alternate frame rendering and the halos are TAA artifacts inherent to the method. No promises, but there might be a way around that in a future update.
And now I will stop answering anything except emergencies for the (short) rest of the day. :)
Very cool Ralf. You’ve given us all a nice Christmas present! Also, why aren’t you taking the day off? (also, why am I typing this today? :)
As often happens my initial question may have mostly been due to misunderstanding what this should be doing for me.
I guess I’m down to two questions for the time being, especially as if I can’t get v1.31 to look as good as v1.23 it looks like I’ll be sticking to the main vorpX method anyway.
1) Am I supposed to be seeing a G3D option? Direct VR is clearly not the same as G3D as it still products halos. If I’m supposed to see G3D then I have something wrong on my end.
2) Is there a config file where I can reduce the total amount of depth? Am I somehow missing it in the vorpX menus? As lovely as this is, I will often go with less depth to reduce halos and other artifacts.
Please do NOT answer those question until after the holidays!
Can you enable us a longer editing window on wordpress? I would go in and edit that post after I had some unexpected time to play with it more:
1) It does not work at all with v1.23, which is a bummer.
2) I totally misunderstood what Direct VR would bring; I thought it was a form of G3D, but it’s got so much distortion. It is wonderful to have that much accurate overall scene depth, but I would either need to turn it way down (which I can’t seem to do currently) or just switch back to Z3D – I actually get far *less* edge distortion with Z3D. Yes, the depth is no longer a bit wonky with Direct VR, but it halos so badly with this much depth. Is there any way we can turn that depth down?
3) Performance appears to be exactly the same as Z3D; switching to Direct VR gives me more depth, more distortion, and no change in performance.
I expect it would be a lot of fun to play with Index controllers, but unfortunately I won’t be able to push the frame-rate for that at anything resembling a high-enough resolution for me to tolerate, so it’s Cinema mode for me anyway.
Try the Delete key on your keyboard. That is the keyboard key to open the vorpX menu.
It’s possible that the profile author that uploaded that Halo profile disabled the menu button for gamepads. It is a setting inside the vorpX menu that allows you to turn off edgepeek and vorpX menu access in the case that you need all of those buttons for gameplay instead.
I haven’t, and I tried other games and the menu appears fine, but it doesn’t work on halo infinite for some reason. Are you saying the menu is not supposed to disappear? I thought it was a dx12 thing. I wonder what the problem is.
Someone posted about attaching HaloInfinite.exe to a Cyberpunk Profile with a Hook Helper installed and I was able to get Halo running in VR with Z3D. I’m curious as to when this might be a supported title if doable? :)
Only thing I’ve found annoying is that there are edge issues on the halo post if you hide it, which makes looking in front very difficult.
On another note, what resolution/quality settings are you running in game. My rig (3080) can handle 4k no problem on many games with vorpx, but with this game it goes crazy if I set that resolution.
Thanks Ralf, “Fullscreen (Windowed)” fixed the crashes I was having in Oculus mode (SteamVR mode still crashes, but that doesn’t matter since Oculus mode works).
Works great with these settings if anyone else is trying it out:
In game – Fullscreen (Windowed)
VorpX:
* Immersive Screen mode (FullVR you can’t see some crucial HUD elements while driving, such as the radio menu. Most info is shown on the wheel in cockpit mode, but there is still some you need the HUD for)
* Turn down 3D strength from default 2.0 to 1.0 (Reduces the distortion around the halo column, or where the column would be if you have it turned off. Can turn it down even further if this is still an issue for you)
* TrackIR on in both VorpX and in-game, allowing you to look into corners and check your wing-mirrors
Still tweking it a bit (looking to the far edges, for mirrors for example, is a bit disoritenting and seems to lag a bit for some reason), but overall a good experience now!