Benjamin J

Ooh... You know what, I probably got them mixed up -.- Sorry!

Isn’t verticalsim also working on palm beach? May want to wait for that one…

Yes. I believe it's how MSFS loads 'more detailed' tiles of ground textures. That is, the further away something is, the lower the resolution of the loaded tiles. if there are differences in the coloration of the Bing maps' tiles between two different resolutions, the more detailed tiles will reflect that as 'change in coloration'. The fact is that this is nothing new. This system of loading tiles was present all the way back to at least FS2004, and likely before (but I didn't use those so I have no idea). Conversely, I have found in South Korea that highres tiles actually don't exist at all, so in a defined radius under my aircraft I will see default 'offline' textures popping in, with lowres satellite imagery from Bing maps farther away. I don't think there is anything that can be done about it accept for Bing maps' data or the Azure system that processes it for MSFS to have better cross-coloration.

This is interesting because I've started running into strange instability with MSFS following the Dune and Windows updates. Do you mean the small KB updated from last week or the bugger 23H2 feature update? I installed the formner. I might try to roll back to before that Windows update and see if that resolves things. Currently I'm finding MSFS will randomly crash or hang in ways I've never seen before. Do you know specifically which updates were the most recent February offending ones (KB numbers)?

I had that spinning circle as well and it went away after restart, but I've also been seeing a lot of instability in MSFS. This weekend I've had MSFS randomly crash on me three times, without any seeming reason and event viewer just claims there was an application hang and Windows shut MSFS down. When I managed to fly from PANC to PACV I found performance quite a bit more stuttery than it had been with quite a lot of stutters upon touchdown. Hadn't seen this behavior in a long, long time... Besides the Dune update there was also a seemingly minor Windows update, though not sure what that did. I also installed Tailstrike Prague, Amsim/BMW KMIA and... a third scenery, don't remember what. Never had any issues after scenery install so must be related to the Windows update or Duna update, I'd think.

To you and others, thanks for pointing that out! Haven't gotten around to try it yet, but will do so soon. It seems likely that this was it because I had already set the DH when this happened... Typically I'd wait until a later point but I was a little bored so I started setting things up for approach. Thanks all!

I just flew 1.0.3 - don't think I had any of the issues people mentioned, but I had something weird going on with the auto throttle. I had PROF and NAV activated before takeoff, I activate TOGA as usual, and both activate as expected upon liftoff, and all was well until I got to the point of descent. Because I tend to fly with default ATC (yes, yes I do. Not the point of this post) and their clearances don't follow VNAV calculations, I tend to switch to Alt Hold and select a speed manually, so I can then follow their guidance by V/S. Normally I've had no issues with this, but this time when I selected ALT HLD mode, I couldn't get SPD to select manually - upon pushing the SPD knob, it would show a selectable value but illuminate PRE-SET. I don't remember ever seeing this illuminate to be honest... I saw in the change lists that there have been some changes to the logic of this over different versions but I've never seen an issue like this pop up. Since I couldn't select the speed manually, I stayed with the commanded 280kts pretty much all the way down, until I finally deactivated auto throttle altogether and set thrust manually. Another weird thing here is that it somehow managed to stick with the commanded speed even at pretty steep descent rates, without putting the engines into idle. No idea what was going on here. I assume I'm doing something wrong here but I have no idea what it might be. I don't think I did anything different from usual, but it sort of ruined the flight... I'm not sure if something happened in the update or whether this has something to do with the Brave quadrant I just bought. Perhaps there is some assignment there that I need to deactivate? Any pointers would be appreciated.

I compared the data in Little NavMap with the data in the Navigraph Charts app and didn't see any discrepancies, so went into MSFS and actually I do have all procedures listed... You sure you don't have any duplicate sceneries that are messing things up for you?

Exactly what @Fiorentoni said. The problem is usually that the runway designators of the scenery don’t match what’s in the approach procedures. Usually it means a scenery update is necessary if they are old, or there may be a mistake that needs to be fixed. I have the scenery in question but haven’t looked into it… I can look later today.

Something that I do is to search by airline in Flightradar24. Go to the hamburger icon on the top right and select airlines, then search for UPS or FedEx, and click the Routes tab. It should show you a map with all the airports where flights have been filed. You can have it display all routes and then search for A300 flights. I like doing things this way sinceI often want to fly a particular carrier from or to a particular airport. This method gives a nice overview of all the possibilities.

Me too, which is why I started a custom Google Maps to keep track of all of them, as well as routes that I’d like to fly between them ☺️

LatinVFR already stated in the Facebook thread where they announced these products that they are investing ‘heavily’ in upgrading the avionics and will not allow modding, so no Horizon for any of these aircraft.

Since we are talking about what FB scenery will next be scooped, it’s KMSP. BMWorld/Amsim just posted a preview on Facebook that I’m pretty sure is KMSP https://www.facebook.com/100066830710698/posts/pfbid031U63MF9A2CkoudHvn5XDNTAkMGRg1Fs5DbErzKfF2jAFAPi2WPr4ELTViybmWtZAl/

Interesting… I was already wondering why I saw so many Iranian carriers around Teheran today… it seemed strange to me that fsltl would include them. Must have been from AIG then, since they do include all those airlines.

I did see the Hawaiian 717s, and also saw several at the Interisland terminal! I use FSLTL.