yosss

Happy new year to all of you from Norway!

Stated at page 11 in the included manual. Make sure the landing gear lever is down, and latched before engine start 😊

It had to do with the gear lever not beeing set in the down position. Since I have unticked "detect crash", it ended up accelerating in a swirl, resulting in a CTD. Seems to be working now.

I just bought the DC3. It looks really good, but at this point I am having some trouble with it. When I try to start the engines the entire plane starts spinning around, resulting in a sim crash. While I am troubleshooting, could anyone confirm that it actually starts and works like it should? Looking forward to sort this out. Thanks in advance!

Thank you for the reponse. yes. I've read the changelog, but the FO always sets the landing elevation to 6000 even if the elevation at the destination airport is below 6000 feet. This happened on both of my flights today: ENGM - ESSA and ESSA - EKCH.

Hi. I don’t know if this is related but the FO now always sets the landing altitude to 6000 at every flight for me. Just updated to latest version.

I can confirm this. Working flawless on my system.

That’s the only thing I did different, I believe. But could of course be something else. I am glad the issue somehow sorted out. Thanks for the support, anyway.

I reinstalled Fs2Crew and can confirm that everythings works again. I have no idea why it didn't work. And again, thanks for this wonderful piece of software!

I'm pretty sure the flow completes. I will try again and pay close attention on my next flight. I'll report the result.

Thank you for your response. The flow get's triggered, I'm used to FS2crew for the old NGX and I don't have this issue with the old one. Is there anything else i could try?

Hi there! I am having an issue with Fs2crew for NGXu while using button control. When I reach the gate at the destination airport I turn off the taxi lights, set the parking brake, start levers to cutoff and turn off F/D on both sides. Then I call for the shutdown checklist. The first officer responds with "Standby". Nothings happens at this point. A workaround is to manually select the down arrow key and force fs2crew to continue. Maybe there is something I am doing wrong here? I have no axis assigned to Mixture control. Thanks in advance. Cheers

FS2Crew already supports it. Just open the configurator and select A321X 😀

Make sure you have set "global texture resolution" to high in the main display settings page.