Unfortunately, there seems to be no mention of PIMAX in the next update either.
Some people say that if the operator had the right technology, it wouldn’t take long to deal with this kind of problem, but it seems that the operator still can’t do it.
Of course the issue is still present, I have done a Zendesk report on it and upvoted the issue as well.
Now that you made this matter; in this thread, the Pimax Anamoly (11) I was the first and only one to mention that TAA was the issue and that if you switch to Nvidia DLSS and choose quality, performance or ultra performance, the flickering goes away.
Further findings after my first comment:
Runtime needs to be PimaxXR.
You also have to be very specific in Pitool Client, device settings: smart smoothing on and compulsive smooth set to 1/2. Do not use other functions. Parallell projection off, fixed foveated rendering off, hidden area mask off. MSFS VR reprojection off.
The settings I’ve activated in Pitool client, MSFS specific settings, I’m at 75hz, native, FOV large, render quality 1, Smart smoothing on, compulsive smoothing 1/2. If you go to compulsive smooth1/3, flickers start again. What is not on this list of Pitool functions is turned off. (backlight and contrast is of course active)
MSFS VR graphics are maxed out with these settings with no flickers.as I have a 4090 OC. The FPS is locked to 37,5FPS in all scenarios.
Hope this helps.
Thank you for the extremely detailed information.
I don’t have the environment to test it, but some people may find this information useful.
My feeling is that canceling TAA is not the solution, but that the high level of drawing support capabilities of DLSS is the solution to the problem.
I think the important point here is whether DLSS is decisive, or whether the FPS that DLSS brings is decisive.
This is a bit meaningful information now that the new model of RADEON is about to be released, but above all, it contains the fundamental problem of whether it is a problem that can be solved by choosing anti-aliasing.
It is interesting to see the subtlety of the Forced Smooth settings on the PITOOL settings.
The need to turn off FFR is also a little interesting, but in terms of FPS, it should be more damage, so I think it’s not very predictable.
I’m letting go of my 3080ti right now and only have a reserve 1080ti (As a temporary refuge for replacement, the 1080TI with 11GB of VRAM was better than expected. Until this SU10 happened, there was no problem at all. However, considering the current information, the 3080ti But it seems that this problem has occurred.) so I don’t have DLSS so I can’t test it, but I think it’s useful information for some refugees. For me, it’s a vexing question, what should I do with my next GPU?
Regarding this, it seems that there is no choice but to lower the altitude and see the situation.
Some say that FSR3 is an illusion, and others say that ray tracing will make a big difference as before.
There is also information that DLSS introduces disturbances to aircraft instrument displays on MSFS.
To top it all off, for us, this wide-angle VR issue adds to the complexity.
I bought some planes on sale.
I’m not going to try it outside of wide-angle VR.
Because it’s something special.
I hope this won’t be your last investment in MSFS.
Unfortunately, this method is also not universal according to information provided by other 4090 users.
Currently, there are no measures that users can take with peace of mind.
It’s been a long time since Su10.
I feel that it is insane that the management side has not announced anything for the time being.
How is your latest situation?
I’m using PIMAX OPENXR, and with the same image quality settings as before, I’m facing a few seconds of normal display, and more frequent flickering than last month, and a repetition of these two conditions.
With all anti-aliasing turned off, the frequency of flickering has decreased, but it always occurs once every ten or so seconds.
In the first place, without anti-aliasing, the health of the eyes will be in a severe state.