Menu

#1862 Nasal runtime error in adv. weather

2020.4
Accepted
nobody
Weather (49)
Low
2024-10-21
2016-04-07
No

I am using advanced weather and Terrasync:

1: I loaded up at KXTA
2: I set "marginal VFR" metar on.
3: I switched location to KNUQ while the weather dialog was open.

Using 2016.2.0 build today on windows 7 I got this:

Nasal runtime error: setprop() value is not string or number
at C:/Program Files/FlightGear 2016.2.0/data/Nasal/local_weather/weather_tile_management.nas, line 232
called from: C:/Program Files/FlightGear 2016.2.0/data/Nasal/local_weather/local_weather.nas, line 3219
called from: C:/Program Files/FlightGear 2016.2.0/data/Nasal/local_weather/local_weather.nas, line 4179
called from: C:/Program Files/FlightGear 2016.2.0/data/Nasal/globals.nas, line 119

Discussion

  • Nikolai V. Chr.

    Nikolai V. Chr. - 2016-04-07

    Oops, I noticed the was stuff before that:

    Tile direction 0 not generated!
    Flag: 0
    Nasal runtime error: vector index -1 out of bounds (size: 1)
    at C:/Program Files/FlightGear 2016.2.0/data/Nasal/local_weather/local_weather.nas, line 390
    called from: C:/Program Files/FlightGear 2016.2.0/data/Nasal/local_weather/local_weather.nas, line 861
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Tile direction 0 not generated!
    Flag: 0
    Starting hard-coded terrain presampling
    Starting hard-coded terrain presampling
    4166.666666666667
    2333.333333333333
    4166.666666666667
    2333.333333333333

     
  • xDraconian

    xDraconian - 2018-09-30
    • labels: --> Metar, Nasal
     
  • Thorsten Renk

    Thorsten Renk - 2018-10-03

    AW does not support teleportation - that has never worked and never will because it creates weather around you - since the launcher now allows you to start with AW already running, if you teleport after such a startup you will crash AW and need to restart.

    (I believe if the reset would trigger a Nasal re-init, the problem would not occur).

     

    Last edit: Thorsten Renk 2018-10-03
  • legoboyvdlp

    legoboyvdlp - 2020-08-06
    • Milestone: None --> 2020.2
     
  • James Turner

    James Turner - 2020-08-06

    Reset does a Nasal re-init, but 'relocate' (reposition) doesn't. Maybe we could disable AW before doing a repostion, and re-enable it afterwards?

     
    • Frederic Türpe

      Frederic Türpe - 2024-10-21

      Has this been done yet ?

       
  • James Turner

    James Turner - 2020-08-06

    Also, I'm confused how this could show up as 'setprop' being undefined, that seems like something more fundamental going wrong.

     
  • Gijs

    Gijs - 2024-01-23
    • labels: Metar, Nasal --> Weather
    • status: New --> Accepted
    • Milestone: 2020.2 --> 2020.4
     
  • Gijs

    Gijs - 2024-01-23

    Can confirm on current next. The actual error is now:

    Nasal runtime error: vector index -1 out of bounds (size: 1)
      at fgdata/Nasal/local_weather/local_weather.nas, line 389
      called from: fgdata/Nasal/local_weather/local_weather.nas, line 881
    
     

Log in to post a comment.

MongoDB Logo MongoDB