Page 1 of 4
most anoying error
Posted: Tue Aug 30, 2016 10:28 pm
by bomber
Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN
Re: most anoying error
Posted: Tue Aug 30, 2016 10:32 pm
by IAHM-COL
Don't know what is that for (what your goal is)
But sometimes I just send a conditional to verify a property with nasal, and avoid code mess
it looks kinda like this
Code: Select all
if (is.valid (property---)){
getprop (property(
}
Re: most anoying error
Posted: Tue Aug 30, 2016 10:36 pm
by IAHM-COL
the example. accurately is:
Code: Select all
if(getprop('/engines/engine[1]/thrust_lb')!=nil) {
setprop('/instrumentation/mfd/thrust1', getprop('/engines/engine[1]/thrust_lb') / 2000);
}
Re: most anoying error
Posted: Tue Aug 30, 2016 10:43 pm
by bomber
I'm not writing nasal... this is the error message I get from my current fdm.
Re: most anoying error
Posted: Tue Aug 30, 2016 11:11 pm
by IAHM-COL
I did not know that FDMs made getprop nasal codes.
Thus, I suspect the problem is not inherently inside the FDM you are modifying.
Re: most anoying error
Posted: Thu Sep 01, 2016 7:46 am
by jwocky
Where did you get this? It's definitively not from the FDM but from some Nasal listening in on properties.
Re: most anoying error
Posted: Thu Sep 01, 2016 12:06 pm
by bomber
I get it in my debug window once FG has crashed
Re: most anoying error
Posted: Thu Sep 01, 2016 2:09 pm
by jwocky
Okay, which plane? When does it happen, a hint about the situation in which this error comes up?
Re: most anoying error
Posted: Thu Sep 01, 2016 3:47 pm
by bomber
It's my new experimental fdm for the beagle.... and normally occurs when the plane is spinning out of control.
Re: most anoying error
Posted: Thu Sep 01, 2016 4:00 pm
by jwocky
I think, you are looking for a nasal listener and the error happens in the routine the listener calls. Can be it is one of the automatically loaded Nasals from FGDATA, those go also worse version by version.