most anoying error
most anoying error
Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN
"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell
Re: most anoying error
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
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(
}
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
Re: most anoying error
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);
}
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
Re: most anoying error
I'm not writing nasal... this is the error message I get from my current fdm.
"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell
Re: most anoying error
I did not know that FDMs made getprop nasal codes.
Thus, I suspect the problem is not inherently inside the FDM you are modifying.
Thus, I suspect the problem is not inherently inside the FDM you are modifying.
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
Re: most anoying error
Where did you get this? It's definitively not from the FDM but from some Nasal listening in on properties.
Free speech can never be achieved by dictatorial measures!
Re: most anoying error
I get it in my debug window once FG has crashed
"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell
Re: most anoying error
Okay, which plane? When does it happen, a hint about the situation in which this error comes up?
Free speech can never be achieved by dictatorial measures!
Re: most anoying error
It's my new experimental fdm for the beagle.... and normally occurs when the plane is spinning out of control.
"If anyone ever tells you anything about an aeroplane which is so bloody complicated you can't understand it, take it from me - it's all balls" - R J Mitchell
Re: most anoying error
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.
Free speech can never be achieved by dictatorial measures!
Return to “Aircraft Development”
Who is online
Users browsing this forum: No registered users and 14 guests