On ven 7 septembre 2007, you wrote:
On ven 7 septembre 2007, Melchior FRANZ wrote:
* Jon S. Berndt -- 9/7/2007 1:33 AM:
[ground material aware gear handling in JSBSim]
Well, if I was the one doing the ridiculing, I apologize.
No need to, you weren't, IIRC. :-)
But the ridiculing
On ven 7 septembre 2007, Melchior FRANZ wrote:
* Jon S. Berndt -- 9/7/2007 1:33 AM:
[ground material aware gear handling in JSBSim]
Well, if I was the one doing the ridiculing, I apologize.
No need to, you weren't, IIRC. :-)
But the ridiculing became known to the IRC participants, and
* Jon S. Berndt -- 9/7/2007 1:33 AM:
[ground material aware gear handling in JSBSim]
Well, if I was the one doing the ridiculing, I apologize.
No need to, you weren't, IIRC. :-)
But the ridiculing became known to the IRC participants, and this
caused very upset (and slightliy exaggerated :-)
* gh.robin -- 9/6/2007 12:05 AM:
We can with an external property scenery material type to process
correctly the aircraft reactions according to the type.
And which material should this report? The one under the left
wing tip, or the one 150 m behind the tail, or what?! FlightGear
has no
Melchior FRANZ
But that's IMHO the only way that makes sense. And JSBSim
(unlike YASim) currently lacks other gear features, anyway.
Per-gear-material-info can easily be implemented when the
JSBSim gear gets friction/solidity/etc. awareness. The
the whole world is a runway behavior is fun,
On jeu 6 septembre 2007, Jon S. Berndt wrote:
Melchior FRANZ
But that's IMHO the only way that makes sense. And JSBSim
(unlike YASim) currently lacks other gear features, anyway.
Per-gear-material-info can easily be implemented when the
JSBSim gear gets friction/solidity/etc.
As far as other gear features, what would those be?
- not allowing to land/taxi on water (except water planes)
- gear friction taken from the ground material
- considering ground bumpiness (small on concrete, high in the forest)
You can check how Maik JUSTUS implemented it for YASim.
Hello,
groundcache.cxx seems to be able to give the material information ( lines 234
and following), mainly solid or water.
According to a recent talk on IRC, i dare that question:
Why don't we have it given on the property tree ?, which could be very useful
for animations (OSG particles,
* gh.robin -- 9/5/2007 4:15 PM:
groundcache.cxx seems to be able to give the material information
[...]
With a specific property we could have it fully opened.
Isn't the property tree, but might be useful nevertheless:
There's a Nasal function geodinfo() that returns material and
other
On mer 5 septembre 2007, Melchior FRANZ wrote:
* gh.robin -- 9/5/2007 4:15 PM:
groundcache.cxx seems to be able to give the material information
[...]
With a specific property we could have it fully opened.
Isn't the property tree, but might be useful nevertheless:
There's a Nasal
* Melchior FRANZ -- 9/5/2007 5:15 PM:
If you really need it in the tree (e.g. for XML animations), then [...]
Oh, and ai submodel impacts report the material in the property tree
already, along with other impact data.
m.
-
On mer 5 septembre 2007, Melchior FRANZ wrote:
* Melchior FRANZ -- 9/5/2007 5:15 PM:
If you really need it in the tree (e.g. for XML animations), then [...]
Oh, and ai submodel impacts report the material in the property tree
already, along with other impact data.
m.
hmm,
may be i
* gh.robin -- 9/5/2007 5:43 PM:
i find nothing regarding impacts in the submodel property tree.
See $FG_ROOT/Docs/README.submodels and the seahawk for an example.
If impacts are enabled in the submodel XML config file (impact),
then every impact generates a dir entry in /ai/models/ with all
the
On mer 5 septembre 2007, Melchior FRANZ wrote:
* gh.robin -- 9/5/2007 5:43 PM:
i find nothing regarding impacts in the submodel property tree.
See $FG_ROOT/Docs/README.submodels and the seahawk for an example.
If impacts are enabled in the submodel XML config file (impact),
then every
* gh.robin -- 9/5/2007 6:16 PM:
unfortunately that is only available with submodel,
which does not answer the request regarding the model itself.
Yes. But it's information that needs to be available per gear,
not for /position/{latitude,longitude}-deg. And YASim provides
this information,
On mer 5 septembre 2007, Melchior FRANZ wrote:
* gh.robin -- 9/5/2007 6:16 PM:
unfortunately that is only available with submodel,
which does not answer the request regarding the model itself.
Yes. But it's information that needs to be available per gear,
not for
* gh.robin -- 9/5/2007 6:37 PM:
* On mer 5 septembre 2007, Melchior FRANZ wrote:
But it's information that needs to be available per gear,
[...] it has to be added to the JSBSim/fgfs interface.
to me, It is not necessary to include it within JSBSim
But that's IMHO the only way that makes
On mer 5 septembre 2007, Melchior FRANZ wrote:
* gh.robin -- 9/5/2007 6:37 PM:
* On mer 5 septembre 2007, Melchior FRANZ wrote:
But it's information that needs to be available per gear,
[...] it has to be added to the JSBSim/fgfs interface.
to me, It is not necessary to include it
On mer 5 septembre 2007, Melchior FRANZ wrote:
* gh.robin -- 9/5/2007 6:37 PM:
* On mer 5 septembre 2007, Melchior FRANZ wrote:
But it's information that needs to be available per gear,
[...] it has to be added to the JSBSim/fgfs interface.
to me, It is not necessary to include it
19 matches
Mail list logo
