Pimax Crystal DFR IL2

[DBCOOPER011]

PSA,

 

I believe eye tracking (DFR) is operational with certain settings in IL2 with the Pimax Crystal. I previously had sporadic CTD's with Il2 when DFR was enabled using steamVR. I've recently noticed that if HDR was checked within the IL2 settings, then CTD's would occur but sporadically. I've unchecked HDR in the IL2 settings menu and have been CTD free for the last couple days in both online/offline gaming sessions. DFR gives me about a 2ms drop in GPU time and a slight bump up in CBP time, the results are very good. I have no idea why the CTD's have stopped with this settings, but maybe someone else can confirm.Thanks...

[TAIPAN_]

Sharpen combined with FXAA would also crash it for me, as would very heavy missions sporadically. I haven't tried it since the latest patch though. 

 

Good to know about HDR, I never used it so had not tested that. 

[DBCOOPER011]

11 hours ago, TAIPAN_ said:

Sharpen combined with FXAA would also crash it for me, as would very heavy missions sporadically. I haven't tried it since the latest patch though. 

 

Good to know about HDR, I never used it so had not tested that. 

 

I dont know why its starting to work now. Game or steam update maybe, who knows. Its a win for those wanting to use it, although the gains are definitely not as great as QVFR in DCS. The gains are pretty much the same using FFR as well. I was thinking about the heavy mission scenario as a possible cause for the prior crashes, but it hasnt happend yet, and i'm running at native resolution (4312x5102) w/the above settings. Just had a mission in CB on day 3, and the GPU frametime were between 9-11ms, 4-7ms on the CPU, and the average GPU load was around 75%.

 

 

[TAIPAN_]

18 minutes ago, DBCOOPER011 said:

 

I dont know why its starting to work now. Game or steam update maybe, who knows. Its a win for those wanting to use it, although the gains are definitely not as great as QVFR in DCS. The gains are pretty much the same using FFR as well. I was thinking about the heavy mission scenario as a possible cause for the prior crashes, but it hasnt happend yet, and i'm running at native resolution (4312x5102) w/the above settings. Just had a mission in CB on day 3, and the GPU frametime were between 9-11ms, 4-7ms on the CPU, and the average GPU load was around 75%.

 

 

 

Possibly even a Pimax play update or firmware update, I'll have to retest my scenarios though it seems one of the updates deleted the mission that I created 😠

 

Curious how did you test plain FFR? The FFR switch in PimaxPlay actually enables DFR and there's no option to change between FFR and DFR.

[DBCOOPER011]

16 minutes ago, TAIPAN_ said:

 

Possibly even a Pimax play update or firmware update, I'll have to retest my scenarios though it seems one of the updates deleted the mission that I created 😠

 

Curious how did you test plain FFR? The FFR switch in PimaxPlay actually enables DFR and there's no option to change between FFR and DFR.

 

Hmm, It says that it changed to FFR when I turn off eye tracking. Is that correct or a bug of some sort..

[TAIPAN_]

8 minutes ago, DBCOOPER011 said:

 

Hmm, It says that it changed to FFR when I turn off eye tracking. Is that correct or a bug of some sort..

 

Ahh no you're totally right, it just never occurred to me to ever turn off eye tracking since I never had reason to.

 

How do you find the 72hz mode? For me I can't handle the flickering, apparently it's not noticeable to some people unless you're sensitive to that. Unfortunately for me I notice it the second I put the headset on.

[DBCOOPER011]

6 minutes ago, TAIPAN_ said:

 

Ahh no you're totally right, it just never occurred to me to ever turn off eye tracking since I never had reason to.

 

How do you find the 72hz mode? For me I can't handle the flickering, apparently it's not noticeable to some people unless you're sensitive to that. Unfortunately for me I notice it the second I put the headset on.

 

I haven't noticed any flickering whatsoever using 72hz mode in both my crystal and pico4. I've had a few other headsets and ran a couple of those at 72hz without flicker as well. Is this just with the crystal or other headsets as well?

[TAIPAN_]

Did some testing, things I noticed:

-Found the mission to reproduce the previous crashes, now does NOT crash with DFR on

-Found that enabling Sharpening with FXAA DOES cause a crash, when testing a frametime over 9 (at 90hz), in QMB Bodenplatte with 8 german fighters vs 8 allied bombers at 500 feet face to face once I begin firing guns at them. 

-Frametime is slightly better, heavy missions can still slow it down but the average career mission stays under 9 frametime better (using moderate AI settings)

 

Another thing I also changed was my Nvidia driver, been 6 months since I updated but I did so last week. Since that DFR uses Nvidia VRS it might be highly dependent on that, however it still can't handle HDR or Sharpening but we can just avoid those.

 

It's not totally conclusive, because the crashes previously could come in some heavy scenarios. But I'm going to run with this and try it for a while.

 

For 72hz I also retested that, and found no flickering in IL2.

However I realized that previously I never tried it in IL2, because DCS is my main sim as soon as it looked bad I immediately went back to 90hz. Testing in DCS again now shows that it's still flickery. Could be due to the lighting issues DCS has with Quadviews that were never completely fixed, but also noticeable with bright cloudy skies. The A10C instant action "free flight" in the winter snow is the perfect mission to showcase this.

 

So it could be that 72hz flickering is only on OpenXR titles, only on QuadViews, or maybe even only for DCS itself.

If you have DCS, especially A10C I'd be curious if you notice that on the snowy free flight mission.

 

ps to answer your other question, I don't have any other headsets to test 72hz. Crystal is my only, as I had a long break from VR between the HP reverb and this.

Edited May 4, 2024 by TAIPAN_