Adamski_NZ

Many thanks! I'll give it a whirl! ;)

Sounds pretty good - and coded by a real human too! I haven't downloaded it yet ... but how would it integrate with something like the iFly 737Max8, where you [typically] load the aircraft (and MCDU) by transferring the Simbrief data via the EFB?

I'd love to give it a go ... but SHE will be ringing for the white van to take me away if she hears me talking to the computer :(

Great to hear it's sorted! :)

They've been a problem for ages ... are they ever going to fix them? I just ran a series of comparisons over various areas. Some PG works fine (and looks great), but it still has far too many "melted" objects (including generic objects like trees, rocks etc.) for my liking.

Shows up fine on my (MS Store) system - with and without photogrammetry, all updates and POIs enabled. I'll put up some pics shortly ... ... and this is why I hate photogrammetry:

I may be wrong, but I think GSX only does the visuals of any loading process. To get the aircraft correctly loaded with fuel, PAX or cargo you're always going to have to use the EFB etc. as well. External addons (like BATC) can inter-react with GSX and trigger certain GSX operations but, again, they won't change anything in the actual aircraft payload. At least that's the way I think it works - and I'm open to be corrected (!).

W-h-a-t? Look at the changelog - and tell me the software wasn't improved <?>. I don't think BATC costs that much, compared to other [subscription type] addons, so you can't accuse them simply of going for the money. Developers need to be paid for their time. Also - what's wrong with building a supportive community - isn't that what we all want?

Wow indeed! Thanks for posting :)

Great! I just had mine update to 1.9.14 (experimental). Any ideas as to the changelog? BTW - the survey shows they are listening - and actively working on fixes/updates etc.

The "Scene change detected without reset flag" message is a standard MSFS SDK/DevMode warning. It appears when the simulator's engine undergoes an abrupt render state change without a prior "reset" signal. For developers, this means a custom code script, visual effect, or third-party camera switch altered the scenery state improperly. For players, it's often triggered by unstable mods or camera transitions. [1, 2] If you are a Player/End-User: Check the Mod Folder: This warning often flags a corrupted or outdated mod. Empty your Community Folder and test the game to see if the issue persists. [1, 2, 3] Avoid Camera/Plane Switching: Toggling between planes, drone cameras, or developer teleport tools while your flight is active often forces unflagged scene changes. [1] Verify Game Files: If using Steam, right-click MSFS, go to Properties > Installed Files, and select Verify Integrity of Game Files to fix any broken core files. [1]

GSX might do it (sort of). I think the problem is a more general one for MSFS though: how to have more than one consecutive flight in a session. Most addons seem to use Simbrief, so you'd need to recreate/re-file a new flight plan for the next leg. I suppose you could create a series of PLN files (using Simbrief) and load them in turn, but I'm not sure how GSX would handle it. I could give it a try though ...

From what I can gather, all ATC/AI addons suffer from interfacing with core MSFS to a greater or lesser extent. I wish Asobo would get its act together ...

Same here, I'm afraid. It's always the descent/approach phase that lets it down. However - I still really like the addon and hope it keeps improving.

Unfortunately, Addon Linker users will have to switch totally. I've been using AL for years now and am reluctant to mess it up. I have all my addons categorised by civil/military, then area/country. Selecting (say) military/NZ is just two clicks. To me, that sort of convenience far outweighs the "where should I fly next?" scenarios that Preflightly might offer.