HHS wrote:helijah wrote:Hum... sorry HHS but I have always :
- Code: Select all
Nasal runtime error: nil used in numeric context
at /home/helijah/FlightGear/data/Aircraft/AirCrane/Nasal/afcs.nas, line 1024
called from: /home/helijah/FlightGear/data/Aircraft/AirCrane/Nasal/afcs.nas, line 1114
called from: /home/helijah/FlightGear/data/Nasal/globals.nas, line 100
and always with the double end of line (which is why the line 514 is indicated also in 1024). Anyway, I am eager to know what it brings;)
Best regards. Emmanuel
Better than the NaN's it produced before... I'm looking for a solution, but it needs time.
flyer5 wrote:Here's a quick fix:
http://www.mediafire.com/?sharekey=b659 ... f6e8ebb871
Extract to your AirCrane's Nasal folder.
The problem was that the file indicated "/controls/flight/fcs/cas/delta_yaw" where there was no such member. I followed the internal properties, and saw that there was no member "delta_yaw".
I adjusted it to simply "/controls/flight/fcs/cas/yaw", and error message is gone.
flyer5 wrote:Here's a quick fix:
http://www.mediafire.com/?sharekey=b659 ... f6e8ebb871
Extract to your AirCrane's Nasal folder.
The problem was that the file indicated "/controls/flight/fcs/cas/delta_yaw" where there was no such member. I followed the internal properties, and saw that there was no member "delta_yaw".
I adjusted it to simply "/controls/flight/fcs/cas/yaw", and error message is gone.
tat wrote:There are four similar fcs.nas (including afcs.nas) in CVS, and I need to update all these files. For better maintainability, I'll unite all these fcs.nas and let each aircraft change the parameters outside fcs.nas. I'll let you know when everything is done.
helijah wrote:Hi HHS,
have a afcs.nas file common to all aircraft using the same, does not every designer has to use that one
but at this time, the OH-1, The EC665 "Tigre", the AirCrane, the Dauphin and the Ka50 use a same file. Make a change on one of them forced to make the same change everywhere (with the risk of omission or error).
File maintenance becomes a problem:)
Best regards. Emmanuel
helijah wrote:Hey tat.
Wow. Good work
I have to update (on my hard drive only for now) the fcs.nas in my Ka50. So I placed the fcs.nas of the OH-1 in "/Aircraft/Instruments/fcs-generic/" and output management fcs of OH-1.nas to bring in fcs-management.nas (I like to separate the elements. This allows for easier re-use for everyone )
It works very well. I will now edit the Aircrane, SuperFrelon and other. Of course I expect to know if "/Aircraft/Instruments/fcs-generic/" location is suitable for everyone before putting it all in CVS.
Of course it remains to modify the parameters of fcs-management.nas to correspond to different helicopters .... hum ... and then my skills are limited But I'm sure some (HHS randomly ) will be happy to review all.
Best regards. Emmanuel
tat wrote:flyer5 wrote:Here's a quick fix:
http://www.mediafire.com/?sharekey=b659 ... f6e8ebb871
Extract to your AirCrane's Nasal folder.
The problem was that the file indicated "/controls/flight/fcs/cas/delta_yaw" where there was no such member. I followed the internal properties, and saw that there was no member "delta_yaw".
I adjusted it to simply "/controls/flight/fcs/cas/yaw", and error message is gone.
Hi,flyer5 wrote:Here's a quick fix:
http://www.mediafire.com/?sharekey=b659 ... f6e8ebb871
Extract to your AirCrane's Nasal folder.
The problem was that the file indicated "/controls/flight/fcs/cas/delta_yaw" where there was no such member. I followed the internal properties, and saw that there was no member "delta_yaw".
I adjusted it to simply "/controls/flight/fcs/cas/yaw", and error message is gone.
Your solution is not technically right. Changing that line may cause unexpected yaw maneuver in a very strong cross wind condition.
delta_yaw and yaw is very different. The former is a difference between expected yaw position and the current yaw position, and the latter is the yaw output of CAS. Therefore, referring yaw instead of delta_yaw is wrong.
The real problem here is that FCS unexpectedly calls update() function that applies CAS and SAS even when these are not initialized. FCS invokes update() every time /rotors/main/cone_deg is updated. However, the cone_deg property is
somehow updated even though the engine is not running at FG startup, which calls update() before CAS is initialized.
Therefore, the real solution is to prevent calling update when engine is not running at FG startup.
I already committed the fix, so you can update CVS to get the proper one.
I also updated Nasal/aircrane-keyboard.xml. Now you can enable CAS from the beginning, and can toggle enable/disable
CAS by pressing Ctrl-e.
Tat
p.s.
There are four similar fcs.nas (including afcs.nas) in CVS, and I need to update all these files. For better maintainability, I'll unite all these fcs.nas and let each aircraft change the parameters outside fcs.nas. I'll let you know when everything is done.
Users browsing this forum: No registered users and 3 guests