Deleted Account

Thanks, I'll forward to sound guy to take a look at it 🙂

Yes, this is known and will be fixed in the next patch.

Because that is not how it works on this plane / an Airbus. You need to click the R-LSK of the waypoint you want to edit, then put in the restiction in the VERT REV A page as people in this thread already said. @Maverick_2000 Can you confirm there is nothing in your scratchpad when you click the R-LSK? Maybe show a video?

Thanks, we will take a look 🙂

Heya! Which procedure out of KIND seems to be a problem? I just tried the OOM5 out of 23R, deleted the MANUAL leg, and it flew it no problem. Please understand that we can't replicate issues if you give us minimal information. For all reports like this we NEED the full route, weights, CI and FL.

Minumum callout got added in 1.0.2 🙂

For future reference, no need to shut down the engines, you can always enter the CG under PROG --> FUEL PRED 🙂

Should be with next weeks patch, if all according to plan 🙂

Should be fixed in 1.0.2 If it still happens, please report back!

Should be fixed with 1.0.2 Please test again and report back!

Should be fixed with 1.0.2 Please try again and report back 🙂

Mmmh.. To me that shounds like a control bind issue. Could you please remove the Hotas/Yoke/Whatever you have, press the TOGA button and see if the engines also roll back?

If you have any other problems, please let me know!

I think this was fixed in 1.0.2, could you check again please?

Thanks, will take a look 🙂

Fixed with 1.0.2 🙂

There isn't, no. But we are working on fixing the issue where the rudder overtakes the nose wheel steering, should hopefully be in 1.0.3

The update is still in the works I'm afraid, sorry for the inconveniece 😕

Yep, exactly, user waypoints. I dont have the chart around currently, but it would be in this general format: Place/Bearing/Distance so like CH/180/05 for a waypoint 5nm in a 180° direction from CH. As for the arrival.. That is also probably due to the navdata mod I'm afraid. We currently only support the insim navdata and everything other than that is "use at your own risk"

This can only be "fixed" if we completly rewrite the FMC to accept Navigraph navdata. When or if we do this, I cant say or promise.

Heya! No, that command shouldn't be used like that. Try using the STEER AXIS command instead 🙂

That sounds like a GSX issue. Did you exclude our PHNL in the GSX options?

Cheers, will fix them 🙂

The IGS13 approach is coded as a GPS approach, which the A300 can't fly and is therefore omitted. When I flew that approach I built the waypoints myself, as they are all in relation to the CH VOR and are easy to do with PBDs 😄

It sounds like another Navigraph incompability with the default navdata (that we use) Please try uninstalling Navigraph navdata and see if the issue persists.