Every FO response is "Flaps up"

[Ratherbflyin 9]

I completed a flight being careful of com frequency. That seems to work, no flaps up on that flight! Thank you for solution!

[byork 2,260]

Glad it works!

[Ravencraft 0]

I was getting the "flaps up" issue. The freq. change works for me. Easy fix until the patch. Thanks for the great add-on.

[PrestonIV 1]

WOW! Thats the first time Ive ever found a bug that actually led to a solution! :(

[TexasGary 47]

I use Radar Contact, and it assigns 121.65 for Ground quite often. To avoid this problem you can change the frequency for Ground Control in the Controller Info section when you load your flight plan.

[gmohr 0]

Wow this must have been a wierd one!

[chiozza 0]

I am also switing to the short panel as well..Same issueEverything has worked fine until now. I go through the PF and get to the B Start Proc and when I call it the FO keeps saying flaps up.

[PrestonIV 1]

Keep in mind you can still get the "Flaps Up" no matter what the panel state is. You have to double check the COMM frequency if it happens and make sure its not on 121.65. Some airports use that frequency for Ground communications, like KLAX. As soon as you request a departure, it switches the panel to that "bug" frequency.

[ginopatrassi 7]

Got the same issue here, no maddog!I'm not gonna reinstall all the 737 with all the liveries and tweaks! Just solve the FS2CREW problem please!Thanks.

[KevinMM 22]

You don't need to re-install!!! Just avoid 121.65!!!!!!!

[byork 2,260]

Correct, issue is avoided by not setting 121.65 in Comm 1 or 2.This is fixed in SP1.

[pfpeter 3]

Correct, issue is avoided by not setting 121.65 in Comm 1 or 2.This is fixed in SP1.

The problem also exists on freq. 121.67 on Comm1 or 2.

[byork 2,260]

This fixed in SP1.The problem was a missing ) in my code.Cheers,