Menu ▾ ▴

#2058 AW won't start in-sim when autostart is disabled in launcher

2018.3.0
Fixed
nobody
Launcher (39) Weather (49)
Low
2018-10-06
2018-09-19
Mihajlo
No

When AW autostart is disabled in launcher AW won't start when selected from the weather dialog. I get the same message that Jonathan has in this thread: https://forum.flightgear.org/viewtopic.php?f=69&t=34783.
Wkitty has already written steps to reproduce it in the thread and in the mailing list.

Discussion

  • James Turner

    James Turner - 2018-09-19

    The forum link isn't working for me, can you past the description / steps here? (In general tickets should be the primary source of information, so all the information about a problem is here when trying to investigate).

    Unfortunartely I think I missed the emails Wkitty wrote about this issue, since this is the first I heard of it.

     

    • Mihajlo

      Mihajlo - 2018-09-19

      he forum link is working now.
      the following is from the forums...

      CAT II / IIIb - what's going on?
      https://forum.flightgear.org/viewtopic.php?f=69&t=34783

      this is my finding when testing the described scenario... look closely at the
      console entries generated when we try to turn on AW... there is a repeat of some
      that have already been done in the first code block... for some reason, some
      init routines get executed a second time but that's another problem to the main
      one with AW not having the proper index in local_weather.nas...

      [quote="wkitty42";p=336518]
      FWIW: i have to say that they're working OK for me, too... i have the latest
      2018.3.0 beta code from the repos... i start with the launcher with AW enabled
      and live METAR data... once the sim is running, i go to
      F10->Environment->Weather, switch the "Weather conditions" drop box from "Live
      data" to "CAT II minimum" and click on the [OK] button... i repeated the moves
      and this time selected "CAT IIIb minimum"... there is a very noticeable lack of
      visibility in CATIIIb than CATII...

      here're my CATII and CATIIIb METAR strings...
      [code]
      CATII: XXXX 012345Z 15010KT 0400 -RA BKN001 OVC002 08/06 Q0990
      CATIIIb: XXXX 012345Z VRB01KT 0100 -RA FG OVC001 OVC002 02/02 Q0990
      [/code]

      EDIT: Mihajlo posted while i was writing the above... i'm testing Mihajlo's
      scenario now... will be back with updates...

      EDIT2: ok, yes... there is a problem if FG is started with the launcher and the
      launcher is set with AW off... when you get into FG and go to turn on AW, you
      get the following as well as the message on screen about the local weather being
      aborted... it is important that it says local weather... this does not happen if
      you try a second time to turn on AW in the sim...

      here's the sequence from the command line...

      start the launcher "FGFS --launcher"
      check that Weather->Active Weather is turned off
      click [Fly!] button
      FG loads with basic weather and the following console output...
      [code]
      [...]
      Reading materials from
      /home/myuser/flightgear-dev/fgdata-ng/Materials/regions/materials.xml
      Reading systems from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/Generic/generic-systems.xml"
      Initializing HUD Instrument
      Reading sound sound from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/ufo/ufo-sound.xml"
      Creating subsystems took:3798
      Splash screen progress binding-subsystems
      Volcanic activity on.
      Submodels: Unable to read AI submodel list
      setWeight() - not supported for ufo
      [/code]

      now, in-sim, F10->Environment->Weather-> enable AW->click [OK] adds the
      following to the above...
      [code]
      Request detected to initialize Advanced Weather on startup...
      Loading local weather routines...
      Starting hard-coded terrain presampling
      Nasal runtime error: vector index 0 out of bounds (size: 0)
      at
      /home/myuser/flightgear-dev/fgdata-ng/Nasal/local_weather/local_weather.nas,
      line 390
      called from:
      /home/myuser/flightgear-dev/fgdata-ng/Nasal/local_weather/local_weather.nas,
      line 3868
      called from: __dlg:weather, line 175
      Reading materials from
      /home/myuser/flightgear-dev/fgdata-ng/Materials/regions/materials.xml
      Reading systems from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/Generic/generic-systems.xml"
      Initializing HUD Instrument
      Reading sound sound from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/ufo/ufo-sound.xml"
      Creating subsystems took:3798
      Splash screen progress binding-subsystems
      Volcanic activity on.
      Submodels: Unable to read AI submodel list
      setWeight() - not supported for ufo
      [/code]

      AW is not active even though the dialog says it is... you have to run the dialog
      a second time and click [OK] and then AW starts as desired... this was also
      started from in the sim and NOT a "request to initialize AW on startup" like the
      message(s) say...
      [/quote]
      From Thorsten:
      The launcher thing is probably easy - one of you can have a go at it - look closely at everything that calls set_tile() - probably the call is duplicated when the property set by the launcher changes to true in-sim

       

  • Mihajlo

    Mihajlo - 2018-09-19

    The forum link is working now.
    the following is from the forums...

    CAT II / IIIb - what's going on?
    https://forum.flightgear.org/viewtopic.php?f=69&t=34783

    this is my finding when testing the described scenario... look closely at the
    console entries generated when we try to turn on AW... there is a repeat of some
    that have already been done in the first code block... for some reason, some
    init routines get executed a second time but that's another problem to the main
    one with AW not having the proper index in local_weather.nas...

    [quote="wkitty42";p=336518]
    FWIW: i have to say that they're working OK for me, too... i have the latest
    2018.3.0 beta code from the repos... i start with the launcher with AW enabled
    and live METAR data... once the sim is running, i go to
    F10->Environment->Weather, switch the "Weather conditions" drop box from "Live
    data" to "CAT II minimum" and click on the [OK] button... i repeated the moves
    and this time selected "CAT IIIb minimum"... there is a very noticeable lack of
    visibility in CATIIIb than CATII...

    here're my CATII and CATIIIb METAR strings...
    [code]
    CATII: XXXX 012345Z 15010KT 0400 -RA BKN001 OVC002 08/06 Q0990
    CATIIIb: XXXX 012345Z VRB01KT 0100 -RA FG OVC001 OVC002 02/02 Q0990
    [/code]

    EDIT: Mihajlo posted while i was writing the above... i'm testing Mihajlo's
    scenario now... will be back with updates...

    EDIT2: ok, yes... there is a problem if FG is started with the launcher and the
    launcher is set with AW off... when you get into FG and go to turn on AW, you
    get the following as well as the message on screen about the local weather being
    aborted... it is important that it says local weather... this does not happen if
    you try a second time to turn on AW in the sim...

    here's the sequence from the command line...

    1. start the launcher "FGFS --launcher"
    2. check that Weather->Active Weather is turned off
    3. click [Fly!] button

    4. FG loads with basic weather and the following console output...
      [code]
      [...]
      Reading materials from
      /home/myuser/flightgear-dev/fgdata-ng/Materials/regions/materials.xml
      Reading systems from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/Generic/generic-systems.xml"
      Initializing HUD Instrument
      Reading sound sound from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/ufo/ufo-sound.xml"
      Creating subsystems took:3798
      Splash screen progress binding-subsystems
      Volcanic activity on.
      Submodels: Unable to read AI submodel list
      setWeight() - not supported for ufo
      [/code]

    5. now, in-sim, F10->Environment->Weather-> enable AW->click [OK] adds the
      following       to the above...
      [code]
      Request detected to initialize Advanced Weather on startup...
      Loading local weather routines...
      Starting hard-coded terrain presampling
      Nasal runtime error: vector index 0 out of bounds (size: 0)
      at
      /home/myuser/flightgear-dev/fgdata-ng/Nasal/local_weather/local_weather.nas,
      line 390
      called from:
      /home/myuser/flightgear-dev/fgdata-ng/Nasal/local_weather/local_weather.nas,
      line 3868
      called from: __dlg:weather, line 175
      Reading materials from
      /home/myuser/flightgear-dev/fgdata-ng/Materials/regions/materials.xml
      Reading systems from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/Generic/generic-systems.xml"
      Initializing HUD Instrument
      Reading sound sound from Path
      "/home/myuser/flightgear-dev/fgdata-ng/Aircraft/ufo/ufo-sound.xml"
      Creating subsystems took:3798
      Splash screen progress binding-subsystems
      Volcanic activity on.
      Submodels: Unable to read AI submodel list
      setWeight() - not supported for ufo
      [/code]

    AW is not active even though the dialog says it is... you have to run the dialog
    a second time and click [OK] and then AW starts as desired... this was also
    started from in the sim and NOT a "request to initialize AW on startup" like the
    message(s) say...
    [/quote]
    From Thorsten:
    The launcher thing is probably easy - one of you can have a go at it - look closely at everything that calls set_tile() - probably the call is duplicated when the property set by the launcher changes to true in-sim

     

  • Mihajlo

    Mihajlo - 2018-09-19

    Sorry, the link is dead again.

     

  • xDraconian

    xDraconian - 2018-09-26
    • labels: --> Launcher, Weather
     

  • Thorsten Renk

    Thorsten Renk - 2018-10-06
    • status: New --> Fixed
     

Log in to post a comment.

MongoDB Logo MongoDB