MDFlier

Same here. Just a circle. No effect on the sim. I must have a completely different version of SU14 then the rest of you guys. I'm getting much better performance, sky and ground colors look much better, and the entire sim just seems to look better = everywhere. On top of that I've been able to increase my AI traffic level from 38% to 85% with no performance hit. ATC seems to be doing much better on climb. I got to 40,000 ft yesterday without having the plane start to level off anywhere because I got my clearance to the next altitude too late. Unfortunately, on descent it seems to ignore the altitude constraints on the star that you are flying. It kept me at 25,000 ft for way too long. And somewhere along the line, they managed to fix that constantly repeating ATIS from KFRR that was being picked up for hundreds of miles and couldn't be turned off when flying the TERPZ SID out of KBWI. Overall, I think it is a good update.

Not anti ice, icing. You can turn it on and off in the menu where you set the realism options.

The fix does work for the PMDG 737s, but not for the Fenix.

I've been using AIG traffic for quite a while now but I haven't run the AI Manager for several months. I ran it a couple of days ago and was pleasantly surprised to see that it had a slick new interface after it auto updated itself. I ran all of the flight plan updates, and then used the new North America preset on the Quick Install tab of the main page to let it add any North American airlines that I hadn't installed yet. It added several. The installation process was truly "one click". Over the past couple of days, I've clicked the Global preset and let it install other airlines from all over while I was off doing something else. I like the fact that you can now hit the cancel button, and it will finish installing whatever airline it is currently installing and then stop. It makes it easy to get them all without tying up my computer when I need it. Doing a few at a time like this will definitely help me get them all. I'm in the SU14 beta and I've been playing with the amount of traffic that AIG injects. Prior to now, anything over 40% would cause major stutters on the ground. Over the past 4 or 5 flights I've been increasing that, and I'm now running at 85% with no impact. I don't know if that is because of changes in MSFS itself, or in AIG between last spring and now (I wasn't flying much during boating season). I have been flying mostly east coast between Boston and Tampa so there has been plenty of traffic. LAX to LAS also had lots of traffic and great performance. I'm in cruise right now going from KBWI to KTPA. I've got the MFD set to 40mi range and there's 9 aircraft on the display. They all seem to be following proper flight plans as I've seen several prominent waypoints where you could tell by the contrails that planes were turning there. The altitude offsets are showing correct now as well. I think this is new, too. The Traffic Controller also updated itself. It also seems to be doing a very good job. I haven't seen anything unusual happening around me like I have in prior versions. Again, no idea if AIG or Asobo fixed it. I think Kai has done a great job making things simpler. The old interface had all sorts of things that I'm sure very advanced users loved, but confused the heck out of me. I was often wondering why and when I would ever need some of those buttons. The new interface is a lot cleaner, and its much more obvious how to operate it now.

Uh.... I just got 1.35.18 Never mind. I just read the release notes. Same as .17 on the Xbox.

Ditto. Flying right now. Beautiful scenery, smooth as silk, buildings everywhere that there should be....

Hmmmm.... This might be a clue....

Well, I'm thinking that it is just a one off software error cause by a combination of conditions during that particular flight. I wouldn't knock myself out trying to troubleshoot that one too deep. Fly some more and see if something similar happens again. Technically, that error is trying to read data from the very last bit that can be accessed in memory. Nothing can read anything from that address, because a read command starts reading at the address provided. In this case, it's trying to read starting at the end, and there's nothing to read past the end. So the most likely conclusion is that the address 0xFFFFFFFFFFFFFFFF is the result of either a routine using a bad pointer, or using a good pointer with a bad address (both of which could be SW errors), or memory corruption messing up something somewhere. If it keeps happening, then try digging deeper.

Deleted

