AutoflightSystem

[HHS81]

Use the one from Pattens Citation X, but:

• remove Autothrottle, as the Dornier 328 TP and Jet never had any Autothrottle. The needed throttle settings are indicated by bugs on the Torque indicator and driven by the FlightManagementComputer

[xcvb85]

To deactivate autothrottle I would just create a custom autopilot gui dialog. I can do this if you want (I already did this for tu134a which has a very basic autothrottle).

[HHS81]

The Cessna Citation X does have an custom autopilot dialog. Just the whole autoflight system works a bit different on the Dornier 328s in RL. Maybe even on the Citation X in RL as well. Together with the work on the flightdeck I'm remapping the autoflight panel, and with that I will install the autoflight system.

The last two weeks had been very busy in RL and Job, sorry for my absence.
Btw.: Happy new year!

[xcvb85]

Happy new year! In the meantime I did my changes on the Flightdeck11.ac (see pull request). Please let me know if you like the new screen textures. If not I don't have a problem to revert them. For the PFD I need to activate the buttons with the circle and the rhombus symbols but this will just affect the flightdeck.xml file.
The custom autopilot dialog from the Citation X seems to be a good starting point. I wonder why you also created custom autopilot system. The settings for the ailerons are very aggressive and the plane tends to overreact. Maybe we just use the default behaviour by not defining any autopilot system at all.

[HHS81]

I wonder why you also created custom autopilot system. The settings for the ailerons are very aggressive and the plane tends to overreact. Maybe we just use the default behaviour by not defining any autopilot system at all.

When I started the aircraft, there was only Syds original version, and its autoflight system was realistic with its functions, but had bugs (like problems catching glideslope). I added then some changes to get the engine parameters right: It includes functions which calculate fuel consumes in different units and remaining distance, which helps me a lot. So this custom autopilot system is only for testing and developement process. That's why the issue#38 to remind me to change it.
Actually there is already an improved engine file in the pipeline, but not yet ready for release or push, since the torque values are not yet right, and therefor I need this system.

[xcvb85]

Is it ok for you if I care about this? I already got flight director working.

[xcvb85]

I created a new branch Issue38. Flying by flight director is not perfect yet but already fun. The hard part is that you need a further controller cascade to be able to cut the connections from the autopilot to the flight control surfaces.