Nasal Error over MP

[legoboyvdlp]

Nasal runtime error: nil used in numeric context at C:/Users/redpa/Documents/Programs/FlightGear 2018.3.0/data/Nasal/bits.nas, line 8 called from: C:/Users/redpa/Documents/FlightGear/Custom Aircraft/c172p/Models/c172p.ac, line 36 called from: C:/Users/redpa/Documents/Programs/FlightGear 2018.3.0/data/Nasal/globals.nas, line 119 Nasal runtime error: nil used in numeric context at C:/Users/redpa/Documents/Programs/FlightGear 2018.3.0/data/Nasal/bits.nas, line 8 called from: C:/Users/redpa/Documents/FlightGear/Custom Aircraft/c172p/Models/c172p.ac, line 54 called from: C:/Users/redpa/Documents/Programs/FlightGear 2018.3.0/data/Nasal/globals.nas, line 119

Someone at KSFO had a c172p: I noticed this error. I take it this is a version incompatiability problem, not something to worry about?

[wlbragg]

Hum, any chance you could bring this up on the dev list, unless someone here knows much about the internals of MP? I can't comfortably answer your question.

Do you have any other information about the other c172p, version, etc? Or what MP compatibility mode you both were using?

[onox]

@legoboyvdlp If you open the pilot list, you can see a "2" in the "version" column if a user uses the 2017.2+ MP protocol, or nothing if using the older protocol.

I think the user probably used the old MP protocol.

[onox]

We can avoid bits.nas by using booleans. I already converted the securing attributes in the branch of issue #1011. See https://github.com/c172p-team/c172p/commit/ef0299c5d1894790e41ee1db4bfb358c1ee182cf

[legoboyvdlp]

Perhaps we could add a warning if FlightGear detects that the old protocol is being used?

[onox]

@legoboyvdlp I've already added that: see https://github.com/c172p-team/c172p/commit/430dbadeb95f598c39eac2c1f3a780b581dc064d