• 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.

FS2004 GPS driving HDG?

lmhariano

lmhariano

Messages
36
Country
argentina
Is it there a way to read the heading commanded by the GPS and sending it to the HDG bug instead of the NAV mode, so that the HDG bug would be driven by the FS2004 GPS? This for enabling GPS use in a panel that forcedly disabled it (I mean, the NAV/GPS switch rebounds when toggled).
 
That is the way it reads from the GPS. The NAV/GPS switch. So if it rebounds then something in the coding must be forcing it to stay on NAV mode. Maybe bad coding.
 
To answer your question it would probably be possible, but it would involve far more gauge coding than fixing the NAV/GPS switch problem...
 
I don't know if FS9 supports these variables and I have not tested this, but this could help:

Code: 
<Gauge>
<Element>
<Select>
<Value>
(A:GPS IS ACTIVE FLIGHT PLAN, bool) (A:GPS IS ARRIVED, bool) ! and
if{ (A:GPS COURSE TO STEER, radians) 57.2 * (A:AUTOPILOT HEADING LOCK DIR, degrees) !=
      if{ (A:GPS COURSE TO STEER, radians) 57.2 * (>K:HEADING_BUG_SET) }
}
</Value>
</Select>
</Element>
</Gauge>
 
Tom/Delivery Guy, thanks a lot for your answer. Actually, the panel in question was the HJG 727 one; this is the only "but" I had of their otherwise excellent panels. Somehow, when HJG added their INS, the GPS use was disabled and that's what prevents the NAV/GPS switch to operate.

Bjoern, thank you thank you thank you very much! I added your code lines into a gauge I did for addressing this. I've just finished a flight with the modified 727, works beautifully.
 
lmhariano said:
Bjoern, thank you thank you thank you very much! I added your code lines into a gauge I did for addressing this. I've just finished a flight with the modified 727, works beautifully.
Click to expand...

Ha, excellent! As I've said, I didn't test it at all.
 
You must log in or register to reply here.
Back
Top