Jim Wilson writes:
Ok, I think this means I can continue in the same direction with
the viewer code. It would be just a matter of editing xml to
switch from using /position/lat||lon||alt to somewhere else in the
property tree, so if folks want to experiment they can.
I don't know if
Andy Ross writes:
I'll chop the cockpit stuff out of YASim as soon as someone tells me
it's OK.
It's fine with me. Curt?
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Arnt Karlsen writes:
..a wee point: in sideslipping, will the responsible pilot
stare, towards the infinte end of the longitudal axis, or will
he watch/look out to where he is going? My .02, only. ;-)
We are talking only about the default viewpoint location. It's up to
the pilot to
David Megginson [EMAIL PROTECTED] said:
Jim Wilson writes:
Err umm...what is it that won't be necessary?
Using properties other than the /position ones.
Right from the start I've been planning to support that anyway.
Two reasons:
1) Probably soon to be realized multiple instances of
David Megginson writes:
Andy Ross writes:
I'll chop the cockpit stuff out of YASim as soon as someone tells me
it's OK.
It's fine with me. Curt?
Sure, sounds good to me.
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED]
David Megginson [EMAIL PROTECTED] said:
I tried this
fgfs --aircraft=c172-3d --fdm=yasim
and had an interesting experience -- I ended up sitting on the runway
a meter or two to the right of the plane, rather than inside it.
Something is overwriting the xyz offsets in the
Jim Wilson writes:
That is intentional. Before the pilot and chase were different
than each other (or seemed that way). Prior to knowing anything
about using plib or Opengl, I always assumed as a user that x was
across the screen, y was up and down and z was depth. That is I
think
David Megginson [EMAIL PROTECTED] said:
Sorry for the confusion there. I think that it's probably not a good
idea to do things that way -- we should stick with normal aircraft
axes for consistency with the rest of FlightGear, at least at the
property level (a GUI can present things
Jim Wilson writes:
It's already inconsistent. The model is one way (as you expected) and the
panel xml is x across and y up/down.
Yes, I know. One consideration, though, is that each panel is (soon)
going to be projected to any arbirtary location and orientation in the
aircraft, so you
Jim Wilson wrote:
David Megginson wrote:
I tried this
fgfs --aircraft=c172-3d --fdm=yasim
and had an interesting experience -- I ended up sitting on the runway
a meter or two to the right of the plane, rather than inside it.
Something is overwriting the xyz offsets in the
Jim Wilson wrote:
It's already inconsistent. The model is one way (as you expected)
and the panel xml is x across and y up/down.
But this is OK -- these are different coordinate systems with
different usages. You'll never put airframe coordinates into the
panel XML, nor use panel
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
David Megginson wrote:
I tried this
fgfs --aircraft=c172-3d --fdm=yasim
and had an interesting experience -- I ended up sitting on the runway
a meter or two to the right of the plane, rather than inside it.
On Wed, 03 Apr 2002 09:32:12 -0800
Something is overwriting the xyz offsets in the c172-3d-set.xml or
maybe it isn't reading that file? Those are defaults from
somewhere...probably from c172-set.xml.
Andy Ross [EMAIL PROTECTED] replied:
YASim _sets_ those offsets based on its own
David Megginson [EMAIL PROTECTED] said:
If I was the only one to have say in this I'd make the xyz in the
model files conform to the expected by the user axes (x across, y
up/down, z depth). It is also what would be expected by anyone who
is unfamiliar with plib but has done other
Jon S Berndt [EMAIL PROTECTED] said:
On Wed, 03 Apr 2002 09:32:12 -0800
Something is overwriting the xyz offsets in the c172-3d-set.xml or
maybe it isn't reading that file? Those are defaults from
somewhere...probably from c172-set.xml.
Andy Ross [EMAIL PROTECTED] replied:
Jim Wilson wrote:
Andy Ross wrote:
David Megginson wrote:
Something is overwriting the xyz offsets in the c172-3d-set.xml or
maybe it isn't reading that file? Those are defaults from
somewhere...probably from c172-set.xml.
YASim _sets_ those offsets based on its own
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
Ultimate, the pilot position comes from the cockpit tag in the YASim
.xml file. The rationale here was that this was the best place to put
the information about the cockpit position was in the aircraft
definition. But that was before
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
That's ok, but as I said earlier, the offsets that the viewer will
use will be defined elsewhere because they are not necessarily the
true actual pilot's eye point.
We're evidently talking past each other. What you say is true.
On Wed, 3 Apr 2002 20:47:57 -
Jim Wilson [EMAIL PROTECTED] wrote:
If there is something that I need to use that comes
from the FDM let me know what it is and how to use it.
But I'm not going to be setting the eyepoint with FDM data (other than
offseting it from the available origin
Jim Wilson wrote:
Andy Ross wrote:
The FDMs already take the c.g. into consideration. If a stopped
aircraft rotates (about the c.g, of couse), you will see the
coordinate origin moving.
Well this might be useful to the 3D model. The effect probably isn't
all that noticable
Jon S Berndt writes:
I'm not sure I understand what you are saying, here. I will say,
however, that if there is a viewpoint given for pilot eyepoint in a
JSBSim config file it would be good to reference it somehow (even
if you copy it into an aircraft 3d model file) because it will be
I mildly disagree.
I think the FGFS should require that the FDMs _and_ the aircraft models
all have the reference point at the original manufacturer's defined
reference point (so they all match nicely) even if this is done by
a parametric offset that the FDM's configuration file has somewhere.
On Wed, 3 Apr 2002 16:26:57 -0600 (CST)
Curtis L. Olson [EMAIL PROTECTED] wrote:
The FDM defines some aribitrary reference point (i.e. on the firewall)
and provides the lon/lat/elev of that point.
We provide the lat/lon/elev of the current _CG_.
The FDM really doesn't care about the actual
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
Andy Ross wrote:
The FDMs already take the c.g. into consideration. If a stopped
aircraft rotates (about the c.g, of couse), you will see the
coordinate origin moving.
Well this might be useful to the 3D model. The
Curtis L. Olson writes:
Jon S Berndt writes:
On Wed, 3 Apr 2002 22:54:01 -
Jim Wilson [EMAIL PROTECTED] wrote:
Ok, so are you saying that the lon/lat/alt values that
the fdm outputs are at the origin already adjusted for cg?
JSBSim gives the lat/lon/alt of the CURRENT CG - NOT the
On Wed, 3 Apr 2002 17:29:42 -0600 (CST)
Curtis L. Olson [EMAIL PROTECTED] wrote:
Jon S Berndt writes:
I think this boils down to let's have the FDM worry about where the
plane is, and let's have FlightGear worry about where the current view
point is.
I agree. We don't care about where the
On Wed, 3 Apr 2002 18:44:23 -0500
Norman Vine [EMAIL PROTECTED] wrote:
My take on this is that all we need is a 'fixed' position ie 'Center of
Geometry' returned by the FDM. This fixed position can be anywhere
on the AirFrame and it needs to be described more exactly in the
individual
Jon S Berndt [EMAIL PROTECTED] said:
On Wed, 3 Apr 2002 18:44:23 -0500
Norman Vine [EMAIL PROTECTED] wrote:
My take on this is that all we need is a 'fixed' position ie 'Center of
Geometry' returned by the FDM. This fixed position can be anywhere
on the AirFrame and it needs to be
Jim Wilson writes:
Jon S Berndt [EMAIL PROTECTED] said:
On Wed, 3 Apr 2002 18:44:23 -0500
Norman Vine [EMAIL PROTECTED] wrote:
My take on this is that all we need is a 'fixed' position ie 'Center of
Geometry' returned by the FDM. This fixed position can be anywhere
on the AirFrame and
On Wed, 3 Apr 2002 17:16:31 -0500,
David Megginson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Jon S Berndt writes:
I'm not sure I understand what you are saying, here. I will say,
however, that if there is a viewpoint given for pilot eyepoint in a
JSBSim config file it
Jim Wilson wrote:
Ok, so are you saying that the lon/lat/alt values that the fdm outputs
are at the origin already adjusted for cg? If so then how would that
affect the axis of say pitch rotation on the c172 model? It's origin
is at the firewall and the pitch rotation is always on the
Jon S. Berndt wrote:
Jim Wilson wrote:
Ok, so are you saying that the lon/lat/alt values that the fdm
outputs are at the origin already adjusted for cg?
JSBSim gives the lat/lon/alt of the CURRENT CG - NOT the origin of the
structural frame.
Ack, really? I was honestly under the
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
Ok, so are you saying that the lon/lat/alt values that the fdm outputs
are at the origin already adjusted for cg? If so then how would that
affect the axis of say pitch rotation on the c172 model? It's origin
is at the firewall
Ack, really? I was honestly under the impression that you were
handing out the coordinate frame too; I thought I had checked this in
code when writing YASim.
Perhaps this is related to the misunderstanding of our gear model and how we
determined where we were?
Why c.g.? Since it moves, it
34 matches
Mail list logo
