Phantoms

That's great for you, but it's a known problem with many CTDs and was likely cause of a big CTD saga I had for a long time. When I did finally go through the trouble of making a zendesk bug report, they had me send in a a msinfo file and a dxdiag file from my computer (instructions on how to generate them were also sent. Once I did that, the first thing they replied was: I didn't have any overclock and I wasn't actively using MSI afterburner anymore, but it was still installed on the system. I did a complete uninstall of it through Add/Remove programs. I also reset nVidia, etc. I had one single CTD a month later (probably a one off) after nearly a year of having them everytime I tried to fly and haven't had anymore since. I can't say 100% it was MSI Afterburner ( I changed a couple other things then too), but given the fact that no more CTDs and the fact that it was the first thing MSFS support said leads me to believe it was a probability it was the cause. I'm not really sure that's why. I believe there are conflicts and that's why it's one of the first things suggested. As I said, i wasn't even actively using it but it was still installed on the system. Undervolting itself could be the cause but you won't know until you stop and uninstall Afterburner to check. I didn't use Afterburner to undervolt, instead I used X1 precision for that. But during my trial of trying to find the culprit I had stopped undervolting and also uninstalled X1. However, since I wasn't actively using Afterburner I never thought to uninstall it. But even if you're not actively using it, it still loads up some stuff when you boot. I no longer worry about undervolting (haven't about overclocking for years) which I did simply to not use as much electricity. I'm of the mind now that the more you mess with, the more chances you can cause problems. Edit: BTW, if you want to file a bug report with MSFS zendesk they've made it real hard to find. Here's a direct link to it - https://flightsimulator.zendesk.com/hc/en-us/requests/new

@FlyIce MSI afterburner is the cause of some CTDs and is one of the first things MSFS support will tell you to uninstall.

It moves a little bit of the load off the CPU and onto the GPU. Here's a little article on it - https://www.technewstoday.com/hardware-accelerated-gpu-scheduling-on-or-off/

@SquadronLeader Just a note that FSLTL was updated when SU13 came out, so you might want to run the installer and see if there's an update available for the injector.

BTW, that article also points out that by Windows 10 users have Hardware-accelerated GPU scheduling turned off as default while Win11 has it on by default.

That doesn't seem to be the case if you believe this article - https://www.tomshardware.com/how-to/enable-frame-generation-windows-10 That's not a doubling but it's not bad either.

The Toprudder 103 by Microsoft is excellent for low slow sightseeing.

I use Geforce Experience but basically only use it for the Drivers and Driver Update notifications. I don't mess with the recommended settings, etc. in Geforce experience. I could drop it but then I'd have to remember to go to their website and check if there are any drivers newer than mine, then manually download and install them. With Geforce experience, I get a notification there is a new driver and if I click install then it gets it for me and installs it automatically. I know Geforce Experience uses a ton more resources, but it's just so convenient.

Does MSFS ATC mimic the differences? What I mean is will you hear those lower Flight Levels as FL in MSFS in those locations, or will MSFS still call them in feet?

Shows that I rarely go very high (at least to FL status). In most places I fly it would be called 10,000 ft., not FL100. In the US, FL starts after the transitional altitude (18,000 ft.) and below that (QNH) you would only hear altitude in feet.

Wouldn't FL100 be 100,000 ft? Or are you referring to 10,000ft? If the later from Bahamas to Miami I would think there are several that fly below oxygen required level (not many commercial mind you). Thank you for spotting the cause. This flight plan was made in MSFS World Map flight plan editor with Low Altitude Airways set and a cruising altitude of 10,000ft set. I guess MSFS is a little janky, just a different part of it (perhaps it should of pointed out an error). I now know to save and go through and carefully pay attention to everything in the flight plan that MSFS makes.

Just want to make sure it's nothing I'm doing that's causing it.