Excellent advice, but there's one item that you forgot, which often has people chasing the problem down the wrong path. That item is to also look for log entries from other processes prior to the item with the actual red exclamation point. It's not uncommon for a problem to occur in a supporting application, .DLL, or OS module where it might not completely fail (as in crash and leave it's own red exclamation mark entry in the log) but might return unexpected or invalid results that in turn crash the program that is using that returned information. So... just beware that even non fatal errors in a process supporting another process may cause the crash of the supported process. For MSFS, you would be looking primarily at processes like the ones you mentioned in your post. Nvidia dlls, .net libraries, Windows APIs, etc.. Completely external applications like GSX, FSLTL, AIG, the Fenix external app, etc. are not likely to crash the sim.

I just flew that day in CAVU conditions. 29.92 and 0/0 winds on both ends. I figured I would just sit back and enjoy a day of flying in perfect weather. Of course, it did make me wish I was back on the boat.

Ironically enough, my last rash of CTDs was in September. I used WinDbg to examine the dump file, and it indicated USB interrupt issues (many interrupts happening in a very short period of time) coming from my mouse I switched things to different ports and changed some cables, but the CTDs for the same reason continued. Even though it was apparently working fine, I went ahead and ordered a new mouse from Amazon. Logs do not lie. I received it on October 2nd and I have not had a CTD ever since. MSFS has been rock solid for the last 5 weeks. SU14 is running fantastic for me. Don't write off the simple stuff. I use the addon linker, so on any given flight, I only have the airplane I'm using, the departure and arrival airports (if I have them), GSX, navigraph nav data, and AIG active when I fly.

That's not how agreements between vendors and clients work. When Asobo contracts a weather provider to provide data, they do not take on any roles within that vendor business. They are simply a customer. If that vendor has an issue, Asobo's only role is pestering them to get it fixed.

Well that's definitely Asobo's fault.

That makes no sense. Using your logic, it's Asobo's fault if your ISP has a problem preventing you from using MSFS. In a distributed software environment (aka "the cloud") it takes many different companies all performing properly to make things happen. If a single one has a problem, they all have a problem. But only one company gets the "blame" (in quotes because this is real life, and stuff happens that is no ones fault - i.e. equipment failure, power outages, lines getting hit by people digging somewhere, etc.).

I get why you are confused. The first thing you need to remember is that there are 2 related components. Navigational data in the sim that tells it about the VORs, NDBs, waypoints, airports, runways, and about other procedures like arrivals and departures. Then, there are the charts which allow you to see all of that information. Two separate things. MSFS includes and will automatically update the nav data in the sim each time a new AIRAC is released in the real world, which is every 56 days. I don't think MSFS comes with charts, so you'll need them from somewhere else. If you choose to use Navigraph for your charts, the Navigraph hub is necessary to install them.

The reason we do it is because we don't want to replace files on the server while client machines are in the middle of downloading them. It breaks things... so we don't let that happen. We stop the service that allows new connections, we wait for any machines currently updating to finish, we replace the files, and then we restart the service. Stopping and starting the service is a simple command line or click in the GUI, not an involved procedure. The server isn't offline. It is ignoring you.

I just fired up the Operations Center and the PMDG servers are down. I think they're staging it now.

I've thought that they were for a long time. I have Drzewiecki's KRNT. If you start a flight there in a PMDG 737, there will PMDG flags around the airplane on the ramp. This indicates some sort of cooperation between the two. If you go into the factory and get in the cockpit of one of the 737s being built, the instrument panels have the Max configuration. I've always though that this was a hint about things to come.

And I've noticed how smooth the sim runs, too. I wonder if they found something in the simobject animation system that was causing poor performance? All of my flights have been unusually stutter free on landing and during taxi to the gate.

Did you select the TO runway from the list? Right after you pick it, the numbers will appear.

I noticed it for the first time ever during a flight yesterday. That's been there for a long time? Who knew? I never even saw it before.

Graphic anomalies or glitches are not a common complaint here. Those are almost always the result of data corruption. It could be caused by bad system memory, system bus, GPU buss, GPU memory, or GPU itself. Sorry to hear about your troubles. I think trying to tie a problem to pressing the fly button too quickly is a bridge too far. I am hovering in that spot waiting to click it as soon as it appears quite often, and I haven't had a CTD in months.

Good idea.

If you do a long flight, you can go into Simbrief and edit your flight before you reach ToD to update the wind data. Switch to Simbrief and edit your current flight. Change the time of your flight to sometime current (it usually asks if you want to use the current time so just click yes) and then hit the generate button. Back in the airplane, request the winds again, and you'll get the current wind data for your descent.