Adamski_NZ

OK - we some progress/enlightenment ... YES .. the ATC command ("boarding passengers") does indeed work (thank you!). So ... is it down to FSDT/GSX to find a solution?

Well ... after the SU2 update (which went OK) ... I simply cannot get past this 5% roadblock. I've retried ALL the known fixes/workarounds out there and none of them worked. I'm left with a sim that I can no longer run. "Not fit for the purpose" springs to mind - but what can I do ... any ideas anyone? UPDATE: I think I have a solution ... deleting all the contents of the Community/StreamedPackages folder seems to cure it (for a while at least).

... AND ... trying to remove useless/old control profiles still causes an instant CTD. They've only had four years to sort *that* one out.

Doesn't work via the ATC command for me 😞

Thanks for that 🙂 ... so whose responsibility is it to fix? NZA, GSX, or Asobo (or a combination of all three, LOL)?

I have the same problem. Do the jetways work if GSX hasn't been installed, I wonder? I've had both active since day one, so not in a position to tell.

Same problem here ... after the SU2 update. Grrr .....

Well ... after the SU2 update (which went OK) ... I simply cannot get past this 5% roadblock. I've retried ALL the known fixes/workarounds out there and none of them worked. I'm left with a sim that I can no longer run. "Not fit for the purpose" springs to mind - but what can I do ... any ideas anyone? To add to that ... I don't see the point of having a rolling cache (at all) if the sim has to redownload/activate everything for each new session.

Well ... after the SU2 update (which went OK) ... I simply cannot get past this 5% roadblock. I've retried ALL the known fixes/workarounds out there and none of them worked. I'm left with a sim that I can no longer run. "Not fit for the purpose" springs to mind - but what can I do ... any ideas anyone?

I also suffer from this problem occasionally - and have tried all the voodoo/fixes around. To be honest, I don't think *any* of them actually work permanently. Often, a simple reboot or sim restart cures the problem (for that session) - giving the impression that the previously applied "fix" worked. The problem usually surfaces again the next day. After all my digging around, I've come to the conclusion that it's a Microsoft *Server* problem - and totally out of our control. Sometimes a reboot (or new session) creates a new/better connection to the servers - and sometimes not. Whatever it is, it effectively renders an expensive product totally useless. Microsoft/Asobo have had FOUR YEARS to sort this mess out.

All's well that ends well! 🙂

That's probably due to the editing software in use - rather than the method of taking the original shot. The shots I posted are totally unedited (except for cropping). My day job is a Web Developer, so I have access to a decent image editor (Photoshop) which does a fine job of saving in JPG from the [lossless] PNG original. However - I'm not sure how (or if) using HDR mode affects things (see previous post). For what it's worth: though I sometimes take screenshots via the native MSFS method, I generally use the facility available from within Reshade, since I use it all the time to try and improve lighting for both sky and terrain.

Good question - but I'm afraid I can't answer that, as I don't have an HDR-compatible monitor so that option in MSFS is greyed out. Does HDR mode make cloud lighting better or worse, I wonder?

Not sure why you're recommending a 3rd party screenshot utility when you can configure MSFS to save in jpg or (lossless) png format - and just use the inbuilt screenshot function.

Here's a comparison: The default MSFS 2024 image (with fairly bleached out clouds): The same view but with a relatively subtle Reshade filter/profile applid: The filter can be tweaked to give the clouds more drama, but then the terrain tends to go too dark/contrasty. It's a balancing act.