search

c172p-team / c172p

A high detailed version of the Cessna 172P aircraft for FlightGear
GNU General Public License v2.0
82 stars 43 forks source link

Material animation and effects definitions load order must come after knob animations #1410

Closed wlbragg closed 1 year ago

wlbragg commented 1 year ago

See https://github.com/c172p-team/c172p/issues/1210#issuecomment-1402789278

Requires rearranging the affected object knob animations to be loaded prior to any affect or material animation.

amalon commented 5 days ago • This appears to be a simgear bug, being discussed on the flightgear-devel mailing list ("SGPickAnimation applying multiple times in the presence of SGMaterialAnimation"), where animations are applied multiple times to objects which appear multiple times in the scene graph, which happens after an effect node.

It can be worked around by putting the animation node after the effect node in the XML (and putting the factors/ranges back to correct values). I'm in the process of adding a warning to simgear for when an animation is applied multiple times, to encourage it to be worked around (with a view to possibly fixing the behavior in the future), and to spot new cases.

I'd appreciate feedback on how practical this sort of workaround is in the case of the c172p. It seems that animation nodes in c172-common.xml would have to go before effect nodes in Interior/Panel/c172p-panel/c172p.xml, so it'd presumably require some rearranging. If this is a giant pain, would you prefer a flag somewhere (perhaps at an XML file level, or individual animation node level) to allow you to explicitly state that you want the corrected behaviour (and to silence the warning), at the cost of losing compatibility with versions of flightgear prior to the introduction of the flag?

This is the output of my current warnings for c172p (not yet pushed into simgear):

4.59 [ALRT]:general Deprecation Alert: Since 2013, knob & slider animations are duplicated if they already take part in an effect, 4.59 [ALRT]:general resulting in exaggerated motion. This incorrect behaviour will be removed in a future version, which will reduce 4.59 [ALRT]:general the motion of these objects. Aircraft can work around the issue and silence this warning by rearranging the XML 4.59 [ALRT]:general so that the animation node comes before the effect node. You may need to double the animation factor or 4.59 [ALRT]:general property-adjust ranges to match the current range of motion. The affected object names will be logged below. 4.59 [ALRT]:general Warning: Duplication of knob animation on object "AdjustKnob" is deprecated behaviour (see above). 4.66 [ALRT]:general Warning: Duplication of knob animation on object "disk" is deprecated behaviour (see above). 4.77 [ALRT]:general Warning: Duplication of knob animation on object "Volume" is deprecated behaviour (see above). 4.77 [ALRT]:general Warning: Duplication of knob animation on object "FRQInner" is deprecated behaviour (see above). 4.77 [ALRT]:general Warning: Duplication of knob animation on object "FRQOuter" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "toggle-stbybatt" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "knob-swcb" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "knob-stbyind" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "knob-pedestal" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "knob-avionics" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "TrimWheel-fg1000" is deprecated behaviour (see above). 5.80 [ALRT]:general Warning: Duplication of knob animation on object "RudderTrimKnob-fg1000" is deprecated behaviour (see above). 6.22 [ALRT]:general Warning: Duplication of knob animation on object "AdjustKnob" is deprecated behaviour (see above). 6.24 [ALRT]:general Warning: Duplication of knob animation on object "disk" is deprecated behaviour (see above). 6.48 [ALRT]:general Warning: Duplication of knob animation on object "Hdg-Knob" is deprecated behaviour (see above). 6.48 [ALRT]:general Warning: Duplication of knob animation on object "OBS-Knob" is deprecated behaviour (see above). 6.55 [ALRT]:general Warning: Duplication of knob animation on object "disk" is deprecated behaviour (see above). 6.61 [ALRT]:general Warning: Duplication of knob animation on object "disk" is deprecated behaviour (see above). 6.65 [ALRT]:general Warning: Duplication of knob animation on object "HDGSelector" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "COMvol" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "COMknobKHZ" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "COMknobMHZ" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "NAVvol" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "NAVknobKHZ" is deprecated behaviour (see above). 6.68 [ALRT]:general Warning: Duplication of knob animation on object "NAVknobMHZ" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "COMvol" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "COMknobKHZ" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "COMknobMHZ" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "NAVvol" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "NAVknobKHZ" is deprecated behaviour (see above). 6.70 [ALRT]:general Warning: Duplication of knob animation on object "NAVknobMHZ" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "AUTO" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "COM1" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "COM2" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "NAV1" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "NAV2" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "ADF" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "DME" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "MKR" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "SENS" is deprecated behaviour (see above). 6.73 [ALRT]:general Warning: Duplication of knob animation on object "Knob" is deprecated behaviour (see above). 6.74 [ALRT]:general Warning: Duplication of knob animation on object "Volume" is deprecated behaviour (see above). 6.74 [ALRT]:general Warning: Duplication of knob animation on object "FRQInner" is deprecated behaviour (see above). 6.74 [ALRT]:general Warning: Duplication of knob animation on object "FRQOuter" is deprecated behaviour (see above). 7.26 [ALRT]:general Warning: Duplication of knob animation on object "TrimWheel" is deprecated behaviour (see above). 7.26 [ALRT]:general Warning: Duplication of knob animation on object "RudderTrimKnob" is deprecated behaviour (see above). 7.26 [ALRT]:general Warning: Duplication of knob animation on object "panel-light-knob" is deprecated behaviour (see above). 7.26 [ALRT]:general Warning: Duplication of knob animation on object "radio-light-knob" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorleft-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorleft" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorright-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorright" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorrodleft-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorleft-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorrodleft" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorleft" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorrodright-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorright-fg1000" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorrodright" is deprecated behaviour (see above). 8.35 [ALRT]:general Warning: Duplication of knob animation on object "visorright" is deprecated behaviour (see above).

wlbragg commented 1 year ago

@dany93 this is finished, Unfortunately there are a lot of files and objects this touched. Fortunately it was really straightforward to fix. All that was required was to change the load order of effects, material animation and knob animations. That require all rotation factors of the affected objects to be doubled. The check is to make sure all affected instruments still scroll as they used to.

The following instruments and interior aircraft objects are what was affected...

c172p

visorrodleft visorleft visorrodright visorright TrimWheel RudderTrimKnob panel-light-knob radio-light-knob Hdg-Knob OBS-Knob

c172sp

visorrodleft-fg1000 visorleft-fg1000 visorrodright-fg1000 visorright-fg1000 toggle-stbybatt knob-swcb knob-stbyind knob-pedestal knob-avionics TrimWheel-fg1000 RudderTrimKnob-fg1000

Multiple variants

AI

AdjustKnob

KR87-ADF

Volume HDGSelector FRQInner FRQOuter

KX165

Volume COMvol COMknobKHZ COMknobMHZ NAVvol NAVknobKHZ NAVknobMHZ

KMA20

Knob AUTO COM1 COM2 NAV1 NAV2 ADF DME MKR SENS

ALT and VOR

disk

EGT

Knob

dany93 commented 1 year ago

@wlbragg For the c172p, I've found that everything works (except for the Horizon Offset, but I guess this is another subject). I hope having understood the object names correctly.

For the c172sp (with FG1000-KAP140), I have an issue, possibly due to my absence of knowledge of the instrument that I've never used. Almost no animation works, except for the NAV1 NAV2 and VOL. Particularly, the HDG knob changes the property values, but it gives no animation of the green bug. The ALT knob seems doing nothing. And nothing changes in flight (no airspeed, no Alt indication). toggle-stbybatt: the green test light behavior is weird.

Do I need a more recent compilation ? Mine is from 19 oct 2022.

Here's where I am: 1 = it works 0 = does not work

  c172p c172sp (FG1000-KAP140)
c172p    
     
visorrodleft 1  
visorleft 1  
visorrodright 1  
visorright 1  
TrimWheel 1  
RudderTrimKnob 1  
panel-light-knob 1  
radio-light-knob 1  
Hdg-Knob 1  
OBS-Knob 1  
     
c172sp    
     
visorrodleft-fg1000   1
visorleft-fg1000   1
visorrodright-fg1000   1
visorright-fg1000   1
toggle-stbybatt   Toggle=1, green test light ?
knob-swcb   1
knob-stbyind   1
knob-pedestal   1
knob-avionics   1
TrimWheel-fg1000   1
RudderTrimKnob-fg1000   1
     
Multiple variants    
     
AI 1 0
     
AdjustKnob    
     
KR87-ADF    
     
Volume 1 1
HDGSelector 1 ?
FRQInner 1 1
FRQOuter 1 1
     
KX165    
     
Volume    
COMvol 1  
COMknobKHZ 1  
COMknobMHZ 1  
NAVvol 1  
NAVknobKHZ 1  
NAVknobMHZ 1  
     
KMA20    
     
Knob    
AUTO 1  
COM1 1  
COM2 1  
NAV1 1  
NAV2 1  
ADF 1  
DME 1  
MKR 1  
SENS 1  
     
ALT and VOR    
     
disk 1  
     
EGT 1  
     
Knob 1  
     
     
Horizon Offset ? No animation No animation
FG1000   No indication, no HDG bug anim, No Alt change

wlbragg commented 1 year ago

@dany93

Well, interesting. The Horizon Offset in the c172p works fine for me, but the one in the c172sp does not adjust, the actual AI works fine in both. What is weird is it is the exact same code for either the c172p or the c172sp. This one is going to take me some time to figure out but the Horizon Offset in the c172sp didn't work before these latest changes so it isn't caused by the recent work.

Do I need a more recent compilation ? Mine is from 19 oct 2022.

I wouldn't think so, but maybe. Beings nothing is working in the c172sp I don't think this is the current work, you may have something wrong with your setup. Nothing on the fg1000 PFD/MFD instruments changed with this commit. Keep in mind the heading bug and the altitude setting change on the fg1000 PFD/MFD only happen by using the knobs on the fg1000 PFD/MFD. The altitude setting on the round gauge on the panel only controls that gauge. It does not interact with the FG1000 PFD/MFD. So again, I think your setup must have issues unrelated to the new commit.

The toggle-stbybatt electrical logic in the fg1000 is not finished, quite honestly I don't remember exactly where I left off with it. So I am not concerned about it either, at the moment. The changes I made, even though that switch is a knob animation, really isn't going to be an issue so you can ignore that behavior for now.

