I bet I left the altitude control swith on

BTW I belong to a good Milsim group sent your link straight away and a few have purchased already, appreciate your work

GARUDA wrote on Apr 21^st, 2024 at 4:38pm:


The "AFF" position is the approach position for the AP. So on the dash you should be set to "VOR/ILS1", the flight director mode on "Auto", and on the pedestal the radio coordinator selector set to "AFF".

However I'm not confident it's working as it should. The "BLUE LEFT LOC" switch should make it follow the localizer but it doesn't it put the plan into wings level mode. The only mode I've found that will follow radio signals is the "RANGE/LOC" mode but the HSI direction resets every few minutes messing that up.

Maybe I'm doing something wrong too - but I don't think I am?

Flying this afternoon has been a lot of fun. Seems to be a really solid first release here. Can't wait to see the improvements that are surely coming!

One major thing to report is the custom autopilot while working normally and well does this odd thing where suddent it will reset the course direction every couple of minutes. For instance I would supposed to be following and had set a course for 73 degree to the VOR station I was tracking. Then suddenly the course reset to 351 degree for no reason - which the plane then turns and follows.

Everytime it would do it, I would fix it - and within a few minutes it would repeat the same thing over and over. I tried toggling the autopilot on/off and reseting it. Didn't seem to clear it up at all.

Off-Topic replies have been moved to this Topic.

appreciate you double checking and guiding us CS <3

@CaptnThud thats why i put only do it if you understand. but sure it works fine, but for whatever reason when you CTRL+E from cold start the AP soon as you kick it on without touching anything else, sends it into a right turn that ends up in an overbank turn straight into the ground 99/100 times. i know the AP works fine, just not when cold dark starting via ctrl+e as mentioned.

yep. the LVARS from the runway.flt moved to the apron.flt seemed to have solved the AP issue when starting via CTRL+E. 100% sure something isnt turning on. but yea i second theres a little funky things going on in the fuel system, when you do a ctrl+e start all crossfeeds open and when you try to take off with them all open, it bogs the engine down and causes the props to start going opposite of eachother rather then work in tandem and then you gotta resync and shut the crossfeeds off. these are the only bugs ive noticed (the ctrl+e AP start issue and the crossfeeds being open causing engine rpm to die)