• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Default autopilot - stupid questionn really

DragonflightDesign

DragonflightDesign

Resource contributor
Messages
1,371
Country
northernireland
In the aircraft.cfg file I have
Code: 
[autopilot]
autopilot_available= 1
but
Code: 
if(ap_active.var_value.n==0)trigger_key_event(KEY_AUTOPILOT_ON, 0);
has no effect. Have I missed something or am I flooding the sim and it's ignoring the command?
 
Remove the space after the =. Perhaps it's an issue. Also, I would recommend send_key_event instead of trigger_key_event. It is processed immediately and trigger is queued.
 
Forum problems mean we lost a post, but I did eventually find the very surprising answer to this.
Code: 
MODULE_VAR ap_available =  { AIRCRAFT_AUTOPILOT_AVAILABLE };
MODULE_VAR ap_active = { AUTOPILOT_ACTIVE };
MODULE_VAR ap_wingleveler = { AUTOPILOT_WING_LEVELER };
All three of these returned zero (not active/not available) when the corresponding SimConnect calls returned one (active/available). SimConnect was right and the module_vars were wrong. I have no explanation, especially as for testing those three KEY_EVENTS_ were only ever turned on and never turned off.
 
I did.



Not. Dammit 😖😖 I knew it had to be something simple. I have one gauge that updates everything once per cycle but the autopilot was not on its call list for this project :banghead::banghead::banghead: (sigh) see thread title...
 
You must log in or register to reply here.
Back
Top