In the c172sp mainly it is the... Alt (round gauge on the panel, not the altitude setting on the fg1000 PFD/MFD) AI Heading Offset knob (which isn't working for me either, not related to the current commit). knob-swcb knob-stbyind knob-pedestal knob-avionics These 4 knobs are all left of the fg1000 PFD/MFD and control all the interior lighting. They are all affected knob animations. If they control the lights correctly then they are OK. They work fine on my setup.

So all in all I think we're good as far as the new commit is concerned. I was sure that the work I did would not "break" anything, unless I totally messed up code. The worst case would have been it changed the ratio of knob rotation to gauge needle deflections for the various gauges. Or in the case of the visors, they would not move in the same range as they used to. So that is mostly what to watch for, barring catastrophic failure.

Thank you for testing. Let me see if I can figure out what is wrong with the AI Horizontal Offset in the c172sp before we merge this.

Maybe you can figure out what is wrong with your c172sp, either rebuild and pull new. Or you might want to delete any saved aircraft data for the fg1000 variant, maybe it is causing issues if you are between changes. I could see the electrical really messing with it if you have a saved data version different from the current version because that is the last major change to the fg1000 variants. It was a major rework of the electrical system if I remember correctly. Maybe check the logs related to the ALT (round gauge) not working and the fg1000 PFD/MFD not working.

dany93 commented 1 year ago

@wlbragg You were right, but not still solved. By deleting my c172p*.xml files under .fgfs/aircraft-data, the FG1000 works, but only once. At the following time, it fails again.

The difference when it fails is in these lines, added:

between (17.37 [INFO]:nasal      Traffic pins off )
   12.32 [INFO]:nasal      #  FG1000  #
   12.32 [INFO]:nasal      ############

   17.37 [INFO]:nasal      Traffic pins off
   17.38 [INFO]:nasal      string index 3 out of bounds (size: 3)
   17.38 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas
   17.38 [INFO]:nasal      956
   17.38 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstrumentsController.nas
   17.38 [INFO]:nasal      478
   17.38 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstrumentsController.nas
   17.38 [INFO]:nasal      540
   17.38 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Nasal/emesary.nas
   17.38 [INFO]:nasal      179
   17.38 [ALRT]:nasal      Recipient PFDInstrumentsController_PFD has been removed from transmitter (GlobalTransmitter) because of the above error
and (17.38 [ALRT]:flight     Failed to save initial FDM property state)

I do not have this issue with the Cessna 182T.

[EDIT] Also see https://github.com/c172p-team/c172p/issues/1410#issuecomment-1419578847

dany93 commented 1 year ago

@wlbragg wrote

Maybe check the logs related to the ALT (round gauge)

The Airspeed and ALTitude Indicators (round gauges) work correctly. The animations fail only, like the Artificial Horizon one, on the FG1000 display.

AI (Artificial Horizon, old round gauge, blue and black): In master and in the Issue-1410 branches. The vertical animation (pitch indication) does not work with the FG1000 (at least KAP140) version. Its position does not change in flight, and the knob (Horizon Offset) has no effect. The Roll indication works. It works correctly with the c172p (without FG1000) version. ==> no vertical animation, not due to your last changes in this branch, but related to FG1000 version.

The FG1000 failure is not due to your recent changes in this branch. I have this same symptoms in master, at least with the current FG1000-KAP140 version. The FG1000 works once, only after having deleted the .fgfs/aircraft-data/c172p-fg1000-kap.xml file. Same error messages.

(On Linux Mint 20.3, up-to-date)

wlbragg commented 1 year ago

The FG1000 works once, only after having deleted the .fgfs/aircraft-data/c172p-fg1000-kap.xml file. Same error messages.

I'm going to have to consult with Stuart on this. It's beyond my scope. If I think of anything you can try to resolve this I will let you know. I don't know how many versions in git there might be for the 172p-fg1000, maybe try rolling it back a few commits and see if it ever worked for you. If you could find a failure point it would be helpful.

I may know what is wrong with the AI (round gauge) in the c172sp. I'll work on it sometime over the weekend.

Thanks for all your help.

dany93 commented 1 year ago

I possibly can paste the content of my .fgfs/aircraft-data/c172p-fg1000-kap.xml (the file which, if present, prevents the FG1000 from working at the following session). But it makes about 300 lines.

Currently, I think the best is the log lines that I posted above.

dany93 commented 1 year ago

@wlbragg wrote

maybe try rolling it back a few commits and see if it ever worked for you

I triedf74cf868 Begin fg1000 variant (2020-10-13). Same issue:

Something I'm wondering: you do not have this issue. Is it under Linux or Windows?

I'm under Linux Mint 20.3, PLIB a542b8a Wed, 4 Oct 2017 17:33:51 +0200 SimGear 0d3ec0c1 Mon, 17 Oct 2022 17:58:48 +0200 FGData 8cbbbcdc8 Tue, 18 Oct 2022 10:08:59 +0100 FlightGear 64ae52438 Tue, 11 Oct 2022 22:08:29 +0100

Reminder: I do not have this issue with the Cessna 182T.

wlbragg commented 1 year ago

I'm on Windows, but I can boot into Linux and try it. I'll try it and get back to you.

I looked at my saved data for the fg1000-kap, it was also over 300 lines. If you want to try it or compare it, here it is.

c172p-fg1000-kap.xml

<?xml version="1.0"?>

<PropertyList>
  <sim>
    <model>
      <hitch>
      </hitch>
      <c172p>
        <save-state type="bool">false</save-state>
        <ruddertrim-visible type="bool">false</ruddertrim-visible>
        <immat-on-panel type="bool">false</immat-on-panel>
      </c172p>
      <walker n="1">
        <animate>
          <enabled-triggers type="bool">true</enabled-triggers>
          <list>
            <sequence>
              <trigger-upon type="string">Standing</trigger-upon>
            </sequence>
            <sequence n="8">
              <trigger-upon type="string">Disabled</trigger-upon>
            </sequence>
          </list>
        </animate>
      </walker>
      <livery>
        <name type="string">4X-CHV (HD livery)</name>
      </livery>
    </model>
    <gui>
      <dialogs>
        <aircraft>
        </aircraft>
        <aicargo-dialog>
          <longline type="bool">true</longline>
          <connection type="bool">false</connection>
        </aicargo-dialog>
        <rope-dialog>
          <alt-origin type="bool">false</alt-origin>
          <settings>
            <x-pos type="double">2.2</x-pos>
            <y-pos type="double">0</y-pos>
            <z-pos type="double">0</z-pos>
            <offset type="double">2.86</offset>
            <diameter type="double">1</diameter>
            <wincharm type="int">0</wincharm>
            <loadpoint type="int">0</loadpoint>
          </settings>
        </rope-dialog>
      </dialogs>
    </gui>
    <cargo>
      <setselected type="string">1</setselected>
      <rope>
        <segments-reeled-in type="int">0</segments-reeled-in>
      </rope>
    </cargo>
    <current-view>
      <user>
        <x-offset-m type="double">-0.21</x-offset-m>
        <y-offset-m type="double">0.238</y-offset-m>
        <z-offset-m type="double">0.36</z-offset-m>
        <pitch-offset-deg type="double">-13.88571429</pitch-offset-deg>
        <default-field-of-view-deg type="double">76.21946642</default-field-of-view-deg>
      </user>
    </current-view>
    <walker>
    </walker>
    <time>
      <hobbs>
        <engine type="double">0</engine>
        <engine n="1" type="double">531.1000001</engine>
      </hobbs>
    </time>
    <view n="110">
      <enabled type="bool">false</enabled>
    </view>
    <view n="111">
      <enabled type="bool">false</enabled>
    </view>
  </sim>
  <fdm>
    <jsbsim>
      <engine>
        <damage-level type="double">0</damage-level>
      </engine>
      <settings>
        <damage type="bool">true</damage>
        <damage-flag type="bool">false</damage-flag>
      </settings>
      <running type="bool">false</running>
      <fuel>
        <tank type="bool">true</tank>
      </fuel>
    </jsbsim>
  </fdm>
  <environment>
    <aircraft-effects>
      <cabin-heat-set type="double">0</cabin-heat-set>
      <cabin-air-set type="double">0</cabin-air-set>
    </aircraft-effects>
  </environment>
  <controls>
    <climate-control>
      <overhead-vent-front-left type="double">0</overhead-vent-front-left>
      <overhead-vent-front-right type="double">0</overhead-vent-front-right>
    </climate-control>
    <mooring>
      <automatic type="bool">false</automatic>
    </mooring>
    <lighting>
      <beacon type="bool">false</beacon>
      <landing-lights type="bool">false</landing-lights>
      <nav-lights type="bool">false</nav-lights>
      <strobe type="bool">false</strobe>
      <taxi-light type="bool">false</taxi-light>
      <gearled type="bool">false</gearled>
      <instruments-norm type="double">0</instruments-norm>
      <radio-norm type="double">0</radio-norm>
      <dome-white-norm type="double">1</dome-white-norm>
    </lighting>
    <switches>
      <magnetos type="int">0</magnetos>
      <master-bat type="bool">false</master-bat>
      <master-alt type="bool">false</master-alt>
      <master-avionics type="bool">false</master-avionics>
      <dome-red type="int">0</dome-red>
      <dome-white type="bool">false</dome-white>
    </switches>
    <anti-ice>
      <engine>
        <carb-heat type="bool">false</carb-heat>
      </engine>
      <pitot-heat type="bool">false</pitot-heat>
    </anti-ice>
    <gear>
      <brake-parking type="double">1</brake-parking>
    </gear>
    <flight>
      <flaps type="double">0</flaps>
      <elevator-trim type="double">0</elevator-trim>
    </flight>
    <engines>
      <current-engine>
        <throttle type="double">0</throttle>
        <mixture type="double">0</mixture>
      </current-engine>
      <engine>
        <primer-lever type="bool">false</primer-lever>
      </engine>
    </engines>
    <circuit-breakers>
      <autopilot type="bool">true</autopilot>
      <bcnlt type="bool">true</bcnlt>
      <flaps type="bool">true</flaps>
      <instr type="bool">true</instr>
      <intlt type="bool">true</intlt>
      <landing type="bool">true</landing>
      <master type="bool">true</master>
      <navlt type="bool">true</navlt>
      <pitot-heat type="bool">true</pitot-heat>
      <radio1 type="bool">true</radio1>
      <radio2 type="bool">true</radio2>
      <radio3 type="bool">true</radio3>
      <radio4 type="bool">true</radio4>
      <radio5 type="bool">true</radio5>
      <strobe type="bool">true</strobe>
      <turn-coordinator type="bool">true</turn-coordinator>
    </circuit-breakers>
  </controls>
  <consumables>
    <fuel>
      <contamination_allowed type="bool">false</contamination_allowed>
      <tank>
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="1">
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="2">
        <level-norm type="double">0.249873366</level-norm>
        <selected type="bool">true</selected>
      </tank>
      <tank n="3">
        <level-norm type="double">0.249873366</level-norm>
        <selected type="bool">true</selected>
      </tank>
    </fuel>
  </consumables>
  <instrumentation>
    <save-switches-state type="bool">false</save-switches-state>
    <dme>
      <power-btn type="bool">true</power-btn>
      <switch-min-kts type="bool">true</switch-min-kts>
      <switch-position type="int">2</switch-position>
      <frequencies>
        <source type="string">/instrumentation/nav[0]/frequencies/selected-mhz</source>
        <selected-mhz type="double">112</selected-mhz>
      </frequencies>
    </dme>
    <kma20>
      <test type="int">0</test>
      <auto type="int">1</auto>
      <com1 type="int">0</com1>
      <com2 type="int">0</com2>
      <nav1 type="int">0</nav1>
      <nav2 type="int">0</nav2>
      <adf type="int">0</adf>
      <dme type="int">0</dme>
      <mkr type="int">-1</mkr>
      <sens type="int">0</sens>
      <knob type="int">-1</knob>
    </kma20>
    <comm>
      <power-btn type="double">0</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">118.3</selected-mhz>
        <standby-mhz type="double">119.3</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <channel-mode-selector type="bool">true</channel-mode-selector>
    </comm>
    <nav>
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.5</volume>
      <frequencies>
        <selected-mhz type="double">112</selected-mhz>
        <standby-mhz type="double">108.5</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">284</selected-deg>
      </radials>
    </nav>
    <comm n="1">
      <power-btn type="bool">true</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">128.3</selected-mhz>
        <standby-mhz type="double">121.9</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
    </comm>
    <nav n="1">
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.7</volume>
      <frequencies>
        <selected-mhz type="double">112.4</selected-mhz>
        <standby-mhz type="double">113.6</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">326</selected-deg>
      </radials>
    </nav>
    <altimeter>
      <setting-inhg type="double">30.60179306</setting-inhg>
    </altimeter>
    <attitude-indicator>
      <horizon-offset-deg type="double">-5.6</horizon-offset-deg>
    </attitude-indicator>
    <heading-indicator>
      <offset-deg type="double">-2.338620194</offset-deg>
    </heading-indicator>
    <adf>
      <rotation-deg type="double">0</rotation-deg>
      <frequencies>
        <dial-1-khz type="int">0</dial-1-khz>
        <dial-100-khz type="int">0</dial-100-khz>
        <standby-khz type="double">200</standby-khz>
        <selected-khz type="double">200</selected-khz>
      </frequencies>
      <adf-btn type="bool">false</adf-btn>
      <bfo-btn type="bool">false</bfo-btn>
      <volume-norm type="double">0.5</volume-norm>
      <power-btn type="bool">true</power-btn>
    </adf>
    <transponder>
      <inputs>
        <knob-mode type="int">4</knob-mode>
        <ident-btn type="bool">false</ident-btn>
        <digit type="int">0</digit>
        <digit n="1" type="int">0</digit>
        <digit n="2" type="int">2</digit>
        <digit n="3" type="int">1</digit>
      </inputs>
    </transponder>
    <clock>
      <lc2>
        <flight-meter-sec type="double">0</flight-meter-sec>
      </lc2>
    </clock>
  </instrumentation>
  <systems>
    <electrical>
      <save-battery-charge type="bool">false</save-battery-charge>
      <battery-charge-percent>
        <a type="double">1</a>
        <b type="double">1</b>
      </battery-charge-percent>
    </electrical>
  </systems>
  <engines>
    <active-engine>
      <complex-engine-procedures type="bool">false</complex-engine-procedures>
    </active-engine>
    <engine>
    </engine>
  </engines>
  <autopilot>
    <settings>
      <heading-bug-deg type="string">169</heading-bug-deg>
    </settings>
  </autopilot>
</PropertyList>
dany93 commented 1 year ago

There are differences, due to our personal configurations. But I see nothing obvious which could give this issue.

If you wish, I can post mine here. Just tell me.

dany93 commented 1 year ago

I've pasted your c172p-fg1000-kap.xml file in my aircraft-data directory: same issue, the FG1000 does not respond. Same error messages as usually.

wlbragg commented 1 year ago

Go ahead and I will take a look and try it out.

dany93 commented 1 year ago

No matter how much I think about it, I don't know what to do to go ahead. It's way above my skills. Ask Richard Harrison (Emesery), Horray, @wkitty42, Stuart Buchanan with the error message?

Did you try on Linux?

dany93 commented 1 year ago

The ALRT message in https://github.com/c172p-team/c172p/issues/1410#issuecomment-1415859341 is not the clue: I have it with the Cessna 182T and the FG1000 works from one session the other... Without deleting the c182t.xml file from my aircraft-data directory.

   14.67 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal//EIS/EIS-C182T.nas
   14.67 [INFO]:nasal      53
   14.67 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal//EIS/EISController.nas
   14.67 [INFO]:nasal      58
   14.67 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal//EIS/EISController.nas
   14.67 [INFO]:nasal      89
   14.67 [INFO]:nasal      /home/dany/fgfs-A/install/flightgear/fgdata/Nasal/emesary.nas
   14.67 [INFO]:nasal      179
   14.67 [ALRT]:nasal      Recipient EISController_MFD has been removed from transmitter (GlobalTransmitter) because of the above error
wlbragg commented 1 year ago

Let me look at it a little closer, the EIS is that engine sidebar on the fg1000. It wasn't completely finished at the time I installed the fg1000. I modified the source code so we could have one of the gauges in the EIS working as Stuart hadn't activated it yet. But then, if I remember correctly, he did finally activate it. So there may still be some residual from what i added. I need to take a really close look at our local code and the fgdata code.

Did you try on Linux?

Yeah I am on Windows, I'll try my Linux boot and see if it changes anything for me.

Give me a couple days and let me see what happens in Linux and time to check the code again.

wlbragg commented 1 year ago

I booted into my Linux Pop OS and both versions of the fg1000 worked the same as the Windows version. I don't have your errors.

string index 3 out of bounds (size: 3)

That whole string of error messages looks familiar to me. Something that happened a while back and was fixed?

I checked the EIS stuff and on my version it is all updated and my fix no longer part of the equation. My fix involved fgdata as well as local files. If you still have some of that stuff, (if your build is to old, including fgdata) that might be what is wrong.

How old is your FG build? If it is old I would suggest rebuilding it, deleting the aircraft data and trying it again, before bringing this to Stuart.

dany93 commented 1 year ago

How old is your FG build? If it is old I would suggest rebuilding it, deleting the aircraft data and trying it again...

My build was not that old (19 oct 2022). Also, I was not very optimistic about a rebuild, because the Cessna 182T already worked with my FG compiled version. The issue is only with the c172s and FG1000.

Anyway, I've done a full rebuild from scratch in a new directory, deleting the aircraft data.

The FG1000 works at first launch, same issue at second launch, as usual.

dany93 commented 1 year ago

I've tried to eliminate a flaw in my c172p git local rep. Not very likely IMO, I believe that the right 'SHA1-id' is a proof of integrity.

I've downloaded the .zip from the github c172p repository (Issue-1410 branch, bdab2c93). Same symptoms... FG1000 fails to work at second launch.

So,

What is left???

wlbragg commented 1 year ago

Any difference in the log between woking and failing, such as... https://github.com/c172p-team/c172p/issues/1410#issuecomment-1415859341

I wasn't sure if this was related to the failure or if there is any notifications at all that something went wrong?

wlbragg commented 1 year ago

Did you try my saved data as your starting point for the c172p-fg1000-kap.xml? Go ahead and post your saved data right before before it fails. I assume the saved data doesn't change after you try to load it again and the loading fails?

dany93 commented 1 year ago

Any difference in the log between woking and failing, such as... https://github.com/c172p-team/c172p/issues/1410#issuecomment-1415859341 I wasn't sure if this was related to the failure

I agree.

or if there is any notifications at all that something went wrong?

Apart from the already mentioned set of lines, I don't find obvious error lines.

Here's the log when it fails: (see after 13.99 [INFO]:nasal Traffic pins off)


./run_fgfs.sh
/home/dany/fgfs-B/simgear/simgear/props/props.cxx:106: active: /sim[0]/property-locking[0]/active[0] verbose: /sim[0]/property-locking[0]/verbose[0] timing: /sim[0]/property-locking[0]/timing[0] parent_listeners: /sim[0]/property-locking[0]/parent_listeners[0]
    0.12 [ALRT]:view       Creating osgViewer::CompositeViewer
    0.12 [ALRT]:general    affinity=
    0.12 [ALRT]:view       Calling composite_viewer->setUseConfigureAffinity() with flag=1
Now checking for plug-in osgPlugins-3.6.4/osgdb_nvtt.so
    0.24 [WARN]:general    Enabling ATI/AMD viewport hack
    0.24 [ALRT]:view       affinity=
    0.40 [INFO]:terrasync  Starting automatic scenery download/synchronization to '/home/dany/FG/Scenes/Terrasync'.
    0.47 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/detailed[0]
    0.47 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/rough-delta[0]
    0.47 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/bare-delta[0]
    2.38 [ALRT]:autopilot  DigitalFilter: unknown config node: absolute

In file /home/dany/FG/github/c172p/c172p.xml: line 567
Engine location ignored, only thruster location is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 572
Engine orientation ignored, only thruster orientation is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 596
Engine location ignored, only thruster location is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 601
Engine orientation ignored, only thruster orientation is used.

    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.83 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.84 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.84 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.84 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    8.77 [INFO]:nasal      Failed to find view-number-raw=nil
    8.94 [INFO]:nasal      towing is active!
    8.94 [ALRT]:nasal      ERROR: Cannot add listener to tied property /sim[0]/current-view[0]/heading-offset-deg[0]
    8.96 [INFO]:nasal      KMA20 audio panel initialized
    8.96 [INFO]:nasal      Hobbs system stopped
    8.96 [INFO]:nasal      Hobbs system stopped
    8.96 [INFO]:nasal      Starter off
    8.96 [INFO]:nasal      KI266 dme indicator #0 initialized
    8.97 [INFO]:nasal      Astro Tech LC-2 Chronometer Loaded
    8.97 [INFO]:nasal      
############
    8.97 [INFO]:nasal      #  FG1000  #
    8.97 [INFO]:nasal      ############

    9.01 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/adf[0]/operable[0]
    9.01 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/nav[1]/operable[0]
    9.01 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/nav[0]/operable[0]
    9.01 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/gps[0]/mode[0]
   10.79 [INFO]:nasal      PFD_Device: Error loading MAP - STORMSCOPE: svg layer StormscopeGroup 
   10.79 [INFO]:nasal      PFD_Device: Error loading MAP - WEATHER DATA LINK: svg layer WeatherDataLinkGroup 
   10.80 [INFO]:nasal      PFD_Device: Error loading MAP - TAWS: svg layer TAWSBGroup 
   10.81 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT DIRECTORY: svg layer AirportDirectoryGroup 
   10.82 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT DEPARTURE INFORMATION: svg layer AirportDepartureGroup 
   10.83 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT ARRIVAL INFORMATION: svg layer AirportArrivalGroup 
   10.83 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT APPROACH INFORMATION: svg layer AirportApproachGroup 
   10.84 [INFO]:nasal      PFD_Device: Error loading WPT - WEATHER INFORMATION: svg layer AirportWeatherGroup 
   10.87 [INFO]:nasal      PFD_Device: Error loading WPT - USER WPT INFORMATION: svg layer UserWPTInfoGroup 
   10.87 [INFO]:nasal      PFD_Device: Error loading AUX - TRIP PLANNING: svg layer TripPlanningGroup 
   10.88 [INFO]:nasal      PFD_Device: Error loading AUX - UTILITY: svg layer UtilityGroup 
   10.88 [INFO]:nasal      PFD_Device: Error loading AUX - GPS STATUS: svg layer GPSStatusGroup 
   10.89 [INFO]:nasal      PFD_Device: Error loading AUX - XM RADIO: svg layer XMRadioGroup 
   10.90 [INFO]:nasal      PFD_Device: Error loading AUX - XM INFORMATION: svg layer XMInfoGroup 
   10.90 [INFO]:nasal      PFD_Device: Error loading AUX - SYSTEM STATUS: svg layer SystemStatusGroup 
   10.93 [INFO]:nasal      PFD_Device: Error loading FPL - ACTIVE FLIGHT PLAN: svg layer ActiveFlightPlanWideGroup 
   10.94 [INFO]:nasal      PFD_Device: Error loading FPL - FLIGHT PLAN CATALOG: svg layer FlightPlanCatalogGroup 
   10.94 [INFO]:nasal      PFD_Device: Error loading FPL - STORED FLIGHT PLAN: svg layer StoredFlightPlanGroup 
   11.03 [INFO]:nasal      PFD_Device: Error loading NRST - NEAREST USER WPTS: svg layer NearestUserWPTGroup 
   11.06 [INFO]:nasal      PFD_Device: Error loading NRST - NEAREST AIRSPACES: svg layer NearestAirspacesGroup 
   11.24 [INFO]:nasal      Electrical system initialized
   11.39 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2514.png 6: Couldn't resolve host name
   11.39 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2513.png 6: Couldn't resolve host name
   11.39 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2512.png 6: Couldn't resolve host name
   11.47 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2511.png 6: Couldn't resolve host name
   11.47 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2510.png 6: Couldn't resolve host name
   11.47 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2509.png 6: Couldn't resolve host name
   11.57 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2514.png 6: Couldn't resolve host name
   11.57 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2513.png 6: Couldn't resolve host name
   11.57 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2512.png 6: Couldn't resolve host name
   11.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2508.png 6: Couldn't resolve host name
   11.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2507.png 6: Couldn't resolve host name
   11.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2506.png 6: Couldn't resolve host name
   12.77 [ALRT]:io         mipmapping: texture size not a power-of-two: /home/dany/fgfs-B/install/flightgear/fgdata/Textures/Terrain/california-shrub3.png
   13.99 [INFO]:nasal      Traffic pins off
   14.02 [INFO]:nasal      string index 3 out of bounds (size: 3)
   14.02 [INFO]:nasal      /home/dany/fgfs-B/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas
   14.02 [INFO]:nasal      956
   14.02 [INFO]:nasal      /home/dany/fgfs-B/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstrumentsController.nas
   14.02 [INFO]:nasal      478
   14.02 [INFO]:nasal      /home/dany/fgfs-B/install/flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstrumentsController.nas
   14.02 [INFO]:nasal      540
   14.02 [INFO]:nasal      /home/dany/fgfs-B/install/flightgear/fgdata/Nasal/emesary.nas
   14.02 [INFO]:nasal      179
   14.02 [ALRT]:nasal      Recipient PFDInstrumentsController_PFD has been removed from transmitter (GlobalTransmitter) because of the above error
   14.02 [INFO]:nasal      Annunciator panel: initialized
   14.02 [ALRT]:flight     Failed to save initial FDM property state
   19.58 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2511.png 6: Couldn't resolve host name
   19.58 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2510.png 6: Couldn't resolve host name
   19.58 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2509.png 6: Couldn't resolve host name
   19.58 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2514.png 6: Couldn't resolve host name
   19.70 [INFO]:nasal      Cessna 172P Skyhawk (180 hp) (FG1000-KAP140)
   19.70 [INFO]:nasal      /home/dany/FG/github/c172p
   21.49 [INFO]:nasal      Model load Nimitz /ai/models/carrier
   21.49 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2512.png 6: Couldn't resolve host name
   21.49 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2511.png 6: Couldn't resolve host name
   21.49 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2510.png 6: Couldn't resolve host name
   21.49 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2509.png 6: Couldn't resolve host name
   22.28 [INFO]:nasal      Model load Eisenhower /ai/models/carrier[1]
   22.28 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2513.png 6: Couldn't resolve host name
   22.28 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2512.png 6: Couldn't resolve host name
   22.28 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2511.png 6: Couldn't resolve host name
   22.28 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2510.png 6: Couldn't resolve host name
   22.37 [INFO]:nasal      Primer reset to 0
   22.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2514.png 6: Couldn't resolve host name
   22.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2513.png 6: Couldn't resolve host name
   22.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2512.png 6: Couldn't resolve host name
   22.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2511.png 6: Couldn't resolve host name
   22.71 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2506.png 6: Couldn't resolve host name
   22.71 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2514.png 6: Couldn't resolve host name
   22.71 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2513.png 6: Couldn't resolve host name
   22.71 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2512.png 6: Couldn't resolve host name
   22.80 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2507.png 6: Couldn't resolve host name
   22.80 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2506.png 6: Couldn't resolve host name
   22.80 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2514.png 6: Couldn't resolve host name
   22.80 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2513.png 6: Couldn't resolve host name
   26.25 [INFO]:nasal      Starter on
   27.96 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2508.png 6: Couldn't resolve host name
   27.96 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2507.png 6: Couldn't resolve host name
   27.96 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2506.png 6: Couldn't resolve host name
   27.96 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2514.png 6: Couldn't resolve host name
   28.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2509.png 6: Couldn't resolve host name
   28.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2508.png 6: Couldn't resolve host name
   28.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2507.png 6: Couldn't resolve host name
   28.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2506.png 6: Couldn't resolve host name
   28.11 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2510.png 6: Couldn't resolve host name
   28.11 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2509.png 6: Couldn't resolve host name
   28.11 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2514.png 6: Couldn't resolve host name
   28.11 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2513.png 6: Couldn't resolve host name
   28.40 [INFO]:nasal      Hobbs system started
   28.42 [INFO]:nasal      Starter off
   33.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2513.png 6: Couldn't resolve host name
   33.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2508.png 6: Couldn't resolve host name
   33.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2507.png 6: Couldn't resolve host name
   33.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2506.png 6: Couldn't resolve host name
   33.30 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2506.png 6: Couldn't resolve host name
   33.30 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2510.png 6: Couldn't resolve host name
   33.30 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2509.png 6: Couldn't resolve host name
   33.30 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2508.png 6: Couldn't resolve host name
   33.37 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2508.png 6: Couldn't resolve host name
   33.37 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2512.png 6: Couldn't resolve host name
   33.37 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2511.png 6: Couldn't resolve host name
   33.37 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2510.png 6: Couldn't resolve host name
   33.40 [INFO]:nasal      Primer reset to 0
   33.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2508.png 6: Couldn't resolve host name
   33.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2507.png 6: Couldn't resolve host name
   33.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2506.png 6: Couldn't resolve host name
   33.44 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2510.png 6: Couldn't resolve host name
   33.50 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2506.png 6: Couldn't resolve host name
   33.50 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2514.png 6: Couldn't resolve host name
   33.50 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2509.png 6: Couldn't resolve host name
   33.54 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2511.png 6: Couldn't resolve host name
   33.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2509.png 6: Couldn't resolve host name
   33.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2509.png 6: Couldn't resolve host name
   33.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2513.png 6: Couldn't resolve host name
   33.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2512.png 6: Couldn't resolve host name
   33.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2507.png 6: Couldn't resolve host name
   33.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2508.png 6: Couldn't resolve host name
   33.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2507.png 6: Couldn't resolve host name
   33.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2507.png 6: Couldn't resolve host name
   33.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2510.png 6: Couldn't resolve host name
   33.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2512.png 6: Couldn't resolve host name
   33.68 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2511.png 6: Couldn't resolve host name
   33.76 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2511.png 6: Couldn't resolve host name
   33.76 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2508.png 6: Couldn't resolve host name

And the log when it works

./run_fgfs.sh
/home/dany/fgfs-B/simgear/simgear/props/props.cxx:106: active: /sim[0]/property-locking[0]/active[0] verbose: /sim[0]/property-locking[0]/verbose[0] timing: /sim[0]/property-locking[0]/timing[0] parent_listeners: /sim[0]/property-locking[0]/parent_listeners[0]
    0.14 [ALRT]:view       Creating osgViewer::CompositeViewer
    0.14 [ALRT]:general    affinity=
    0.14 [ALRT]:view       Calling composite_viewer->setUseConfigureAffinity() with flag=1
Now checking for plug-in osgPlugins-3.6.4/osgdb_nvtt.so
    0.26 [WARN]:general    Enabling ATI/AMD viewport hack
    0.26 [ALRT]:view       affinity=
    0.43 [INFO]:terrasync  Starting automatic scenery download/synchronization to '/home/dany/FG/Scenes/Terrasync'.
    0.51 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/detailed[0]
    0.51 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/rough-delta[0]
    0.51 [ALRT]:terrain    Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/bare-delta[0]
    2.44 [ALRT]:autopilot  DigitalFilter: unknown config node: absolute

In file /home/dany/FG/github/c172p/c172p.xml: line 567
Engine location ignored, only thruster location is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 572
Engine orientation ignored, only thruster orientation is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 596
Engine location ignored, only thruster location is used.

In file /home/dany/FG/github/c172p/c172p.xml: line 601
Engine orientation ignored, only thruster orientation is used.

    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    2.90 [ALRT]:autopilot  DigitalFilter: unknown config node: value
    8.82 [INFO]:nasal      Failed to find view-number-raw=nil
    9.00 [INFO]:nasal      towing is active!
    9.00 [ALRT]:nasal      ERROR: Cannot add listener to tied property /sim[0]/current-view[0]/heading-offset-deg[0]
    9.02 [INFO]:nasal      KMA20 audio panel initialized
    9.03 [INFO]:nasal      Hobbs system stopped
    9.03 [INFO]:nasal      Hobbs system stopped
    9.03 [INFO]:nasal      Starter off
    9.03 [INFO]:nasal      KI266 dme indicator #0 initialized
    9.03 [INFO]:nasal      Astro Tech LC-2 Chronometer Loaded
    9.03 [INFO]:nasal      
############
    9.03 [INFO]:nasal      #  FG1000  #
    9.03 [INFO]:nasal      ############

    9.07 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/adf[0]/operable[0]
    9.07 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/nav[1]/operable[0]
    9.07 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/nav[0]/operable[0]
    9.07 [ALRT]:nasal      ERROR: Cannot add listener to tied property /instrumentation[0]/gps[0]/mode[0]
   10.86 [INFO]:nasal      PFD_Device: Error loading MAP - STORMSCOPE: svg layer StormscopeGroup 
   10.87 [INFO]:nasal      PFD_Device: Error loading MAP - WEATHER DATA LINK: svg layer WeatherDataLinkGroup 
   10.87 [INFO]:nasal      PFD_Device: Error loading MAP - TAWS: svg layer TAWSBGroup 
   10.90 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT DIRECTORY: svg layer AirportDirectoryGroup 
   10.90 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT DEPARTURE INFORMATION: svg layer AirportDepartureGroup 
   10.91 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT ARRIVAL INFORMATION: svg layer AirportArrivalGroup 
   10.92 [INFO]:nasal      PFD_Device: Error loading WPT - AIRPORT APPROACH INFORMATION: svg layer AirportApproachGroup 
   10.92 [INFO]:nasal      PFD_Device: Error loading WPT - WEATHER INFORMATION: svg layer AirportWeatherGroup 
   10.95 [INFO]:nasal      PFD_Device: Error loading WPT - USER WPT INFORMATION: svg layer UserWPTInfoGroup 
   10.96 [INFO]:nasal      PFD_Device: Error loading AUX - TRIP PLANNING: svg layer TripPlanningGroup 
   10.96 [INFO]:nasal      PFD_Device: Error loading AUX - UTILITY: svg layer UtilityGroup 
   10.97 [INFO]:nasal      PFD_Device: Error loading AUX - GPS STATUS: svg layer GPSStatusGroup 
   10.98 [INFO]:nasal      PFD_Device: Error loading AUX - XM RADIO: svg layer XMRadioGroup 
   10.98 [INFO]:nasal      PFD_Device: Error loading AUX - XM INFORMATION: svg layer XMInfoGroup 
   10.99 [INFO]:nasal      PFD_Device: Error loading AUX - SYSTEM STATUS: svg layer SystemStatusGroup 
   11.02 [INFO]:nasal      PFD_Device: Error loading FPL - ACTIVE FLIGHT PLAN: svg layer ActiveFlightPlanWideGroup 
   11.02 [INFO]:nasal      PFD_Device: Error loading FPL - FLIGHT PLAN CATALOG: svg layer FlightPlanCatalogGroup 
   11.03 [INFO]:nasal      PFD_Device: Error loading FPL - STORED FLIGHT PLAN: svg layer StoredFlightPlanGroup 
   11.11 [INFO]:nasal      PFD_Device: Error loading NRST - NEAREST USER WPTS: svg layer NearestUserWPTGroup 
   11.14 [INFO]:nasal      PFD_Device: Error loading NRST - NEAREST AIRSPACES: svg layer NearestAirspacesGroup 
   11.33 [INFO]:nasal      Electrical system initialized
   11.48 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2514.png 6: Couldn't resolve host name
   11.48 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2513.png 6: Couldn't resolve host name
   11.48 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2512.png 6: Couldn't resolve host name
   11.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2511.png 6: Couldn't resolve host name
   11.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2510.png 6: Couldn't resolve host name
   11.56 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2509.png 6: Couldn't resolve host name
   11.62 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2514.png 6: Couldn't resolve host name
   11.62 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2513.png 6: Couldn't resolve host name
   11.62 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2512.png 6: Couldn't resolve host name
   11.67 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2508.png 6: Couldn't resolve host name
   11.67 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2507.png 6: Couldn't resolve host name
   11.67 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2506.png 6: Couldn't resolve host name
   11.72 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2511.png 6: Couldn't resolve host name
   11.72 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2510.png 6: Couldn't resolve host name
   11.72 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2509.png 6: Couldn't resolve host name
   11.77 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2514.png 6: Couldn't resolve host name
   11.77 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2513.png 6: Couldn't resolve host name
   11.77 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2512.png 6: Couldn't resolve host name
   11.82 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2508.png 6: Couldn't resolve host name
   11.82 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2507.png 6: Couldn't resolve host name
   11.82 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2506.png 6: Couldn't resolve host name
   11.90 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2511.png 6: Couldn't resolve host name
   11.90 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2510.png 6: Couldn't resolve host name
   11.90 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2509.png 6: Couldn't resolve host name
   11.95 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2514.png 6: Couldn't resolve host name
   11.95 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2513.png 6: Couldn't resolve host name
   11.95 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2512.png 6: Couldn't resolve host name
   12.01 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2508.png 6: Couldn't resolve host name
   12.01 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2507.png 6: Couldn't resolve host name
   12.01 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2506.png 6: Couldn't resolve host name
   12.06 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2511.png 6: Couldn't resolve host name
   12.06 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2510.png 6: Couldn't resolve host name
   12.06 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2509.png 6: Couldn't resolve host name
   12.12 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2514.png 6: Couldn't resolve host name
   12.12 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2513.png 6: Couldn't resolve host name
   12.12 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2512.png 6: Couldn't resolve host name
   12.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2508.png 6: Couldn't resolve host name
   12.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2507.png 6: Couldn't resolve host name
   12.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2506.png 6: Couldn't resolve host name
   12.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2511.png 6: Couldn't resolve host name
   12.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2510.png 6: Couldn't resolve host name
   12.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2509.png 6: Couldn't resolve host name
   12.83 [ALRT]:io         mipmapping: texture size not a power-of-two: /home/dany/fgfs-B/install/flightgear/fgdata/Textures/Terrain/california-shrub3.png
   14.05 [INFO]:nasal      Traffic pins off
   14.05 [INFO]:nasal      Annunciator panel: initialized
   14.05 [ALRT]:flight     Failed to save initial FDM property state
   19.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2508.png 6: Couldn't resolve host name
   19.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2507.png 6: Couldn't resolve host name
   19.63 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/651/2506.png 6: Couldn't resolve host name
   19.81 [INFO]:nasal      Cessna 172P Skyhawk (180 hp) (FG1000-KAP140)
   19.81 [INFO]:nasal      /home/dany/FG/github/c172p
   21.59 [INFO]:nasal      Model load Nimitz /ai/models/carrier
   21.59 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2514.png 6: Couldn't resolve host name
   21.59 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2513.png 6: Couldn't resolve host name
   21.59 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2512.png 6: Couldn't resolve host name
   22.40 [INFO]:nasal      Model load Eisenhower /ai/models/carrier[1]
   22.40 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2511.png 6: Couldn't resolve host name
   22.40 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2510.png 6: Couldn't resolve host name
   22.40 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/654/2509.png 6: Couldn't resolve host name
   22.55 [INFO]:nasal      Primer reset to 0
   22.61 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2508.png 6: Couldn't resolve host name
   22.61 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2507.png 6: Couldn't resolve host name
   22.61 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2506.png 6: Couldn't resolve host name
   22.91 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2514.png 6: Couldn't resolve host name
   22.91 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2513.png 6: Couldn't resolve host name
   22.91 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2512.png 6: Couldn't resolve host name
   22.98 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2511.png 6: Couldn't resolve host name
   22.98 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2510.png 6: Couldn't resolve host name
   22.98 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/658/2509.png 6: Couldn't resolve host name
   23.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2508.png 6: Couldn't resolve host name
   23.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2507.png 6: Couldn't resolve host name
   23.02 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2506.png 6: Couldn't resolve host name
   23.13 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2508.png 6: Couldn't resolve host name
   23.13 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2507.png 6: Couldn't resolve host name
   23.13 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/653/2506.png 6: Couldn't resolve host name
   23.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2511.png 6: Couldn't resolve host name
   23.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2510.png 6: Couldn't resolve host name
   23.18 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/656/2509.png 6: Couldn't resolve host name
   23.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2514.png 6: Couldn't resolve host name
   23.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2513.png 6: Couldn't resolve host name
   23.23 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/659/2512.png 6: Couldn't resolve host name
   28.30 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2511.png 6: Couldn't resolve host name
   28.33 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2514.png 6: Couldn't resolve host name
   28.33 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2513.png 6: Couldn't resolve host name
   28.33 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/655/2512.png 6: Couldn't resolve host name
   28.35 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2509.png 6: Couldn't resolve host name
   28.38 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/652/2510.png 6: Couldn't resolve host name
   28.38 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2508.png 6: Couldn't resolve host name
   28.38 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2507.png 6: Couldn't resolve host name
   28.38 [INFO]:nasal      Failed to get image /home/dany/.fgfs/cache/maps/openaip_basemap/12/657/2506.png 6: Couldn't resolve host name
   28.71 [INFO]:nasal      Starter on
   30.85 [INFO]:nasal      Hobbs system started
   30.88 [INFO]:nasal      Starter off
   35.87 [INFO]:nasal      Primer reset to 0
dany93 commented 1 year ago

Did you try my saved data as your starting point for the c172p-fg1000-kap.xml?

Yes. This response. https://github.com/c172p-team/c172p/issues/1410#issuecomment-1417631819

Go ahead and post your saved data right before before it fails. I assume the saved data doesn't change after you try to load it again and the loading fails?

Before it fails: Launch with no file in .fgfs/aircraft-data. The FG1000 works. Quitting the simulator creates this file.

<?xml version="1.0"?>

<PropertyList>
  <sim>
    <model>
      <occupants type="bool">true</occupants>
      <c172p>
        <cockpit>
          <control-lock-placed type="bool">false</control-lock-placed>
        </cockpit>
        <securing>
          <pitot-cover-visible type="bool">false</pitot-cover-visible>
          <cowl-plugs-visible type="bool">false</cowl-plugs-visible>
          <chock type="bool">false</chock>
          <tiedownL-visible type="bool">false</tiedownL-visible>
          <tiedownR-visible type="bool">false</tiedownR-visible>
          <tiedownT-visible type="bool">false</tiedownT-visible>
        </securing>
        <enable-fog-frost type="bool">true</enable-fog-frost>
        <digitalclock-visible type="bool">false</digitalclock-visible>
        <save-state type="bool">false</save-state>
        <ruddertrim-visible type="bool">false</ruddertrim-visible>
        <immat-on-panel type="bool">false</immat-on-panel>
      </c172p>
      <walker n="1">
        <animate>
          <enabled-triggers type="bool">true</enabled-triggers>
          <list>
            <sequence>
              <trigger-upon type="string">Standing</trigger-upon>
            </sequence>
            <sequence n="8">
              <trigger-upon type="string">Disabled</trigger-upon>
            </sequence>
          </list>
        </animate>
      </walker>
      <livery>
        <name type="string">4X-CHV (HD livery)</name>
      </livery>
    </model>
    <current-view>
      <user>
        <x-offset-m type="double">-0.21</x-offset-m>
        <y-offset-m type="double">0.208</y-offset-m>
        <z-offset-m type="double">0.36</z-offset-m>
        <pitch-offset-deg type="double">-12</pitch-offset-deg>
        <default-field-of-view-deg type="double">73.6</default-field-of-view-deg>
      </user>
    </current-view>
    <walker>
    </walker>
    <time>
      <hobbs>
        <engine type="double">0</engine>
        <engine n="1" type="double">15.55</engine>
      </hobbs>
    </time>
    <view n="110">
      <enabled type="bool">false</enabled>
    </view>
    <view n="111">
      <enabled type="bool">false</enabled>
    </view>
  </sim>
  <controls>
    <gear>
      <brake-parking type="double">0</brake-parking>
    </gear>
    <climate-control>
      <overhead-vent-front-left type="double">0</overhead-vent-front-left>
      <overhead-vent-front-right type="double">0</overhead-vent-front-right>
    </climate-control>
    <mooring>
      <automatic type="bool">false</automatic>
    </mooring>
    <lighting>
      <beacon type="bool">true</beacon>
      <landing-lights type="bool">false</landing-lights>
      <nav-lights type="bool">true</nav-lights>
      <strobe type="bool">true</strobe>
      <taxi-light type="bool">false</taxi-light>
      <gearled type="bool">false</gearled>
      <instruments-norm type="double">0</instruments-norm>
      <radio-norm type="double">0</radio-norm>
      <dome-white-norm type="double">1</dome-white-norm>
    </lighting>
    <switches>
      <magnetos type="int">3</magnetos>
      <master-bat type="bool">true</master-bat>
      <master-alt type="bool">true</master-alt>
      <master-avionics type="bool">true</master-avionics>
      <dome-red type="int">0</dome-red>
      <dome-white type="bool">false</dome-white>
    </switches>
    <anti-ice>
      <engine>
        <carb-heat type="bool">false</carb-heat>
      </engine>
      <pitot-heat type="bool">false</pitot-heat>
    </anti-ice>
    <flight>
      <flaps type="double">0</flaps>
      <elevator-trim type="double">0</elevator-trim>
    </flight>
    <engines>
      <current-engine>
        <throttle type="double">0.2</throttle>
        <mixture type="double">1</mixture>
      </current-engine>
      <engine>
        <primer-lever type="bool">false</primer-lever>
      </engine>
    </engines>
    <circuit-breakers>
      <autopilot type="bool">true</autopilot>
      <bcnlt type="bool">true</bcnlt>
      <flaps type="bool">true</flaps>
      <instr type="bool">true</instr>
      <intlt type="bool">true</intlt>
      <landing type="bool">true</landing>
      <master type="bool">true</master>
      <navlt type="bool">true</navlt>
      <pitot-heat type="bool">true</pitot-heat>
      <radio1 type="bool">true</radio1>
      <radio2 type="bool">true</radio2>
      <radio3 type="bool">true</radio3>
      <radio4 type="bool">true</radio4>
      <radio5 type="bool">true</radio5>
      <strobe type="bool">true</strobe>
      <turn-coordinator type="bool">true</turn-coordinator>
    </circuit-breakers>
  </controls>
  <engines>
    <active-engine>
      <carb_icing_allowed type="bool">false</carb_icing_allowed>
      <oil_consumption_allowed type="bool">false</oil_consumption_allowed>
      <oil-service-hours type="double">0</oil-service-hours>
      <oil-level type="double">8</oil-level>
      <complex-engine-procedures type="bool">false</complex-engine-procedures>
    </active-engine>
    <engine>
    </engine>
  </engines>
  <fdm>
    <jsbsim>
      <engine>
        <damage-level type="double">0</damage-level>
      </engine>
      <settings>
        <damage type="bool">true</damage>
        <damage-flag type="bool">false</damage-flag>
      </settings>
      <running type="bool">false</running>
      <fuel>
        <tank type="bool">true</tank>
      </fuel>
    </jsbsim>
  </fdm>
  <environment>
    <aircraft-effects>
      <cabin-heat-set type="double">0</cabin-heat-set>
      <cabin-air-set type="double">0</cabin-air-set>
    </aircraft-effects>
  </environment>
  <consumables>
    <fuel>
      <contamination_allowed type="bool">false</contamination_allowed>
      <tank>
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="1">
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="2">
        <level-norm type="double">0.2499142157</level-norm>
        <selected type="bool">true</selected>
      </tank>
      <tank n="3">
        <level-norm type="double">0.2499142157</level-norm>
        <selected type="bool">true</selected>
      </tank>
    </fuel>
  </consumables>
  <instrumentation>
    <save-switches-state type="bool">false</save-switches-state>
    <dme>
      <power-btn type="bool">true</power-btn>
      <switch-min-kts type="bool">true</switch-min-kts>
      <switch-position type="int">2</switch-position>
      <frequencies>
        <source type="string">/instrumentation/nav[0]/frequencies/selected-mhz</source>
        <selected-mhz type="double">112</selected-mhz>
      </frequencies>
    </dme>
    <kma20>
      <test type="int">0</test>
      <auto type="int">1</auto>
      <com1 type="int">0</com1>
      <com2 type="int">0</com2>
      <nav1 type="int">0</nav1>
      <nav2 type="int">0</nav2>
      <adf type="int">0</adf>
      <dme type="int">0</dme>
      <mkr type="int">-1</mkr>
      <sens type="int">0</sens>
      <knob type="int">-1</knob>
    </kma20>
    <comm>
      <power-btn type="double">0</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">120.5</selected-mhz>
        <standby-mhz type="double">119.3</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <channel-mode-selector type="bool">true</channel-mode-selector>
    </comm>
    <nav>
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.5</volume>
      <frequencies>
        <selected-mhz type="double">112</selected-mhz>
        <standby-mhz type="double">108.5</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">284</selected-deg>
      </radials>
    </nav>
    <comm n="1">
      <power-btn type="bool">true</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">128.3</selected-mhz>
        <standby-mhz type="double">121.9</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
    </comm>
    <nav n="1">
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.7</volume>
      <frequencies>
        <selected-mhz type="double">112.4</selected-mhz>
        <standby-mhz type="double">113.6</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">326</selected-deg>
      </radials>
    </nav>
    <altimeter>
      <setting-inhg type="double">29.97269627</setting-inhg>
    </altimeter>
    <attitude-indicator>
    </attitude-indicator>
    <heading-indicator>
      <offset-deg type="double">-12.67313616</offset-deg>
    </heading-indicator>
    <adf>
      <rotation-deg type="double">0</rotation-deg>
      <frequencies>
        <dial-1-khz type="int">0</dial-1-khz>
        <dial-100-khz type="int">0</dial-100-khz>
        <standby-khz type="double">200</standby-khz>
        <selected-khz type="double">200</selected-khz>
      </frequencies>
      <adf-btn type="bool">false</adf-btn>
      <bfo-btn type="bool">false</bfo-btn>
      <volume-norm type="double">0.5</volume-norm>
      <power-btn type="bool">true</power-btn>
    </adf>
    <transponder>
      <inputs>
        <knob-mode type="int">4</knob-mode>
        <ident-btn type="bool">false</ident-btn>
        <digit type="int">0</digit>
        <digit n="1" type="int">0</digit>
        <digit n="2" type="int">2</digit>
        <digit n="3" type="int">1</digit>
      </inputs>
    </transponder>
    <clock>
      <lc2>
        <flight-meter-sec type="double">0</flight-meter-sec>
      </lc2>
    </clock>
  </instrumentation>
  <systems>
    <electrical>
      <save-battery-charge type="bool">false</save-battery-charge>
      <battery-charge-percent>
        <a type="double">0.9953526583</a>
        <b type="double">1</b>
      </battery-charge-percent>
    </electrical>
  </systems>
  <autopilot>
    <settings>
      <heading-bug-deg type="string">0</heading-bug-deg>
    </settings>
  </autopilot>
</PropertyList>

After it fails:

<?xml version="1.0"?>

<PropertyList>
  <sim>
    <model>
      <occupants type="bool">true</occupants>
      <c172p>
        <cockpit>
          <control-lock-placed type="bool">false</control-lock-placed>
        </cockpit>
        <securing>
          <pitot-cover-visible type="bool">false</pitot-cover-visible>
          <cowl-plugs-visible type="bool">false</cowl-plugs-visible>
          <chock type="bool">false</chock>
          <tiedownL-visible type="bool">false</tiedownL-visible>
          <tiedownR-visible type="bool">false</tiedownR-visible>
          <tiedownT-visible type="bool">false</tiedownT-visible>
        </securing>
        <enable-fog-frost type="bool">true</enable-fog-frost>
        <digitalclock-visible type="bool">false</digitalclock-visible>
        <save-state type="bool">false</save-state>
        <ruddertrim-visible type="bool">false</ruddertrim-visible>
        <immat-on-panel type="bool">false</immat-on-panel>
      </c172p>
      <walker n="1">
        <animate>
          <enabled-triggers type="bool">true</enabled-triggers>
          <list>
            <sequence>
              <trigger-upon type="string">Standing</trigger-upon>
            </sequence>
            <sequence n="8">
              <trigger-upon type="string">Disabled</trigger-upon>
            </sequence>
          </list>
        </animate>
      </walker>
      <livery>
        <name type="string">4X-CHV (HD livery)</name>
      </livery>
    </model>
    <current-view>
      <user>
        <x-offset-m type="double">-0.21</x-offset-m>
        <y-offset-m type="double">0.208</y-offset-m>
        <z-offset-m type="double">0.36</z-offset-m>
        <pitch-offset-deg type="double">-12</pitch-offset-deg>
        <default-field-of-view-deg type="double">73.6</default-field-of-view-deg>
      </user>
    </current-view>
    <walker>
    </walker>
    <time>
      <hobbs>
        <engine type="double">0</engine>
        <engine n="1" type="double">24.63333333</engine>
      </hobbs>
    </time>
    <view n="110">
      <enabled type="bool">false</enabled>
    </view>
    <view n="111">
      <enabled type="bool">false</enabled>
    </view>
  </sim>
  <controls>
    <gear>
      <brake-parking type="double">0</brake-parking>
    </gear>
    <climate-control>
      <overhead-vent-front-left type="double">0</overhead-vent-front-left>
      <overhead-vent-front-right type="double">0</overhead-vent-front-right>
    </climate-control>
    <mooring>
      <automatic type="bool">false</automatic>
    </mooring>
    <lighting>
      <beacon type="bool">true</beacon>
      <landing-lights type="bool">false</landing-lights>
      <nav-lights type="bool">true</nav-lights>
      <strobe type="bool">true</strobe>
      <taxi-light type="bool">false</taxi-light>
      <gearled type="bool">false</gearled>
      <instruments-norm type="double">0</instruments-norm>
      <radio-norm type="double">0</radio-norm>
      <dome-white-norm type="double">1</dome-white-norm>
    </lighting>
    <switches>
      <magnetos type="int">3</magnetos>
      <master-bat type="bool">true</master-bat>
      <master-alt type="bool">true</master-alt>
      <master-avionics type="bool">true</master-avionics>
      <dome-red type="int">0</dome-red>
      <dome-white type="bool">false</dome-white>
    </switches>
    <anti-ice>
      <engine>
        <carb-heat type="bool">false</carb-heat>
      </engine>
      <pitot-heat type="bool">false</pitot-heat>
    </anti-ice>
    <flight>
      <flaps type="double">0</flaps>
      <elevator-trim type="double">0</elevator-trim>
    </flight>
    <engines>
      <current-engine>
        <throttle type="double">0.2</throttle>
        <mixture type="double">1</mixture>
      </current-engine>
      <engine>
        <primer-lever type="bool">false</primer-lever>
      </engine>
    </engines>
    <circuit-breakers>
      <autopilot type="bool">true</autopilot>
      <bcnlt type="bool">true</bcnlt>
      <flaps type="bool">true</flaps>
      <instr type="bool">true</instr>
      <intlt type="bool">true</intlt>
      <landing type="bool">true</landing>
      <master type="bool">true</master>
      <navlt type="bool">true</navlt>
      <pitot-heat type="bool">true</pitot-heat>
      <radio1 type="bool">true</radio1>
      <radio2 type="bool">true</radio2>
      <radio3 type="bool">true</radio3>
      <radio4 type="bool">true</radio4>
      <radio5 type="bool">true</radio5>
      <strobe type="bool">true</strobe>
      <turn-coordinator type="bool">true</turn-coordinator>
    </circuit-breakers>
  </controls>
  <engines>
    <active-engine>
      <carb_icing_allowed type="bool">false</carb_icing_allowed>
      <oil_consumption_allowed type="bool">false</oil_consumption_allowed>
      <oil-service-hours type="double">0</oil-service-hours>
      <oil-level type="double">8</oil-level>
      <complex-engine-procedures type="bool">false</complex-engine-procedures>
    </active-engine>
    <engine>
    </engine>
  </engines>
  <fdm>
    <jsbsim>
      <engine>
        <damage-level type="double">0</damage-level>
      </engine>
      <settings>
        <damage type="bool">true</damage>
        <damage-flag type="bool">false</damage-flag>
      </settings>
      <running type="bool">false</running>
      <fuel>
        <tank type="bool">true</tank>
      </fuel>
    </jsbsim>
  </fdm>
  <environment>
    <aircraft-effects>
      <cabin-heat-set type="double">0</cabin-heat-set>
      <cabin-air-set type="double">0</cabin-air-set>
    </aircraft-effects>
  </environment>
  <consumables>
    <fuel>
      <contamination_allowed type="bool">false</contamination_allowed>
      <tank>
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="1">
        <level-norm type="double">0</level-norm>
        <selected type="bool">false</selected>
      </tank>
      <tank n="2">
        <level-norm type="double">0.2499428105</level-norm>
        <selected type="bool">true</selected>
      </tank>
      <tank n="3">
        <level-norm type="double">0.2499428105</level-norm>
        <selected type="bool">true</selected>
      </tank>
    </fuel>
  </consumables>
  <instrumentation>
    <save-switches-state type="bool">false</save-switches-state>
    <dme>
      <power-btn type="bool">true</power-btn>
      <switch-min-kts type="bool">true</switch-min-kts>
      <switch-position type="int">2</switch-position>
      <frequencies>
        <source type="string">/instrumentation/nav[0]/frequencies/selected-mhz</source>
        <selected-mhz type="double">112</selected-mhz>
      </frequencies>
    </dme>
    <kma20>
      <test type="int">0</test>
      <auto type="int">1</auto>
      <com1 type="int">0</com1>
      <com2 type="int">0</com2>
      <nav1 type="int">0</nav1>
      <nav2 type="int">0</nav2>
      <adf type="int">0</adf>
      <dme type="int">0</dme>
      <mkr type="int">-1</mkr>
      <sens type="int">0</sens>
      <knob type="int">-1</knob>
    </kma20>
    <comm>
      <power-btn type="double">0</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">120.5</selected-mhz>
        <standby-mhz type="double">119.3</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <channel-mode-selector type="bool">true</channel-mode-selector>
    </comm>
    <nav>
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.5</volume>
      <frequencies>
        <selected-mhz type="double">112</selected-mhz>
        <standby-mhz type="double">108.5</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">284</selected-deg>
      </radials>
    </nav>
    <comm n="1">
      <power-btn type="bool">true</power-btn>
      <volume-selected type="double">0.7</volume-selected>
      <frequencies>
        <selected-mhz type="double">128.3</selected-mhz>
        <standby-mhz type="double">121.9</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
    </comm>
    <nav n="1">
      <ident-audible type="bool">false</ident-audible>
      <power-btn type="bool">true</power-btn>
      <volume type="double">0.7</volume>
      <frequencies>
        <selected-mhz type="double">112.4</selected-mhz>
        <standby-mhz type="double">113.6</standby-mhz>
        <dial-khz type="int">0</dial-khz>
        <dial-mhz type="int">0</dial-mhz>
      </frequencies>
      <radials>
        <selected-deg type="double">326</selected-deg>
      </radials>
    </nav>
    <altimeter>
      <setting-inhg type="double">29.97269627</setting-inhg>
    </altimeter>
    <attitude-indicator>
    </attitude-indicator>
    <heading-indicator>
      <offset-deg type="double">-12.67313612</offset-deg>
    </heading-indicator>
    <adf>
      <rotation-deg type="double">0</rotation-deg>
      <frequencies>
        <dial-1-khz type="int">0</dial-1-khz>
        <dial-100-khz type="int">0</dial-100-khz>
        <standby-khz type="double">200</standby-khz>
        <selected-khz type="double">200</selected-khz>
      </frequencies>
      <adf-btn type="bool">false</adf-btn>
      <bfo-btn type="bool">false</bfo-btn>
      <volume-norm type="double">0.5</volume-norm>
      <power-btn type="bool">true</power-btn>
    </adf>
    <transponder>
      <inputs>
        <knob-mode type="int">4</knob-mode>
        <ident-btn type="bool">false</ident-btn>
        <digit type="int">0</digit>
        <digit n="1" type="int">0</digit>
        <digit n="2" type="int">2</digit>
        <digit n="3" type="int">1</digit>
      </inputs>
    </transponder>
    <clock>
      <lc2>
        <flight-meter-sec type="double">0</flight-meter-sec>
      </lc2>
    </clock>
  </instrumentation>
  <systems>
    <electrical>
      <save-battery-charge type="bool">false</save-battery-charge>
      <battery-charge-percent>
        <a type="double">0.9943686174</a>
        <b type="double">1</b>
      </battery-charge-percent>
    </electrical>
  </systems>
  <autopilot>
    <settings>
      <heading-bug-deg type="string">357</heading-bug-deg>
    </settings>
  </autopilot>
</PropertyList>

==> Just a few differences on hobbs/engine, fuel level, heading-indicator offset, battery charge, heading bug.

dany93 commented 1 year ago

I've made a kind of 'git bisect' in the aircraft-data/c172p-fg1000-kap.xml file.

The error comes with these lines: (inside <instrumentation>)

    <transponder>
      <inputs>
        <knob-mode type="int">4</knob-mode>
        <ident-btn type="bool">false</ident-btn>
        <digit type="int">0</digit>
        <digit n="1" type="int">0</digit>
        <digit n="2" type="int">2</digit>
        <digit n="3" type="int">1</digit>
      </inputs>
    </transponder>

If they are in the file, the FG1000 PFD does not respond. My issue. If they are not in it, it responds and displays changes.

They are automatically added again at 'quit' of the simulator.

The line <knob-mode type="int">4</knob-mode>alone is enough to give the error. like this:

    <transponder>
      <inputs>
        <knob-mode type="int">4</knob-mode>
      </inputs>
    </transponder>
dany93 commented 1 year ago

I'm afraid to hold you up for an issue which is not due to to your merge request.

As it seems that the FG1000 at least partially works (maybe to be checked better) with no file in aircraft-data for me, would you prefer that I merge your commit? Assuming my issue is due to I don't know which particular configuration.

wlbragg commented 1 year ago

It's not critical that we get this done immediately, There are no changes in the source that are going to make the existing version fail. At worst users get the warnings. I don't know when anyone will implement any actual changes to the fg source that will cause errors.

The error comes with these lines:

(inside <instrumentation>)
<transponder>
<inputs>
<knob-mode type="int">4</knob-mode>
<ident-btn type="bool">false</ident-btn>
<digit type="int">0</digit>
<digit n="1" type="int">0</digit>
<digit n="2" type="int">2</digit>
<digit n="3" type="int">1</digit>
</inputs>
</transponder>

If they are in the file, the FG1000 PFD does not respond. My issue. If they are not in it, it responds and displays changes.

OK, this leads me to a potential issue. It's kind of complicated, but not really. We have different set files that load different variants and their configurations. The important part of this is that the fg1000 aircraft use a different electrical system and do not use many of the systems of the other variant aircraft. Yet we also have a c172p-main.xml file that all the variants load and use. I did a bunch of work separating out the systems to their appropriate variants. So fg1000 variants will have one set of system files load other variants will also load different system files. I just looked in c172p-main.xml, which all variants load, and there is still in the system section...

property-rule n="100" FiltersOnly Systems/instruments.xml

which is being loaded in all variants.

If you look into this file you will probably find some instrument filters that don't belong in the fg1000 configuration.

I think I just missed it. Why it messes with your setup and not mine, I have no clue. But I am guessing this is the issue. There may be other system files that need to be dissected and broke out for inclusion in either the fg1000 or the other variants, but not both.

I also need to look closely at what is in the systems.xml file and make sure those items belong in all variants.

This is going to take some digging.

So let's leave this PR open, I'll go through the systems and make sure they are separated appropriately. You can test it and if/when it works correctly, we can do the merge and head off a potential issue for others. OK?

wlbragg commented 1 year ago

This list is mainly for my reference so I don't forget what I need to review. A little more extensive than I hoped. Most of this is innocuous, but some of it could cause an issue. The variant system is really nice but it needs to be laid out in advanced and given much thought to in the beginning VS after the fact.

Systems/instruments.xml Systems/instrumentation.xml Systems/als-lights.xml

        <panel>
            <path>Aircraft/c172p/Panels/c172-610x-panel.xml</path>
            <visibility>false</visibility>
        </panel>
        <aircraft-data>
            <path>/instrumentation/save-switches-state</path>
            <path>/systems/electrical/save-battery-charge</path>
            <path>/systems/electrical/battery-charge-percent</path>
        </aircraft-data>
        <flight-recorder>
            <replay-config type="int">0</replay-config>
            <config n="0" include="Systems/flight-recorder/flight-recorder.xml">
                <name type="string">Cessna 172P Flight Recorder</name>
            </config>
        </flight-recorder>
        <engines>
            <engine n="0">
                <primer type="double">0</primer>
                <primer-lever type="bool">false</primer-lever>
                <use-primer type="bool">false</use-primer>
            </engine>
            <current-engine>
                <throttle type="double">0.0</throttle>
                <mixture type="double">0.0</mixture>
            </current-engine>
        </engines>
        <circuit-breakers>
            <autopilot type="bool">true</autopilot>
            <bcnlt type="bool">true</bcnlt>
            <flaps type="bool">true</flaps>
            <instr type="bool">true</instr>
            <intlt type="bool">true</intlt>
            <landing type="bool">true</landing>
            <master type="bool">true</master>
            <navlt type="bool">true</navlt>
            <pitot-heat type="bool">true</pitot-heat>
            <radio1 type="bool">true</radio1>
            <radio2 type="bool">true</radio2>
            <radio3 type="bool">true</radio3>
            <radio4 type="bool">true</radio4>
            <radio5 type="bool">true</radio5>
            <strobe type="bool">true</strobe>
            <turn-coordinator type="bool">true</turn-coordinator>
        </circuit-breakers>
        <switches>
            <master-avionics type="bool">false</master-avionics>
            <master-gear type="bool">false</master-gear>
            <starter type="bool">false</starter>
            <master-alt type="bool">false</master-alt>
            <master-bat type="bool">false</master-bat>
            <magnetos type="int">0</magnetos>
            <dome-red type="int">0</dome-red>
            <dome-white type="bool">false</dome-white>
        </switches>
        <lighting>
            <nav-lights type="bool">false</nav-lights>
            <beacon type="bool">false</beacon>
            <strobe type="bool">false</strobe>
            <taxi-light type="bool">false</taxi-light>
            <landing-lights type="bool">false</landing-lights>
            <instruments-norm type="double">0.0</instruments-norm>
            <radio-norm type="double">0.0</radio-norm>
            <dome-white-norm type="double">1.0</dome-white-norm>
            <gps-norm type="double">0.0</gps-norm>
            <gearled type="bool">true</gearled>
        </lighting>
    <instrumentation>
        <kma20 include="Aircraft/Instruments-3d/kma20/kma20init.xml"/>
        <attitude-indicator>
            <config>
                <tumble-flag archive="y" type="bool">true</tumble-flag>
            </config>
        </attitude-indicator>
        <encoder>
            <serviceable type="bool">true</serviceable>
        </encoder>
        <adf n="0">
            <ident-audible type="bool">false</ident-audible>
            <volume type="double">0.7</volume>
            <frequencies>
                <dial-1-khz type="int">0</dial-1-khz>
                <dial-100-khz type="int">0</dial-100-khz>
                <standby-khz type="double">200.0</standby-khz>
                <selected-khz type="double">200.0</selected-khz>
            </frequencies>
        </adf>
        <comm n="0">
            <power-btn type="bool">1</power-btn>
            <frequencies>
                <dial-khz type="int">0</dial-khz>
                <dial-mhz type="int">0</dial-mhz>
            </frequencies>
            <volume-selected type="double">0.7</volume-selected>
            <channel-mode-selector type="bool">1</channel-mode-selector>
        </comm>
        <comm n="1">
            <power-btn type="bool">1</power-btn>
            <frequencies>
                <dial-khz type="int">0</dial-khz>
                <dial-mhz type="int">0</dial-mhz>
            </frequencies>
            <volume-selected type="double">0.7</volume-selected>
            <channel-mode-selector type="bool">1</channel-mode-selector>
        </comm>
        <nav n="0">
            <volume type="double">0.7</volume>
            <frequencies>
                <dial-khz type="int">0</dial-khz>
                <dial-mhz type="int">0</dial-mhz>
            </frequencies>
            <ident-audible type="bool">false</ident-audible>
        </nav>
        <nav n="1">
            <volume type="double">0.7</volume>
            <frequencies>
                <dial-khz type="int">0</dial-khz>
                <dial-mhz type="int">0</dial-mhz>
            </frequencies>
            <ident-audible type="bool">false</ident-audible>
        </nav>
        <magnetic-compass>
            <pitch-offset-deg type="double">-2.7</pitch-offset-deg>
        </magnetic-compass>
        <airspeed-indicator>
            <serviceable type="bool">true</serviceable>
        </airspeed-indicator>
        <save-switches-state type="bool">false</save-switches-state>
    </instrumentation>
    <nasal>
        <c172p>
            <file>Nasal/kma20.nas</file>
            <file>Nasal/ki266.nas</file>
            <file>Nasal/kx165a.nas</file>
            <file>Nasal/engine.nas</file>
            <file>Nasal/avionics.nas</file>
            <file>Nasal/interior-lighting.nas</file>
        </c172p>
        <kr87>
            <file>Nasal/kr87.nas</file>
        </kr87>
    </nasal>
    <systems>
        <electrical>
            <outputs>
                <flaps type="double">0.0</flaps>
                <hydraulic-pump type="float">0.0</hydraulic-pump>
                <gear-select type="float">0.0</gear-select>
                <gear-advisory type="float">0.0</gear-advisory>
                <beacon-norm type="float">0.0</beacon-norm>
            </outputs>
            <save-battery-charge type="bool">false</save-battery-charge>
        </electrical>
    </systems>
dany93 commented 1 year ago

If I delete (comment) both of these two lines in the aircraft-data/c172p-fg1000-kap.xml file (or-gfc.xml) like this

    <transponder>
      <inputs>
        <!-- <knob-mode type="int">4</knob-mode>
        <ident-btn type="bool">false</ident-btn> -->
        <digit type="int">0</digit>
        <digit n="1" type="int">0</digit>
        <digit n="2" type="int">2</digit>
        <digit n="3" type="int">1</digit>
      </inputs>
    </transponder>

The FG1000 responds (works). With none of the previously seen error messages.

Just as a clue in the hope it can help, because I don't understand.

wlbragg commented 1 year ago

Wow, ok, I think this will support my hypothesis of what is going on. Thanks.

This also corrects the fg1000 aircraft not loading a second time after writing to aircraft data?

dany93 commented 1 year ago

This also corrects the fg1000 aircraft not loading a second time after writing to aircraft data?

Not exactly. This corrects the FG1000 glass panel not working a second time after writing to aircraft data.

Otherwise, the issue at second time is not that the fg1000 aircraft doesn't load (it loads and fly) but that the FG1000 glass panel doesn't respond to main knobs and that it's indications don't change, don't work.

@dany93 wrote: Almost no animation works, except for the NAV1 NAV2 and VOL. Particularly, the HDG knob changes the property values, but it gives no animation of the green bug. The ALT knob seems doing nothing. And nothing changes in flight (no airspeed, no Alt indication).

wlbragg commented 1 year ago

OK I think I got it. So remove those lines and your MFD/PFD work as they are supposed to, even after loading a second time. I'm planning on getting to this starting this next week. I hope to have it cleaned up so you can test to see if everything works as expected by the end of the week.

dany93 commented 1 year ago

I don't know what to do for this merge request. I think the essentials work, as far as your original subject (hardware animations...) is concerned.

If you can tell me...

(is this FG1000 feature compatible with FG 2020.3?)

wlbragg commented 1 year ago

@dany93 I just tested this on 2020.3 and it is fully compatible. We jsat need to change the minimum-fg-version from 2020.4.0 to 20202.3 so as not to get the warning about it not being compatible. But it all works, afaik. I tested lighting, panel objects, anything I could think of that might rely on newer additions to the core. It all works.

As far as the "clearing of the aircraft cache", we've run into that before and I don't know what all we can do about it. Thinking about it though, we can read and write to that cache. I suspect we could clear it in the c172p code, the difficulty might be in determining when it needs to be cleared. I'd have to test what all we can do with the read/write options to cache. It might be as simple as looking for a particular "new" property in the cache file and if it is not there, then delete the cache file. We might be able to add a persistent version property to the cache so in the future we can handle these instances where it needs cleared in the code. Regardless, I think when it happens from updates and code changes, and even if we can't auto deal with it, then I guess we just have to do it and let user know when they come across an issue. The version property being cached might help solve this for us in the future. We should be able to write code to check it and clear it if current and cached versions don't match. But that might not be the total solution either because of timing of when a cache issue actually causes the problem. Timing, as in, if it crashes before code can check to prevent it. It might need to be a check in the core at a certain startup process. If we can identify exactly when it happens and then reproduce it on demand, then I think we would be in a better position to look for a solution.

dany93 commented 1 year ago

@wlbragg Hi, just tell me if and when you think it can be merged.

Most of my tests are in this message. If that's enough...

wlbragg commented 1 year ago

@dany93 if I correct the issue that you have with

If I delete (comment) both of these two lines in the aircraft-data/c172p-fg1000-kap.xml file (or-gfc.xml) like this

<inputs>
<!-- <knob-mode type="int">4</knob-mode>
<ident-btn type="bool">false</ident-btn> -->
<digit type="int">0</digit>
<digit n="1" type="int">0</digit>
<digit n="2" type="int">2</digit>
<digit n="3" type="int">1</digit>
</inputs>
</transponder>

Will you be able to recreate and test that I indeed fixed it?

Also,

Some others are not your subject, but problems in the FG1000 (functions not working properly, like the map, or the slip-skid ball, inverted and not sensitive enough).

Did you turn the range up on the map to verify it isn't moving. I thought maybe mine was not working as well until I turned up the range. If it indeed isn't moving, is this even after you clear the cache and eliminate the errors?

What "slip ball"? In the fg1000? Inverted? Can you explain why you think the sensitivity is too low? I have no problem with you adjusting the sensitivity if you think it is wrong. You could either add a new issue or just fix it here. I have couple really small items I don't want to create an issue for so I am committing them under the PR this is attached to.

dany93 commented 1 year ago

@wlbragg wrote

Will you be able to recreate and test that I indeed fixed it?

Of course. I lastly reproduced the failure. Also, functioning after deleting the lines.

Did you turn the range up on the map to verify it isn't moving

I do not need to. The map is moving and the range (zoom) changes. But by observing more carefully, I noticed that the "Airspace-class limits" do not follow, no longer match the map limits when zooming. Which is that confused me and is wrong. This is independent from PFD failure (linked to aircraft-data/c172p-fg1000-kap.xml file). FG1000-map-04 FG1000-map-02 FG1000-map-01 FG1000-map-03

dany93 commented 1 year ago

@wlbragg wrote

What "slip ball"? In the fg1000? Inverted? You could either add a new issue or just fix it here.

Yes, the slip ball in the FG1000. Inverted (objectively) and too low sensitivity (estimated).

I had difficulty at finding where it is. All the more that the file location had been changed. It is in flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas

line 350, initial:

     me.getElement("SlipSkid")
      .setTranslation(slip * 10, 0);

I've changed it for (subjectively for the sensitivity): 

    me.getElement("SlipSkid")
      .setTranslation(-slip * 40, 0)

But only in my local files for testing, I cannot propose it for your PR, it is in the flightgear/fgdata part. Not in the c172p.

wkitty42 commented 1 year ago

On 7/5/23 11:06 AM, dany93 wrote:

It is in flightgear/fgdata/Aircraft/Instruments-3d/FG1000/Nasal/MFDPages/PFDInstruments/PFDInstruments.nas

since that's in FGData, i suggest the issue be pointed out on the FG issue tracker so the dev (richard? stuart?) that did the 1000 might take a look at it... idk...

wlbragg commented 1 year ago

@dany93 I haven't put the fg1000 through its paces, I really don't know if anyone has really tested it thoroughly. Not just the one installed in the 172, but the system in general. These issue would need to be addressed by Stuart. It shouldn't affect our implementation here. So for now I think a separate issue logging the fg1000 issues would suffice so we don't forget about them and help Stuart eventually address them. @wkitty42 Yes, I'll try to remember to let @stuartbuchanan know.

dany93 commented 1 year ago

@wlbragg So, what's next? Will you try to fix the fgdata file issue prior to merging?

This branch is older than the one recently merged from Issue #1414 , PR #1416. Is there a risk? However, PR #1412 is written as "no conflicts". Does git manages this well?

wlbragg commented 1 year ago

Will you try to fix the https://github.com/c172p-team/c172p/issues/1410#issuecomment-1618878934 prior to merging?

Not necessarily, but maybe, if I can get Sturat to address it prior to us wrapping this up.

Is there a risk?

No I don't think in this case there is a risk. Yes git manages this well and in every case I am aware of will report issues.

The saved date cache issue, your reproducible error, this is something I might be able to mitigate by separating the variant data more completely, this is my main concern. I feel this is loosely related to this, because you got this error when trying to update your local version with this issue data, correct?

I'm not sure why that triggered your cache error. But I would like to correct that and I think it is the breakout of variant data to their own variants, not done in this issue or PR. Why does that rear its head when you incorporate this data and test this issue?

wlbragg commented 1 year ago

your reproducible error Is this only when starting the fg1000-kap version? fg1000-gfc works ok?

And after you delete it, how does that work? You delete the lines and then start the sim, it works fine from that point forward, or does it have issues after it writes to the cache again and you start it the next time?

dany93 commented 1 year ago

because you got this error when trying to update your local version with this issue data, correct?

Sorry, I don't understand. I probably merely imported the branch, as usually. I did not, I do not, have this issue with master or other branches. I have this only with aircraft=c172p-fg1000-kap, aircraft=c172p-fg1000-gfc, for FG1000 PFD.

Previously, I think I merely didn't try the FG1000 with previous c172p versions, even if they included the FG1000. Except a long time ago, when my computer was too weak.

wlbragg commented 1 year ago

I was testing and the transponder is active in the fg1000. What happens when you change the transponder digits and exit the sim then restart? is all well? The fg1000 uses the same transponder code as the non-fg1000 variants.

wlbragg commented 1 year ago

I probably merely imported the branch, as usually.

This is the part of git I am not familiar with. So from your end you go to https://github.com/c172p-team/c172p/tree/Issue-1413 and import that code, right?

dany93 commented 1 year ago

Is this only when starting the fg1000-kap version? fg1000-gfc works ok?

Both give the issue.

And after you delete it, how does that work?

It works once. Not the next time.

You delete the lines and then start the sim, it works fine from that point forward, or does it have issues after it writes to the cache again and you start it the next time?

After deleting the lines, it works only once. It have the issue after it writes to the cache again and I start it the next time.

wlbragg commented 1 year ago

That makes, no sense whatsoever. Not on you, I can't understand why this is an issue at all. It's just saved data that is actually supposed to be there.

If you can when you have time,

What happens when you change the transponder digits and exit the sim then restart?

dany93 commented 1 year ago

This is the part of git I am not familiar with. So from your end you go to https://github.com/c172p-team/c172p/tree/Issue-1413 and import that code, right?

I do:

git fetch origin

git remote show origin

git checkout Issue-1410

wlbragg commented 1 year ago

OK, same thing, I guess.

I compared our saved data caches, yours is different a few entries before the transponder. You have

    <attitude-indicator>
    </attitude-indicator>

I have

    <attitude-indicator>
      <horizon-offset-deg type="double">-5.6</horizon-offset-deg>
    </attitude-indicator>

I'm searching now to see what this might be.

wlbragg commented 1 year ago

That was just me changing the setting I guess.

wlbragg commented 1 year ago

There is another difference, in transponder, you have knob-mode 4, mine is set to 3. I am checking now to see what knob-mode is?