The setting was successful on my second 2 hour flight up to Moscow.
Who knows who will come up with a solution? This problem has been going on for ages and you wonder if things are getting too complex. Sincerely, thanks for your work and the information you share on this and many, many other topics. But that does not mean LM et al don't need to do more work on this.
It obviously is a good workaround for now. And, I say this because my understanding is, like yours, that the TDRLevel=0 setting is really only intended for use in testing and troubleshooting. My point is simply that a true fix is going have to come from LM/Microsoft/Nvidia. And, I certainly am appreciative of your willingness to so freely share your findings. I don't intend to be critical of what you have found through a considerable effort. So as far as I’m concerned this is a fix and in all probability, a permanent one. In over 12 flights now I’ve not had the problem in any bar one instance when I paused the sim. Except you won’t hear from LM as we’re not entitled to support. And between Microsoft, Nvidia and LM if you raise the issue with one they’ll just point the finger at the other two. It seems to affect users of complex 3rd party aircraft so LM will never be able to fix it with their simplistic aircraft. It’s been suggested I uninstall and reinstall P3Dv5 again but given I get no other problems what guarantee is there all that work will resolve the problem? None. These Tdr features are there for good reason. Jesse, I suspect the problem will remain unresolved and Registry entries will be the solution for many. Perhaps all we can really say is that the TdrLevel=0 is potentially allowing recovery from the DXGI problem and it appears the underlying problem still exists? So, not so much a "fix" as a workaround?
0 kommentar(er)
