by Octal450 » Wed Aug 03, 2016 2:41 am
@tikibar
It is systems.nas line 1183. setprop() value is not string or number. I haven't pushed anything yet, debugging some stuff.
I'll do it before I go to bed tonight
The reason I'm using it is because The other AP keeps throwing me into the ground for some reason. It's just a concept, which is why I'm doing it on a separate branch. I plan to develop me AP to the level of the current one, or above.
The AP is very complex and you've done a good job! But I don't know why he goes into the ground?
You are welcome to use my FLCH controller, it works very well on 16+ aircrafts now. (I tested in the MD-11, it works lovely). I also limited clb thrust to 0.9 throttle for now, I plan to put it on a property thing, so climb limits can work.
I will install my flch system on the MD-11 with your AP, it's shouldn't be too hard, since all I need is to modify the enable prop, and add some nasal code to AFDS.nas.
Suggestion: Can you make it switch from clb thrust to alt hold 500ft below the target altitude? That is how the real one levels off. It always overruns right now. With FLCH, the climb rates/desc rates can be quite high at times. I don't understand some of that nasal code (but I'm learning!) so I'm not sure I know how to do that. Also, if it misses the altitude, it cannot go back into CLB THRUST. MD-11 stays in altitude capture from 500ft away from target, until another alt is set and the system is set into FLCH again. If it switches back into FLCH, then the throttle will do some funny things!
Best,
Josh