byork

FYI, the new Fenix Airbus is "freezing" the tug. The Fenix dev is aware of the issue. Hopefully they'll sort it soon. Cheers,

Are you sure you're not activating the PMDG pushback at the same time? Anyone else have this issue?

Glad you got it sorted. To everyone else, there's really no reason to use the "preview" version of Windows 11 unless you're a software developer. Please just use the normal version to avoid issues such as this. Cheers,

It's not a "may" breach the PMDG Eula. It's a "will" breach the PMDG EULA. We have to wait for the PMDG SDK. No way round it I'm afraid.

When it rains, it pours 😉 In the last few weeks, we've had a slew of major releases: Maddog PMDG 737 and now the Fenix Airbus. I'll keep this short: We'll be supporting them all. Road map is Maddog, then 737 then Fenix. However, Fenix may come before the 737 depending on what happens with the PMDG SDK. We'll have to wait and see. Enjoy your weekend!

Are you using Voice or Button Control?

The Fenix won't come over night. We still have to finish the Maddog, finish the PMDG 737... This stuff takes a lot of time. We can't just whip them out in a week or two...

I gather you're using the "Preview" version of Windows 11. If so, please don't use them. They're buggy. Only use the normal version of Windows 11. Pls see this: https://answers.microsoft.com/en-us/windows/forum/all/i-am-getting-0xc0000135-error-when-opening-any/c80f6cd2-dcb1-4475-9e76-3edc80f86d29

It would work in a limited way. FS2Crew FBW is heavily customized for the FBW (the FBW uses a lot of "custom" names for the variables used to move the switches, etc, and FS2Crew FBW accounts for those custom naming conventions).

Cheers 😉

Glad you got it sorted 😉 Yes, all your old orders are on the legacy site: https://legacy.fs2crew.com/cart/

Can you translate those to English pls.

We will definitely be supporting the Fenix. About failures, it really depends on how much data can be read out of the plane and what's available to us. Cheers,

We need access to view those images. Try deleting the FS2Crew folder in your Community Files folder. Then re-download the Product Manager: https://fs2crew.com/downloads/

What happens if you hit Shift P? Does the tug move? Please remember that PBE utilizes the default pushback system. Also, try it at a different airport in case there is an issue with your airport (if it is 3rd party). And confirm your chocks are out in the PMDG...

Remember there's two steps: 1st step: Connect the tug. 2nd step after tug connects Tell tug you're ready for pushback. You can't just connect the tug. You need to do step 2 as well. Cheers,

Yes, please confirm that.

We will make an FS2Crew for the Fenix, yes.

We can't wait either 😉

Hi Daniel, If VATSIM is not working as well, maybe there is a problem with your headset? That's a wireless headset, right? Wireless can be prone to interference, dropped connections, dead batteries, etc. We generally recommend a cheap USB generic headset. They're less prone to issues.

You said before that according to your UGCX Log file "Advanced Animations" in FSX was not selected, but in your FSX menu Advanced Animations was indeed checked?

Can you post your log so we can see exactly what you're saying?

Hi Mark, This happens to you when using the pre flight events when the time reaches 0? Normally you'd call for the "Before Start checklist" well before the time reaching 0. Then you'd run the "below the line" portion of the checklist at around time 0. You can cancel any checklist by speaking, I recall "Cancel Checklist". Then you could call for the intended checklist again. Also, with Flows, using the "manual flow selector", you can manually trigger any Flow you like at basically almost anytime. But it happens to you again, be sure to look at the Log in the Info Center. It will tell you what the speech system actually heard. Maybe the system though you said "After Start Checklist" inadvertently? Only the log will say. But let me know. If there is something we can tweak or polish, we'd like to know so we can address it.

That's going back a long time... but I recall it was several months.

That's going back a long time... but I recall it was several months.