byork

Glad you got it sorted 😉

I'm not sure I follow. UGCX needs to create a scenery index. That's normal. Are you able to open the UGCX panel via the ADDONs menu? Please see the FAQs thread if not. Cheers,

Please download the latest version via the Product Manager... you don't have the latest version: https://fs2crew.com/downloads/ For flight controls check, are you following the order listed in the ASSIST PANEL? Elevators first, then ailerons, then rudder.

We recommend a generic USB headset. You can get one for around $30 USD.

Do you see this folder in your Community folder? "fs2crew-data-proc"

Yes, we need the Log. You may have a bad airport or something in there.

The MSFS version of RAAS creates the runways database by itself. It's hands-off. You don't need to do anything. The FSX/P3D version is different: In it, you need to run MakeRunways.

You can do it, but FS2Crew will flip some of the switches on the FO's side. It won't be 100 percent perfect, but it's more than do-able.

Thanks, we'll add to that to our list.

FS2Crew Fall Sale! All FS2Crew's at sale pricing! https://fs2crew.com/shop/

Huh? The Product Manager displays a warning if MSFS is running. MSFS must "not" be running when you attempt to install an FS2Crew. Also, please use our new forum or Discord. Discord is really the best now. It's essentially replaced our forum... it's 100 times more active. https://discord.com/invite/ZJ4HKx727m

So you want "prepare for arrival" at FL180?

Are you using a payware airport with a slope? Try it a default airport please.

Which sim? FSX/P3D/P3D v4/5?

What about the tugs?

Try uninstalling your audio driver. When you restart Windows, it will install a generic audio driver. Cheers,

Please ensure "ENABLE HTTP SERVER" is checked on the FS2Crew PBE Setting Panel. Also see this: https://fs2crew.com/fs2crew-command-center-troubleshooting/ Try the start Command Center at Windows start option.

Hi Roy, If, after you registered, you are prompted to re-enter your serial code each time you run FS2Crew, please: 1. Ensure your firewall is not blocking the FS2Crew EXE file(s) located in your Program Files X86 folder. The test is to try again with your Firewall off. 2. If you registered your product while the FS2Crew EXE did not have Admin rights, remove the admin rights from the FS2Crew EXE. If you registered FS2Crew while the FS2Crew EXE had Admin rights, then you removed those admin rights at a later time, re-add the Admin rights to the FS2Crew EXE. The FS2Crew EXEs are located in: C:Program Files (x86) [FS2Crew product name] By right clicking on the EXE, you can select the Admin level for the EXE. For your cancelled order status, please send us a support ticket via: www.fs2crew.com so we can look at your order payment history.

Are you using P3D v4/5? If using FSX or P3D 1 to 3, install the Global Voice set in your FS2Crew PMDG 777 folder. If P3D v4 to 5, the Global Voice set is built it. It gives you more voices.

Which voice set have you select US or NA? There are two for America. "US" and "NA".

Hi Ken, You can only use what voice sets are available.

Airbus changed all its procedures not too long ago. The Below the Line stuff is now gone. Why Airbus did it... you'd have to ask them. There's a link to the FS2Crew manual on your desktop. We modelled the "new" Airbus procedures. Please check it over. You can see how things have changed a lot.

We corrected a WASM issue for the SU 10 beta. Look on the ABOUT page in the Info Center. What does it say for WASM version number. Wasm is how we read data out of the aircraft using LVARS. Maybe WASM failed?

Hi Toby, It does work with the Rudders in Pushback Express now. We are the only 3rd party tool pushback tool that support the updated Fenix and FBW this way. Please update to the latest version via the Product Manager!

It's all right here: https://fs2crew.com/fs2crew-command-center-troubleshooting/ Your EXE.xml is corrupt. Easiest solution is use the Load Command Center on the Windows start option. This bypasses the DLL.xml entirely,