Mikeingreen

That's the one. ;)

I mount my yoke/throttle quad to my desk with the Honeycomb pad units when I want to fly. Much better system than using clamps of some kind.

I have been wondering how it would run on my laptop. It has an I7-10750 with 16g of ram and a GTX1650 on a 1tb nVME. I have held back as the 1650 only has 4g of vram but I am going on vacation in Sept and mught just try it out.

Set controls to Legacy, maybe? That is where I have mine and I don't see that at all.

Same here with a 100mb fibre connection, but only since SU5. I agree it is something in the update causing it.

I am not using any online ATC, just in game and it is NOT working as I was told to expedite my climb to FL230 when I was at FL230. I don't see how you can say that is FIXED.

I am not so happy. ATC is still telling me to expedite to my assigned altitude when I am at my assigned altitude.

Ain't that the truth 😂🤣😂

This is my hope too. The High temp at altitude is the most glaring issue to me right now. I guess I will just stay low & slow until it does come out.

If ever a thread had "run it's course" I believe this one has.

My system was rock solid with SU4 and before. The 1st flight of SU% I started getting CTD's. I had been running an older AMD driver as that is what "worked" for MSFS before SU5. I installed a new driver and no more CTD's. Then a newer version of SU5 brought back the CTD's. After trying multiple "fixes" I tried installing the newest AMD driver in the "Driver Only" option, meaning no AMD Control panel thingy. No more CTD's. So, Richard, who is at fault? Asobo or me?

I am sure you don't want to hear this but I am not having an issue with the TBM and my Honeycomb Bravo. I just have to use 2 levers, Throttle & Prop. Keep the Prop maxed until shutdown when I pull it back. That shifts the in-cockpit lever to the right.

No, Bob, that is an actual screenshot from the game. The 2nd pic was with my phone. After doing that I could understand why some of you guys were complaining about the washed out look and blurriness but I wasn't seeing it. The 2nd pic is what I was seeing except without the camera moving and the weird checkerboard looking artifacts.

I can only speak from my experience. I have been running MSFS since last August. In that time I have had 2 series of CTD's and both of them after changing from a Vega64 card to a 6800XT. 1st batch was cured by going to an older driver and disabling Freesync. I just explained how I cured the 2nd series. So for me, both instances were caused by the user, not MSFS. But they can be a word not allowed to chase down. I don't envy A/MS in their quest to fix them.

I was plagued by CTD's from the start of the Beta this time around and it was not helped by also running Win11. I guess I am a gluten for punishment but I do like a challenge. I tried ALL of the posted "fixes" but nothing seemed to help. Ran an empty Community folder, I don't o/c my system, kept a vigilant eye on temps, etc, etc, yadayadayada. I maded one small change by installing the latest AMD driver with the "Driver Only" option and my CTD's have vanished for days now. I miss having a way to control my gpu fan speeds or have any driver level options but I will gladly trade those for no CTD's. I tell this story to show that A/MS won't have an easy time eliminating CTD's and to show that some, if not most CTD's do in fact start t the User level. No matter how much we want to think that they don't.

Here we go: MSFS Screenshot: and MSFS/HDR: Using my phone wasn't the best but I am too lazy to get out my Sony Alpha. Plus I may not have been quite steady enough. Couldn't insert image!

Yes, HDR is enabled and I have an HDR multimode display. I took a pic with my iPhone of the display. If I can remember what my password is to an image site I will post the comparison shots. They are night and day different. I can see why people not using HDR are having issues.

Shift+Win+S worked but the quality leaves alot to be desired pasting it into Paint or Gimp. Colors were all washed out and hazy. Nothing like what I am seeing on my display.

I am off to try that, thanks

I have a quick OT question. How are you guys taking the screenshots? I tried yesterday using the xBox Game Bar but couldn't make it work.

I used the Longitude Mod yesterday but was sorry to see the "wing wobble" is still there at higher altitude. The wobbling back and forth is a deal breaker for me and why I don't fly the Longitude very much at all.

I flew the Baron yesterday and did not have any issues with the fuel selector.

I don't normally run with HDR enabled, but after reading this thread I decided to go back and see what changes it would make. Enabled it in Win11 and then started MSFS. When it started loading pages I was appalled at the total over saturation that was showing. The pic of the rhino was practically glowing. I then checked the Graphic options and saw that HDR was turned OFF. I turned it on and it was night and day difference. Loaded up one of the Discovery flights, the one in Italy, and was impressed in the visual quality vs non-HDR. I then tried the different HDR presets that are available with my Dell display, choosing the "GameHDR" mode, and MSFS has never looked better on my PC. I guess you can teach and old dog a new trick. Now here is to hoping the CTD's stay gone.

I have a Series X and have MSFS installed. I pulled it up once to see it and probably won't go back to it. Having to change things to use a controller in the menus and then flying with the controller has 0 interest to me. I will stick with the PC and my external controllers, now that I have found my CTD solution. 3 flights down now without issues.

I may have to update my poll selection. I had to make some major config changes when going to 1.18.9.0 but did in fact get it mainly stable. Once we went to 1.18.12.0 and then 1.18.13.0 I could never complete a flight. I either CTD or video just froze. That to me would mean GPU temp issue but that was never the case as temps were well within range. I had tried numerous drivers for my 6800XT, even as far back as last November which wasn't easy under Win11. But I could never keep a driver as Win11 will update them behind the scenes and then I would get a warning from the AMD control software about the driver version being wrong. So today I got the idea to update to the latest WHQL driver but doing the Driver Only option. The down side to that is I no longer have a way of controlling the GPU cooling fans. But the upside is that I have now been able to complete 2 flights in a row without any issues. I guess there is some kind of weirdness in the way that Win11 gets along with the AMD control software. I know it doesn't like Ryzen Master either and will not even let it load completely. I am now off to put away my TCA Airbus stick and hook up my Honeycomb stuff and see if I have the same success. Fingers crossed along with toes