cannonplug

I keep hoping it's a simple matter of an unpaid hosting bill while Ben is out of reach (which he has been before), but a lot of time has passed now. I do hope he's well.

That rules it out, I guess. I'll keep experimenting...

Same here. Twice during my last flight, it hung for 2-3 minutes each time. And then things went back to normal and I was able to continue the flight. I'd never seen these hangs in any previous flight. The only change to my system was that this was my first flight with FSLTL. I had been using AIG for AI before this.

I feel for you, I really do! I hope you soon get a nice heavy downpour that washes all that stuff down the stormdrains.

Is it safe to assume that PMDG has not acted on this yet?

Haven't had a chance to sit down with it just yet. Next week my schedule seems a bit more reasonable. I'll have a look then. EDIT: I actually had a little time right now and was able to track it down. It was a utility called RGB Fusion that came with my motherboard. I must have installed it as part of a utility package. I don't even know what it's supposed to do. Anyway, all's well now.

Just deselect all the Envtex sliders. If you're not making any changes to Envtex, you don't need to leave those options on. With them off, installing the Envshade shaders should only take a few seconds.

Thanks Bryan! It's an SSD. I'll look at my running background programs when I get a little time. I can probably run it down with a little diligence. I'll report back when I figure it out.

Hi Bryan, I'm writing to see whether you might have an idea what could be causing my FS2Crew installers to hang. Right now, I'm trying to install the latest FSLabs Crew and it's hung at the 28% mark installing the FS2CrewData.ini file. I've seen the same behavior with the PMDG 737 and 747 installations. Strangely, the last few versions of the 777 Crew have installed very quickly and without issues. In the past, sometimes waiting for a while has been enough to complete the installation (like this very instant!). Other times, waiting even 10 minutes or more has not worked, so I've gotten it installed by going into Windows safe mode. I imagine this is something unique to my computer or I suspect I would have found others having the same issue. I just can't seem to find any spurious program running that would interfere with the installation. The only AV I have is MS Defender, and turning off real-time protection and excluding all the relevant folders doesn't seem to do the trick. This isn't a huge deal because I've always managed to get them installed in the end. It just would be nice to figure out where the issue lies.

I run all these things and got the DXGI crash early on in v5, but since I toned down the overclock on my 1080Ti, I haven't seen it a single time. My card is one of those gaming ones that is overclocked from the factory. I had no idea about this overclock until someone mentioned it in one of the forums.

Had some time to do a little troubleshooting on this and found that a good number of my JustSim sceneries had this issue. It seems the LGRP installer wiped out the windsock texture file in my case. What I did was reinstall another JustSim scenery – LEPA, I think – and the windsocks are back everywhere.

Strangely, I don't see this. In my case, the FO puts the FCTL display on the lower center DU, as you're requesting. I really have no idea why that is.

I did try out the new 200ER without my FS2Crew today. Nice flight! So automated, I didn't really need my co-pilot. But boy, was it quiet! And lonely. I'm glad the update is coming soon. 😀

Thanks for the info, Bruno! Mystery solved...

Right after releasing the parking brakes, if I notice that the airplane won't move, I fully apply the brakes for a second, and that breaks it free for me. It's a shame that isn't working for you. We probably don't have the exact same problem, though it sure seems similar.

I've been seeing this for a long time now and have unfortunately never found a permanent solution. What I do have is a workaround: a quick full application of the brakes before taxiing always releases them for me and I can taxi normally after that. Give it a shot!

Hi Ben, I know you're busy putting together the last few pieces of the A320 course, so I'm not expecting a quick response here. Anyway, in the Q400 Cadet program, during non-icing operations, the engine intake switches were always left in the closed position with green lights on. But then in the FO program, those switches were always left in the open position with lights in amber. I was wondering whether it was simply a change in SOPs or if there was another reason for doing so. I know it's been a very long time since these programs were recorded, so I understand if you can't remember why the change took place. I've done a few Google searches on the topic but haven't found anything. Incidentally, these programs, together with the 777 Cadet course, have aged really well. They're all still as relevant today as they were back then. Kudos for all of these, and now for the A320! I've enjoyed them all.

Now it's Turkish delight on a moonlit night 😁

I'm very happy for you, Ben, not just because of your return, but because things seem to be going so much better for you now. Stay well!

Glad it's working for you! Gives me some ideas where to continue looking.

After a few days of experimenting, I'm right back where I started. I tried both the default MS drivers and the newest Realtek driver and, for a short while, the problem seemed to be gone. But after just a few restarts, the crash on exit came back (ucrtbase.dll). No amount of driver cleaning and reinstalling has changed anything since then. Then I remembered that I had also updated Windows to 20H2 before trying the new drivers. This Windows update is likely what caused the crash to go away for a few tries. And then something broke... again. To me this isn't a very big issue because it's now almost second nature for me to click on HS before I quit P3D, but still, it would be nice to get to the bottom of this issue someday.

I'll add my +1 to this topic, though in my case it's the CTD that Ezio is describing, not a hang. I've had this issue continuously throughout several P3D and FSLabs updates. If FS2Crew is deactivated, P3D always ends without crashing. With it, it crashes, unless I click on HS before shutting down. I just noticed that there are newer Realtek audio drivers for my motherboard (from two weeks ago). I'll try them first (probably later today) and, if those don't fix it, I'll try the stock Windows drivers and report back. If after that the issue persists, since this is 100% reproducible on my end, you're more than welcome to poke around my machine in a Teamviewer session if you feel that will help.

It is intentional. It's heeding the rules: https://en.wikipedia.org/wiki/NATO_phonetic_alphabet

For boarding purposes, I start FS2Crew 37 or 38 minutes before my intended pushback time and then request boarding in the ATSU at a time that is 21 minutes before departure. So, I get the request to board about a minute before GSX actually starts the boarding process. I also have GSX boarding set to dense. This way, everything usually wraps up in time for pushback and the flow seems natural. With a full A321, I believe I've had to set the density to very dense so that boarding completes on time.

Indeed! Other enhancements that have made the purchase worthwhile for me (in addition to those mentioned already): the improved ground friction model, the new steering model, and, most important, the continued development. I just saw a post from Randazzo on how he fought to get the autobrake to behave better. I'm also looking forward to the promised LNAV improvement. Having said that, I'm not a PMDG surrogate, and I'm not trying to sell this plane to anyone. If you don't see value in the new version, just don't buy it. I simply don't care whether you do or not. But for those who insist on running it down, do those considering purchasing it a favor and don't pass off your opinions as facts.