Cessna 337 Nav needle not working

[SurferTim]

With the FGAddon code, the course line will only move 1 line left or right indicating full deflection on a VOR station.
Is it not moving, or only moving one line left and right? The VOR deflection will move only 1/5 of the localizer deflection.

When I change frequencies, the course indicator gets disoriented.

[polly]

I'm not seeing the same:


That's with the plane loaded from fgaddon at OP's first post, located --airport=EGPC (Wick ) . The VOR deviation looks to be full scale.
I don't know if the release level is affecting this, I'm running 2020-4 at the moment.

[wkitty42]

I don't know if the release level is affecting this, I'm running 2020-4 at the moment.

that may very well be the difference... the power code in next got some attention a few months ago... ISTR that a few craft were also updated... i'm not sure which SVN branch those updates were put in, though... so it is possible that there're at least two versions of the craft in question being looked at for this problem...

[wlbragg]

I'm not sure what it means and I didn't dig into the code very far but in OP's posted image it shows power-btn = false and also operable = false. Not so with my flight using the same parameters as the OP's. The radio code has no power-btn logic that I saw. Also in the prop tree, changing power-btn to false in my test did not shut down the radio. But it did set operable to false.

@cookf try setting power-btn to true.

[polly]

I don't think there's been any update to the power circuitry in e.g the model's Nasal or Instrumentation.xml.

It may well be that a workaround for the power getting messed up was back-ported to a recent version of 2020-3 ( because a ticket was raised for this issue ) which would explain why neither 'next' nor '2020-3' show the issue here, while OP's 2020-3 is an earlier version.

The numeric digits for the KI155 appear to depend on:

Code: Select all

   <condition>
      <property alias="../../../params/comm-serviceable"/>
      <property alias="../../../params/nav-serviceable"/>
      <property alias="../../../params/power"/>
      <property alias="../../../params/nav-electrical"/>
   </condition>

<params>
   <comm-serviceable>instrumentation/comm[0]/serviceable</comm-serviceable>
   <nav-serviceable>instrumentation/nav[0]/serviceable</nav-serviceable>
   <power>instrumentation/comm[0]/power-btn</power>




Does that mean the property alant mentioned, if not set, will disable the NAV while the power-btn has allow the Nav radio digits to illuminate ?

[wlbragg]

I pulled 2019.1 337 and it does not work same as OP until you set the power-btn to true for whatever nav radio your using. So that is the issue.

Easiest is to add
instrumentation/nav/power-btn = 1;
instrumentation/nav[1]/power-btn = 1;
to the code.

Or for OP to download the 2020.3 version. It should work fine.

[cookf]

I finally got it working. Auto start made no change. After tuning nav1 and nav2 to 2 VOR beacons, I went to debug - browse internal properties/instrumentation/nav/ and ctrl + click to toggle power. Values immediately change. Repeat for nav2.
Very odd that I appear to have this and it works for others.
Now flying over Iceland from VOR to VOR. Iceland = country, not Iceland = Uk frozen stuff shop.

[wlbragg]

Very odd that I appear to have this and it works for others.

No, not at all. You need a more recent version of the aircraft as I suggested in my prior post.
2020.3 version

I think the aircraft you are using reads the following in the .set file.

Code: Select all

<aircraft-version>v20170106</aircraft-version>

No minimum tag.

The one you want should read...

Code: Select all

<aircraft-version>v20170106</aircraft-version>
<minimum-fg-version>2018.2.0</minimum-fg-version>

Kind of funny the aircraft versions are the same and were never updated.

[SurferTim]

If polly's version is ok, then it must be a version problem. I'm on FG2020.4.0 compiled version.

[wlbragg]

Am I missing something? I think it is the version of aircraft, not of FSFG.

[SurferTim]

I got mine from FGAddon. I believe FG2020.4.0 uses a different set of aircraft files.
How did polly get the one that works?

[wlbragg]

My FGFS is next 2020.4 and the 337's that work are from fgaddon next down to 2020.3.
Where the aircraft stops working is fgaddon 2019.1.

[SurferTim]

It's working with most VORs. I was testing with Crestview VOR 115.9, and apparently it is one that doesn't work.
Inverness works. St. Maarten works. ??

[polly]

I do
svn checkout http://svn.code.sf.net/p/flightgear/fga ... rcraft/xxx
for Aircraft and git pull - build from the source trees. " Is that wrong " ?

[wlbragg]

No, not wrong. I think that your getting your aircraft from "trunk" root which is the cutting edge aircraft.