Board index FlightGear Development Aircraft Systems

747 8i startup issue  Topic is solved

Modeling aircraft systems, like electrical stuff, hydraulics, pneumatics? Feel free to ask support.

747 8i startup issue

Postby Volador » Sat Nov 20, 2021 11:48 pm

Yes, I use the autostart (please don't judge me ) the 747-8i seems to have now disabled the autostart, even trying to start manually has not worked either but the instructions are fairly limited and assume you know where certain switches are (or they're not labelled as in the instructions) :(
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby Volador » Sun Nov 21, 2021 9:32 am

Might it be something to do with having nightly build?
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby wkitty42 » Sun Nov 21, 2021 12:49 pm

as always, what does the FG log file tell you?
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9162
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 22.04

Re: 747 8i startup issue

Postby Volador » Sun Nov 21, 2021 4:53 pm

Hi Wkitty, always the voice of reason :) The log file probably says a lot of thing that go over my head but the warnings [WARN] and [ALRT] cut from the log are: (If there's a better way to share a log file please let me know)

Code: Select all
 11.06 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2608: multiple values forbidden for option:httpd, ignoring:8080
 
   11.16 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_props.cxx:205: Unknown logging priority: 5
 
   11.25 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:806: Enabling ATI/AMD viewport hack
 
   11.95 [ALRT]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\scenery.cxx:319: Unexpected property in listener /scenery[0]/elevation-mesh[0]/lod-range-factor[0]
   11.95 [ALRT]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\scenery.cxx:319: Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/detailed[0]
   11.95 [ALRT]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\scenery.cxx:319: Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/rough-delta[0]
   11.95 [ALRT]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\scenery.cxx:319: Unexpected property in listener /sim[0]/rendering[0]/static-lod[0]/bare-delta[0]
 
   15.45 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_props.cxx:205: Unknown logging priority: 5

   16.05 [WARN]:network   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Network\generic.cxx:758: Couldn't find protocol file for 'fgcom-mumble.xml'
   16.05 [ALRT]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_io.cxx:401: Failed to parse config=generic,socket,out,10,127.0.0.1,16661,udp,fgcom-mumble
   16.05 [ALRT]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_io.cxx:384: add_channel() failed. config=generic,socket,out,10,127.0.0.1,16661,udp,fgcom-mumble

   16.38 [INFO]:systems   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Systems\electrical.cxx:386: NOTICE: System manager configuration specifies an electrical system: Aircraft/Generic/generic-electrical.xml but it is being overridden by the one specified in the -set.xml file: Aircraft/747-8i/Systems/electrical.xml
   16.38 [WARN]:systems   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Systems\electrical.cxx:402: Reading deprecated xml electrical system model from
    D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Systems/electrical.xml
   16.46 [INFO]:cockpit   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Instrumentation\instrument_mgr.cxx:82: Reading instruments from Path "D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Systems/instrumentation.xml"
   16.46 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\install\msvc140-64\include\simgear/props/tiedpropertylist.hxx:59: Failed to tie property /instrumentation[0]/encoder[0]/setting-inhg[0]
   16.46 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\install\msvc140-64\include\simgear/props/tiedpropertylist.hxx:59: Failed to tie property /instrumentation[0]/encoder[0]/setting-hpa[0]
 
   16.91 [INFO]:sound     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Sound\fg_fx.cxx:132: Reading sound sound from Path "D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Sounds/747-sound.xml"
   16.91 [WARN]:sound     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\sound\xmlsound.cxx:129:   Neither a condition nor a property specified in section:
   17.63 [ALRT]:io        C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\material\mipmap.cxx:272: mipmapping: texture size not a power-of-two: D:\FlightGear\Downloads\Aircraft\org.flightgear.fgaddon.trunk\Aircraft\747-8i\Models\Service\Pushback\pushback.png

   23.05 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture
   23.11 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[1]
   23.11 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[2]
   23.27 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /instrumentation[0]/altimeter[0]/setting-inhg[0]
   23.27 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /instrumentation[0]/altimeter[0]/setting-inhg[0]
   23.28 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[1]/empty[0]
   23.28 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[2]/empty[0]
   23.28 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[3]/empty[0]
   23.28 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[4]/empty[0]
   23.30 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: filtered_touchdown
   23.30 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 932
   23.30 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 848
   23.30 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 992
   23.30 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/system.nas, line 389
   23.32 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
   23.32 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/electrical.nas, line 697
   23.32 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/electrical.nas, line 722

   23.80 [ALRT]:input     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\SGBinding.cxx:52: No command supplied for binding.
   23.80 [ALRT]:input     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\SGBinding.cxx:52: No command supplied for binding.
   23.80 [ALRT]:input     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\SGBinding.cxx:52: No command supplied for binding.
   23.80 [ALRT]:input     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\SGBinding.cxx:52: No command supplied for binding.
   23.80 [ALRT]:input     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\SGBinding.cxx:52: No command supplied for binding.
 
   38.19 [ALRT]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\Version.cpp:40: This aircraft uses yasim version 'YASIM_VERSION_32' (1)

   38.19 [ALRT]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\FGFDM.cpp:331: This aircraft does not use the latest yasim configuration version.
   38.19 [WARN]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\FGFDM.cpp:612: YASIM warning: versions before 2017.2 are buggy for wings with camber=0
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:73: YASim solution results:
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:74:        Iterations: 2525
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:75:  Drag Coefficient: 11.0388
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:76:        Lift Ratio: 115.261
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:77:        Cruise AoA: 2.13697
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:78:    Tail Incidence: 2.0162
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:79: Approach Elevator: -0.519521
   39.44 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:85:             CG: 1.838, 0.000, -0.718
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
   39.44 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
   39.45 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Copilot ready
   39.45 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[3]
   39.46 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'sodipodi:namedview' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.46 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'metadata' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.46
   39.46 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element in <defs>: <path> [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.78 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\elements\CanvasElement.cxx:552: Canvas: invalid clip: 124, 1024, 1024, 0
   39.79 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[4]
   39.80 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'sodipodi:namedview' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.80 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'metadata' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.80 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element in <defs>: <path> [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   39.80 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element in <defs>: <path> [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingND.svg']
   40.08 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\elements\CanvasElement.cxx:552: Canvas: invalid clip: 124, 1024, 1024, 0
   40.09 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'sodipodi:namedview' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingAirplane.svg']
   40.09 [INFO]:nasal     C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/svg.nas:29: parsesvg: Skipping unknown element 'metadata' [path='C:/Program Files/FlightGear 2020.4/data/Nasal/canvas/map/Images/boeingAirplane.svg']
   40.09 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: AFDS System ... check
   40.09 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
   40.09 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 254
   40.09 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 320
   40.09 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 382
   40.09 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
 
   49.62 [WARN]:terrain   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:496: Path "D:/FlightGear/Downloads/TerraSync/Pylons/e010n40/e012n48/3154584.stg": Object at 12.026, 48.5 in incorrect bucket (12:0, 48:3) - should be in 3154592 (12:0, 48:4)
 
   54.41 [WARN]:terrain   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:496: Path "D:/FlightGear/Downloads/TerraSync/Terrain/e010n40/e011n48/3138185.stg": Object at 11.2483, 48.2068 in incorrect bucket (11:1, 48:1) - should be in 3138184 (11:0, 48:1)
 
   61.72 [WARN]:OSG       C:\Jenkins\workspace\Windows-nightly\install\msvc140-64\include\simgear/debug/OsgIoCapture.hxx:37: PNG lib warning : Interlace handling should be turned on when using png_read_image

   61.76 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: magic_autostart
   61.76 [INFO]:terrain   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:521: Loading stg file Path "D:/FlightGear/Downloads/TerraSync/Objects/e010n40/e012n47/3154552.stg"
   61.76 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at /sim/bindings/menu/binding[475], line 1
   61.76 [INFO]:terrain   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:521: Loading stg file Path "D:/FlightGear/Downloads/TerraSync/Terrain/e010n40/e012n47/3154552.stg"

  219.31 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Boeing747.magic_autostart();
  219.31 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: --------------------------------------------------------------------------------
  223.81 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: No such member: magic_autostart:
 at <nasal-console/#1>, line 1
  244.79 [INFO]:opengl    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\PUICamera.cxx:273: Deleting PUI camera
  244.82 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\globals.cxx:898: Saving user settings to Path "C:/Users/Win7/AppData/Roaming/flightgear.org/autosave_2020_4.xml"
  245.03 [INFO]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\terrain_stg.cxx:264: FGStgTerrain::shutdown - shutdown tilemgr
  245.04 [INFO]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\terrain_stg.cxx:233: FGStgTerrain::dtor
  256.42 [INFO]:input     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Input\FGHIDEventInput.cxx:944: HID event input shutting down
  256.42 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Network\props.cxx:811: closing FGProps
  256.42 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_io.cxx:470: Shutting down channel ""
  256.42 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Network\props.cxx:811: closing FGProps
  256.42 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_io.cxx:470: Shutting down channel "generic-1"
  256.43 [INFO]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_io.cxx:470: Shutting down channel "generic-2"
  256.43 [INFO]:terrasync C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\tsync\terrasync.cxx:1148: Shutdown
  256.56 [INFO]:systems   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Systems\electrical.cxx:365: Destroying elec system
  256.57 [INFO]:terrain   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scenery\SceneryPager.cxx:42: Destroying scenery pager

User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby V12 » Sun Nov 21, 2021 7:08 pm

Very strange ALRT on properties about LOD. I have this revision :

/sim/version/simgear: 2020.4.0
/sim/version/openscenegraph: 3.6.5
/sim/version/build-id: 4220
/sim/version/build-number: 4220
/sim/version/build-type: Nightly
/sim/version/revision: a7b972129639ccb375a196c7a41f184b815db006

and doesn't displays these alerts in the console.

EDIT :
FG2020.4.0 displays custom VHHX incorrectly and probably ignores LOD described properties. FG2020.3.11 works with it flawless.

Described alerts have not influence on 747 - 8i startup sequence.
Fly high, fly fast - fly Concorde !
V12
 
Posts: 2757
Joined: Thu Jan 12, 2017 5:27 pm
Location: LZIB
Callsign: BAWV12

Re: 747 8i startup issue

Postby Volador » Mon Nov 22, 2021 10:25 am

Hi V12 I looked up those properties you listed and these are my versions:
build-id = 4224
build-number = 4224
build-type = Nightly
flightgear = 2020.4.0
hla-support = false
openscenegraph = 3.6.5
revision = aad67cdad90a8c66a66a8e35b21212f6c3ed23ea
simgear = 2020.4.0

I've no clue how that info would help though?
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby V12 » Mon Nov 22, 2021 2:48 pm

Your FG is bit newer than my.

EDIT :

I tested 747-8i, she doesn't work in 2020.4.0. But in 2020.3.11 flawless.
Again - tax for developer's version :(
Fly high, fly fast - fly Concorde !
V12
 
Posts: 2757
Joined: Thu Jan 12, 2017 5:27 pm
Location: LZIB
Callsign: BAWV12

Re: 747 8i startup issue

Postby Volador » Tue Nov 23, 2021 6:51 pm

I think I may have had a less detailed log level set, I've found these warnings now and there seems to be loads of Nasal errors later on

Code: Select all
  104.39 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Loading local weather routines...
  104.40 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Animated jetways ... initialized
  104.45 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\elements\CanvasElement.cxx:259: addEventListener(/sim[0]/gui[0]/canvas[0], mousedown)
  104.47 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture
  104.52 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[1]
  104.52 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[2]
  104.76 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /instrumentation[0]/altimeter[0]/setting-inhg[0]
  104.76 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /instrumentation[0]/altimeter[0]/setting-inhg[0]
  104.89 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[1]/empty[0]
  104.89 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[2]/empty[0]
  104.89 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[3]/empty[0]
  104.89 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1763: ERROR: Cannot add listener to tied property /consumables[0]/fuel[0]/tank[4]/empty[0]
  104.91 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: filtered_touchdown
  104.91 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 932
  104.91 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 848
  104.91 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/aircraft.nas, line 992
  104.91 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/system.nas, line 389
  104.97 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
  104.97 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/electrical.nas, line 697
  104.97 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/electrical.nas, line 722
  104.97 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: 747-8 hydraulic system: so far so good
  105.15 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\FGPUIMenuBar.cxx:57: Initializing old dialog commands:
  139.22 [ALRT]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\Version.cpp:40: This aircraft uses yasim version 'YASIM_VERSION_32' (1)

  139.22 [ALRT]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\FGFDM.cpp:331: This aircraft does not use the latest yasim configuration version.
  139.23 [WARN]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\FGFDM.cpp:612: YASIM warning: versions before 2017.2 are buggy for wings with camber=0
  140.74 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:73: YASim solution results:
  140.74 [INFO]:flight    C:\Jenkins\workspace\Windows-nightly\flightgear\src\FDM\YASim\YASim.cxx:74:        Iterations: 2525
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: click
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/efis.nas, line 443
  140.74 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
  140.76 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Copilot ready
  140.77 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\canvas\Canvas.cxx:142: Canvas constructor: node=/canvas/by-index/texture[3]
  141.69 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: AFDS System ... check
  141.69 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
  141.69 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 254
  141.69 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 320
  141.69 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/fuel_system.nas, line 382
  141.69 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: C:/Program Files/FlightGear 2020.4/data/Nasal/globals.nas, line 137
  141.69 [INFO]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:557: Pilot dual control ... initialized
  153.54 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
  153.54 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/pneumatic.nas, line 69
  153.54 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/pneumatic.nas, line 243
  153.54 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/pneumatic.nas, line 314
  153.54 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/pneumatic.nas, line 320
  153.98 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: nil used in numeric context
  153.98 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   at D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/eicas.nas, line 204
  153.98 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1473:   called from: D:/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft/747-8i/Nasal/eicas.nas, line 310
  154.04 [INFO]:aircraft  C:\Jenkins\workspace\Windows-nightly\flightgear\src\Model\modelmgr.cxx:145: Adding model Models/Weather/lightning_combined.xml


and the magic autostart...

Code: Select all
162.02 [ALRT]:nasal     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Scripting\NasalSys.cxx:1457: Nasal runtime error: No such member: magic_autostart
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby Volador » Fri Nov 26, 2021 9:20 pm

Still no joy. re-downloaded the aircraft too.
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: 747 8i startup issue

Postby TheEagle » Sat Nov 27, 2021 5:10 pm

I'll try if I can start it.
Cessna 210 (Wiki)
My other aircraft: my wiki profile !
Other: FGTools (GitHub)
World tour: View on SkyVector
Please consider donating $1 / €1 to help me finance a new camera !
User avatar
TheEagle
 
Posts: 3433
Joined: Sat May 01, 2021 3:27 pm
Location: France
Pronouns: You, he
Callsign: F-EAGLE
IRC name: none
Version: Git next
OS: Ubuntu Studio 22.04

Re: 747 8i startup issue

Postby TheEagle » Sat Nov 27, 2021 5:27 pm

Autostart works for me. But the change date of the folder is 31.08.21 for me - I'll remove it and see if a newer version is downloaded.
Cessna 210 (Wiki)
My other aircraft: my wiki profile !
Other: FGTools (GitHub)
World tour: View on SkyVector
Please consider donating $1 / €1 to help me finance a new camera !
User avatar
TheEagle
 
Posts: 3433
Joined: Sat May 01, 2021 3:27 pm
Location: France
Pronouns: You, he
Callsign: F-EAGLE
IRC name: none
Version: Git next
OS: Ubuntu Studio 22.04

Re: 747 8i startup issue

Postby TheEagle » Sat Nov 27, 2021 8:22 pm

I just got a fresh download from FGAddon, and for me on 2020.4.0 the autostart works fine (didn't try manual start :oops: )
Cessna 210 (Wiki)
My other aircraft: my wiki profile !
Other: FGTools (GitHub)
World tour: View on SkyVector
Please consider donating $1 / €1 to help me finance a new camera !
User avatar
TheEagle
 
Posts: 3433
Joined: Sat May 01, 2021 3:27 pm
Location: France
Pronouns: You, he
Callsign: F-EAGLE
IRC name: none
Version: Git next
OS: Ubuntu Studio 22.04

Re: 747 8i startup issue

Postby wlbragg » Sun Nov 28, 2021 4:03 am

I think the nasal electrical error is what is breaking the autostart. Or maybe a cascade type failure from the nasal tiresmoke. It's broke on recent next and aircraft out of fgaddon.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7609
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: 747 8i startup issue  

Postby wlbragg » Sun Nov 28, 2021 6:15 am

I verified that commenting out the tyresmoke new function in system.nas does fix the autostart function.
Code: Select all
#aircraft.tyresmoke_system.new(0, 1, 2, 3, 4);


I did not investigate why tyresmoke is not being found, only that this error is causing the rest of the errors, at least on my system.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7609
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: 747 8i startup issue

Postby Volador » Sun Nov 28, 2021 12:09 pm

wlbragg, you have restored the delicate balance of the FG universe once again! This works on my system, thank you :D
I just did a take-off from EDDM -I did only get 12 fps but that might be cranking up the clouds range (which look great by the way) for a bit of atmosphere, thanks again.
Chris
User avatar
Volador
 
Posts: 1142
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Next

Return to Systems

Who is online

Users browsing this forum: No registered users and 1 guest