On Saturday, June 18, 2011 08:00:41 PM Jon S. Berndt wrote:
> > From: syd adams [mailto:adams@gmail.com]
> >
> > Does jsbsim ? I've just begun to look into it , so I don't really know
> > jsbsim's capabilities.
>
> It's not automatic - not a natural effect calculated by JSBSim code itself.
>
> From: syd adams [mailto:adams@gmail.com]
>
> Does jsbsim ? I've just begun to look into it , so I don't really know
> jsbsim's capabilities.
It's not automatic - not a natural effect calculated by JSBSim code itself.
Like many things in JSBSim, the facilities are present to let the aircraft
On the other hand, YASim does not take into the wing downwash
> or the propwash while computing the tail incidence (while they are
> first order contributors) so I would not use the word 'fidelity'.
Does jsbsim ? I've just begun to look into it , so I don't really know
jsbsim's capabilities.
Che
2011/6/18 Gary Neely :
> On Sat, Jun 18, 2011 at 10:38 AM, Bertrand Coconnier
> wrote:
>> 2011/6/17 Gary Neely :
>>> I've always understood actionpt to be the location where thrust should
>>> be applied with respect to the airframe. For a propeller-driven
>>> engine, I use the approximate locatio
On Sat, Jun 18, 2011 at 10:38 AM, Bertrand Coconnier wrote:
> 2011/6/17 Gary Neely :
>> I've always understood actionpt to be the location where thrust should
>> be applied with respect to the airframe. For a propeller-driven
>> engine, I use the approximate location of the main thrust bearing. Fo
On 17 Jun 2011, at 20:47, Torsten Dreyer wrote:
> Thanks for supporting our effort to create the next FlitghtGear release
Woo-hoo, release process!
Thanks to Torsten for driving the release, and ThorstenB for already doing a
huge amount of bug-fixing. If you've previously filed bugs in tracker
On Saturday, June 18, 2011 01:17:10 AM Vivian Meazza wrote:
> Hal,
>
>
>
> Since the dialog seems to be fundamentally broken, and in view of the
> freeze that has been declared on fgdata, I won't be merging this
> immediately. I'll see if I can fix up the Nasal errors, and then review
> the situ
Ok, i worded that wrong ... action point is a way to specify the
thrust point if it's not the point defined for the engine mass ... and
yes , the coordinates are relative the aircraft origin ... my mistake.
--
EditLive Ent
2011/6/18 syd adams :
> My more simple understanding was the actionpoint was the point where
> thrust was applied relative to the engine mass , like the
> documentation states.
>
> an subelement
> to place the action point of the thrust at a different
> position than the mass of
My more simple understanding was the actionpoint was the point where
thrust was applied relative to the engine mass , like the
documentation states.
an subelement
to place the action point of the thrust at a different
position than the mass of the engine.
Works for me.
Cheer
Frederic Bouvier wrote:
> No scenery dir (top most) is editable. The google url isn't.
Ah, ok,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
---
2011/6/17 Gary Neely :
> On Fri, Jun 17, 2011 at 12:17 AM, xsaint wrote:
>> Hello Folks...
>>
>> Was wondering if any nice souls will assist clear this doubt on mine...
>>
>> In YASIM, what does "actionpt" really refers to?
>> Is it the point the engines pull the air through? which the point will
2011/6/17 Emilian Huminiuc :
> On Friday 17 June 2011 08:15:36 xsaint wrote:
>> Thank you Emilian and Buck
>>
>> Ok i tested changing the location of the point to ahead of the engine
>> and also behind the engine, near exhaust.
>> Irrespective of the location, looking at the results at the Yasi
- "Martin Spott" a écrit :
> Frederic Bouvier wrote:
>
> > embedded terrasync was not working for me because the scenery-dir
> > entered in the dialog was not copied in the property. It should be
> > fixed in fgdata now (dialog definition lacking a global
> dialog-apply).
>
> Isn't the scen
Frederic Bouvier wrote:
> embedded terrasync was not working for me because the scenery-dir
> entered in the dialog was not copied in the property. It should be
> fixed in fgdata now (dialog definition lacking a global dialog-apply).
Isn't the scenery-dir in the terrasync dialogue meant to be
non
Vivian,
embedded terrasync was not working for me because the scenery-dir entered in
the dialog was not copied in the property. It should be fixed in fgdata now
(dialog definition lacking a global dialog-apply).
I don't know if it is related to the issue you are seeing, but fgfs nightly
downlo
Hal,
Since the dialog seems to be fundamentally broken, and in view of the freeze
that has been declared on fgdata, I won't be merging this immediately. I'll
see if I can fix up the Nasal errors, and then review the situation.
Vivian
-Original Message-
From: V. Engel [mailto:hve
17 matches
Mail list logo
