Jump to content

Recommended Posts

Posted (edited)

Today I made flight from KCLT to EDDM.

One hour before TOD I set the approach (RWY/STAR/VIA) for EDDM. I checked the flightplan and saw I used the wrong STAR. The runway was 26R ,the VIA was MIQ but the STAR was BETO1B. So I went back to the arrival page on the FMC. I didn't change the RWY neither the VIA only the STAR to ROKI1B. Then the plane partially frozen. No sidestick command, no throttle command and some other functions didn't work. 

I tried to save my flight. So I pushed the "save now" button and entered a text but the flight wasn't saved.

Next I restart the flight by using the last autosave on a runway near the frozen point.

At the first try the plane starts in cold and dark. I put on the ext. power and load the last autosave. But it was the same conditions like the frozen one.

Second try I set the plane again at the same Airport. The plane came up in "ready for takeoff" mode, but also partially frozen as before.

Third try, same Airport, same mode as before, and everthing works. I set the right approach (26R/MIQ/ROKI1B) w/o any error.

 

Maybe someone can reproduce this error to find a solution for this issue.

 

Frustrated regards 

Edited by Roadie04

My System:

MSI tomahawk max z790 mainboard; i9 14900K processor; msi geforce RTX4080 super graphic card

Thrustmaster Airbus TCA Throttle & sidestick; WinWing FCU & EFIS L, Stream Deck XL & Stream Deck+

Razer Seiren mic, cobra pro mouse, ornata v3 x keyboard

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...