I'm not a pilot so I'm sure I'm missing something. Many times during I get in a fight with ATC wanting to increase my flight level well above my flight plan altitude that I made using Low Altitude Airways in the World Map. One I almost always have issue with is flying over the ocean, mostly clear skys and low amounts of traffic between HEYDR and JEKER. My flightplan was made in the World Map using Low Altitude Airways and set for cruise of 10,000 Ft, but I'm constantly bombarded to climb and maintain 19,000 ft. Is this a airspace issue, a airway issue or just a janky MSFS issue? Here's my FP as made by the MSFS World Map. <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>Lynden Pindling Intl to Miami-Opa Locka Executive</Title> <FPType>IFR</FPType> <RouteType>LowAlt</RouteType> <CruisingAlt>10000.000</CruisingAlt> <DepartureID>MYNN</DepartureID> <DepartureLLA>N25° 2' 20.25",W77° 27' 58.43",+000013.25</DepartureLLA> <DestinationID>KOPF</DestinationID> <DestinationLLA>N25° 54' 26.70",W80° 16' 41.60",+000000.00</DestinationLLA> <Descr>Lynden Pindling Intl to Miami-Opa Locka Executive</Descr> <DeparturePosition>PARKING 23 PARKING NONE</DeparturePosition> <DepartureName>Lynden Pindling Intl</DepartureName> <DestinationName>Miami-Opa Locka Executive</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="MYNN"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N25° 2' 20.25",W77° 27' 58.43",+000013.25</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <RunwayNumberFP>14</RunwayNumberFP> <ICAO> <ICAOIdent>MYNN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="D0"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N25° 1' 8.78",W77° 26' 21.04",+000400.00</WorldPosition> <Alt1FP>416</Alt1FP> <AltDescFP>AT_OR_ABOVE</AltDescFP> <SpeedMaxFP>-1</SpeedMaxFP> <DepartureFP>FREDY2</DepartureFP> <RunwayNumberFP>14</RunwayNumberFP> </ATCWaypoint> <ATCWaypoint id="FREDY"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N24° 59' 42.00",W77° 24' 45.00",+000800.00</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <DepartureFP>FREDY2</DepartureFP> <RunwayNumberFP>14</RunwayNumberFP> <ICAO> <ICAORegion>MY</ICAORegion> <ICAOIdent>FREDY</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="JUTED"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N24° 51' 8.00",W77° 34' 1.00",+003200.00</WorldPosition> <SpeedMaxFP>210</SpeedMaxFP> <DepartureFP>FREDY2</DepartureFP> <RunwayNumberFP>14</RunwayNumberFP> <ICAO> <ICAORegion>MY</ICAORegion> <ICAOIdent>JUTED</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HEROM"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N24° 53' 48.00",W77° 45' 45.00",+005400.00</WorldPosition> <SpeedMaxFP>210</SpeedMaxFP> <DepartureFP>FREDY2</DepartureFP> <RunwayNumberFP>14</RunwayNumberFP> <ICAO> <ICAORegion>MY</ICAORegion> <ICAOIdent>HEROM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="NICKO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N24° 59' 27.33",W78° 10' 45.56",+010000.00</WorldPosition> <SpeedMaxFP>210</SpeedMaxFP> <DepartureFP>FREDY2</DepartureFP> <RunwayNumberFP>14</RunwayNumberFP> <ICAO> <ICAORegion>MY</ICAORegion> <ICAOIdent>NICKO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="PEACH"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 25' 46.67",W77° 46' 22.84",+010000.00</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>PEACH</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SOFAR"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 31' 59.97",W78° 14' 52.89",+010000.00</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>SOFAR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HEYDR"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 34' 37.45",W78° 26' 54.78",+010000.00</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>HEYDR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FANUP"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 38' 44.80",W78° 45' 58.99",+010000.00</WorldPosition> <Alt1FP>19000</Alt1FP> <AltDescFP>AT_OR_ABOVE</AltDescFP> <SpeedMaxFP>270</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>FANUP</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="JEKER"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 42' 20.99",W79° 2' 49.77",+010000.00</WorldPosition> <Alt1FP>14000</Alt1FP> <AltDescFP>AT_OR_ABOVE</AltDescFP> <SpeedMaxFP>270</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>JEKER</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DOPLY"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 45' 23.99",W79° 17' 13.37",+010000.00</WorldPosition> <Alt1FP>10000</Alt1FP> <AltDescFP>AT_OR_ABOVE</AltDescFP> <SpeedMaxFP>270</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>DOPLY</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="OLAHS"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 50' 21.16",W79° 35' 58.06",+010000.00</WorldPosition> <SpeedMaxFP>270</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>OLAHS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FISHB"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 51' 7.21",W79° 38' 1.93",+010000.00</WorldPosition> <Alt1FP>5000</Alt1FP> <AltDescFP>AT</AltDescFP> <SpeedMaxFP>250</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K</ICAORegion> <ICAOIdent>FISHB</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="JEPSI"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 59' 15.58",W79° 57' 8.65",+009900.00</WorldPosition> <SpeedMaxFP>250</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K7</ICAORegion> <ICAOIdent>JEPSI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FRRDY"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N25° 59' 57.26",W80° 28' 24.83",+004300.00</WorldPosition> <Alt1FP>5000</Alt1FP> <AltDescFP>AT</AltDescFP> <SpeedMaxFP>250</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> <ICAO> <ICAORegion>K7</ICAORegion> <ICAOIdent>FRRDY</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="A10"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N25° 59' 52.86",W80° 33' 58.06",+003300.00</WorldPosition> <SpeedMaxFP>250</SpeedMaxFP> <ArrivalFP>OLAHS3</ArrivalFP> </ATCWaypoint> <ATCWaypoint id="KOPF"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N25° 54' 26.70",W80° 16' 41.60",+000000.00</WorldPosition> <SpeedMaxFP>-1</SpeedMaxFP> <ApproachTypeFP>RNAV</ApproachTypeFP> <RunwayNumberFP>9</RunwayNumberFP> <RunwayDesignatorFP>LEFT</RunwayDesignatorFP> <ICAO> <ICAOIdent>KOPF</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document>

I just got this aggravating thing today with the white dot and flickering mouse. Made it impossible to hold any buttons down. I checked and was on Lock, switched it to Legacy and was able to control my mouse (hold buttons down) after. I don't know if it was on Legacy and got switched to Lock or what. I have occasionally seen the white box issue before after the last SU, but not the white dot until today.