Jump to content

JesC

Donor
  • Content Count

    429
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by JesC

  1. Great to hear. Would be nice to see your computer specs and what sim version you are using. Jesse
  2. I don't have windows 11 yet but found this: https://allthings.how/how-to-get-classic-context-menu-of-file-explorer-back-in-windows-11/ Maybe that will help? Good Luck. I know these changes can sometimes be very frustrating. Jesse
  3. Talking about the Google Ads banner? I see it. Very annoying. Jesse
  4. Jesse, I suspect the problem will remain unresolved... Please don't misunderstand my post. I don't intend to be critical of what you have found through a considerable effort. And, I certainly am appreciative of your willingness to so freely share your findings. My point is simply that a true fix is going have to come from LM/Microsoft/Nvidia. 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. It obviously is a good workaround for now. But that does not mean LM et al don't need to do more work on this. Sincerely, thanks for your work and the information you share on this and many, many other topics. You have always been very helpful. Jesse
  5. Ray, 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? Jesse
  6. Ray, Did you remember to clear the DX12 Cache after the previous crash? Jesse
  7. Any chance of resurrecting this project for P3D; perhaps by substituting the avionics with RXP integration and/or standard Nav/Com options and an acceptable autopilot that is P3D compatible? I really was looking forward this in P3D and find the GNS 530/430 perfectly acceptable. Curious to get your thoughts. Jesse
  8. Yeah. At one point (maybe in 5.1?) I could consistently produce the error even with default aircraft, but no longer. It's so inconsistent that it becomes difficult to be certain about any fix. Testing can take hours and it is seldom repeatable. Frankly after, more than a year of v5.x I have returned to v4.5 and spent a considerable time getting it just right for consistently great experiences. I think v5 is promising but has a long way to go. I continue to keep it installed for occasional flights and testing and will keenly follow it's development. For now, though I am really enjoying v4.5 and all of my favorite addons for my regular flights. Jesse
  9. Well, Ray, as I suggested earlier in this thread the Registry Key edit did not work for me. The only thing that reliably solved the issue for me was using MSI Afterburner to set the power limit to 93%. I also would note this caution from Microsoft: "Important These registry keys should not be manipulated by end users, or by applications outside of targeted testing or debugging during driver development." Jesse
  10. Exactly!! That's the reason for my post to suggest the distinction between TdrDelay and TdrLevel. I think you and @MarkW are talking about distinctly different settings. Did you look at the link I provided??? Jesse
  11. Mark, Sounds like you may be referring to setting the TdrDelay rather than the TdrLevel that Ray is referring to. Jesse This link may help: https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys
  12. Actually, I think they are a little different. The Max performance power setting is just forcing the GPU to maintain it's maximum voltage and clock so there are no variations. MSI Afterburner is just lowering the power limit to a value that is more stable. At least that's my understanding of it. Admittedly this is waaay above my pay grade. Of course if the Max Performance setting works for you there is no need to mess with success. Good Luck, Jesse
  13. @Ray Proudfoot I had the DXGI problems also.Tried pretty much everything mentioned above. So, I contacted the guys at Jetline who advised they had found that using the tuning utility called MSI Afterburner can help reduce/eliminate these errors. Simply download and install this app (it’s free). before you run P3D, open MSI Afterburner and set your Power Limit to 93% . You can download the Afterburner program here https://www.msi.com/Landing/afterburner. That stopped the error for me on my Nvidia1080ti.You might want to see if that helps. Jesse
  14. Well, it looks very nice. But, have to admit that I am really disappointed to hear that it won't be coming to P3D. Not sure what changed after all this time but wish you guys luck. Unfortunately I will be passing it up unless something changes to allow you to complete the P3D version. Jesse
  15. Interesting. For me seems quick click activates and slow click closes when using HTML5. Go figure. Jesse
  16. Well, that seems to have fixed the alt key issue I was having. Not sure what else it may effect other than the obvious appearance; which I kind of like. Will just have to keep an eye on other behavior. Thanks for your help. Pierre. Jesse
  17. Thanks Pierre. I'll give it a try, but not sure if that effects the alt key performance. Jesse
  18. Is this a change in 5.2 or do I have something wrong. The Alt key should display the menu but mine doesn't. If I right click and uncheck "display menu" the menu displays and then the Alt key will hide the menu. My searches are producing nothing, so anything you can suggest would be appreciated. And, where is that HTML5 setting. Does that have anything to do with my issue? Is that a .cfg entry? Thanks for any help. Just trying to catch up. Jesse
  19. Take a look at this thread. It may be helpful to you. Hope this helps Jesse
  20. Here is just one of many threads here at Avsim discussing these issues. It describes exactly what Bert is saying but may be worth a look.
  21. @Ray Proudfoot To my surprise, after trying quite a few times I have been unable to reproduce the crash under the circumstances you suggested. However, after considering why that may be and following some additional tests I think something else is at play in my current situation. When I considered what was happening I recalled that a while after successfully following and testing the suggestion to use prefer max performance I then updated my Nvidia driver to 461.72. So as an additional test today I returned to the default Nvidia control panel settings and did some more tests. I have yet to be able to reproduce a Device_Hung error since, even in my most consistent scenarios. So I guess to sum up my situation, after months of consistent crashes and testing it seems that either lowering the max power in MSI Afterburner or setting prefer max performance in NCP, or using the 461.72 driver will resolve the crashes on my system. I think this seems consistent with what @SteveW @westmanand @simbol have been saying.Time will tell if this is reliable for others but for now I hope it is helpful. Jesse
  22. Ray, I have been plagued by DXGI crashes in V5 for quite some time. I haven't associated menu use or "aircraft select" with the crashes but the crashes were regular and completely repeatable even in a plain vanilla default V5 installation. When I get time I will try your aircraft selection scenario but I would expect that it very well may initiate a crash. My test became a flight set up with the default Commander at KAUS. Crashes always occurred before I could even make one circuit. I have seen two solutions work reliably for me. I can use MSI Afterburner to lower max power to 93% or I can use the Nvidia Control Panel Prefer Max Performance setting. In either case I have yet to experience a single crash. Hope this is helpful, Jesse
  23. Hi Bert. This has definitely fixed my issue and seems to make some serious improvements to the PC12. Interestingly, I found it easier to edit my existing panel.cfg to reflect the new gauges rather than trying to make all of the GTN to GNS edits. But all seems to be working as expected now and I am very pleased with having the PC12 back in my hangar. Thanks so much for the excellent support, once again. Jesse
×
×
  • Create New...