The nasal script action-sim,and similar animation scripts produces
aircraft-geometry-unique animation parameters used by xml files to
produce the actual animations. If one wants to animate the gear so it
responds to the fdm produced gear compressions, such nasal scripts are
critical. The alternative is to have the tires penetrate the ground
surface different depth dependent on the fdm supplied compression and
the oleo links move up and down rigidly. Both are not at all
realistic. This script is not at all "useless".
Dave P. (author of the script)
On 02/11/2011 05:49 AM, henri orange wrote:
Hi,
Though, newbe, since i have to maintain some old jsbsim aircraft, my
understanding ts becoming better.
Here we do have a c172p which is using nasal only for animation, that
scrip is, to me, right now, useless.
The data compression, rotation and so on, are exposed in the, today,
jsbsim FDM.
The others features, landing gear related ( rolling friction and so on
) , can be easily processed, within the FDM, since, the required data
are exposed, and RT updated, with functions.
To do that, jsbsim want only the ground values, load-resistance,
friction-factor, rolling-friction, and solid or not.
These real time data are NOT EXPOSED within Flighgear,. i don't know,
why, and, i don't know if this has being discussed before.
ONLY, a little nasal script gives the right required, input.
Thus, every jsbsim Aircraft model which want the right behavior on
ground, need that nasal scrip.
Yes the best would be to transfer the "nasal 30 lines script" to the
jsbsim source, or better to the Flightgear source, since others
generic flightgear features does want such data.
I can notice the usage of that nasal script with some yasim aircraft
also.
2011/2/11 Alasdair <ali...@btinternet.com <mailto:ali...@btinternet.com>>
On Thu, 2011-02-10 at 15:34 +0100, Bertrand Coconnier wrote:
> Correct. JSBSim itself makes no distinction between ground materials
> (hence the reason why some aircrafts are able to land on water).
This
> can however be managed with Nasal scripts. So I would say that this
> issue is likely located in one of the C172 Nasal scripts.
>
> Bertrand
>
On an OT philisophical note..
Is , or rather, was the introduction of NASAL scripting a "Good Thing"
or can it be considered as the hugest abomination to ever befall
the FG
World, rendering the
use of GDB as a useless tool for tracing the behaviour of C/C++ code,
sometimes
modified or nullified by a run-time script? Just a thought. Are
there
any other source
code purists out there. I hope so, cos I would hate to justify this
untimely rant on my
own. Somehow it reminds me of self modifiaction of computer code,
thought clever
by some specialists when Babbage was but a baby.
--
Kind regards,
Alasdair
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel
Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
<mailto:Flightgear-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Best regards,
Henri, aka Alva
Official grtux hangar maintainer
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
