On Freitag, 13. Februar 2004 02:59, Andy Ross wrote:
> David Megginson wrote:
> > Thanks -- your explanation and Jon's has made it all clear, and the
> > discussion has been useful. So, as far as I understand, JSBSim
> > supports this in JSBSim CVS but not yet in FlightGear. Does YASim
> > suppor
> True, but... This is a chunk of calculations running every frame. In
> the olden days, the cost would be too high.
These days, it's not even a spec on a flea on the butt of an elephant in
terms of the overall FDM calculations - which in turn are not much of a spec
on a flea in the overall Flig
Alex Romosan <[EMAIL PROTECTED]> said:
> Jorge Van Hemelryck <[EMAIL PROTECTED]> writes:
>
> > Try xvidcap... I haven't managed to really make a movie file with it
> > yet, but that's what it's supposed to do.
>
> thanks. xvidcap worked great. i put the movie up at:
>
> http://caliban.lbl.gov
David Megginson wrote:
Andy Ross wrote:
I'm not sure exactly what this is for. I can (and probably should)
export the C.G. position for the view code to use appropriately. But
the VRP stuff seems like a double-correction. It's basically
identical to the view center offset stuff, isn't it?
> David Megginson <[EMAIL PROTECTED]> said:
>
> > It's the location on the plane where the FDM reports the
> > lon/lat/alt. It's kind-of a nifty idea, actually.
>
> In relation to? It is always 0,0,0 in Yasim.
>
> Best,
>
> Jim
JSBSim could also define the tip of the nose as (0,0,0). It really
David Megginson <[EMAIL PROTECTED]> said:
> Andy Ross wrote:
>
> > I'm not sure exactly what this is for. I can (and probably should)
> > export the C.G. position for the view code to use appropriately. But
> > the VRP stuff seems like a double-correction. It's basically
> > identical to the v
Andy Ross wrote:
I'm not sure exactly what this is for. I can (and probably should)
export the C.G. position for the view code to use appropriately. But
the VRP stuff seems like a double-correction. It's basically
identical to the view center offset stuff, isn't it?
It's the location on the pla
Jon S Berndt <[EMAIL PROTECTED]> said:
> On Thu, 12 Feb 2004 22:56:46 +0100
> Mathias Fröhlich <[EMAIL PROTECTED]> wrote:
> >
>
> >Even JSBSim CVS does not support this visual reference point yet.
> >There is a
> >patch pending in Jon's mailbox to report the visual reference point
> >to
> >
Vivian Meazza <[EMAIL PROTECTED]> said:
> > Josh Babcock
>
> > Vivian Meazza wrote:
> >
> > >
> > >I enter the loop in a shallow dive, 2nd stage boost on, 350
> > kts, pull
> > >baaack the stick and the model rolls violently and does not
> > enter the
> > >loop ... Works fine in other model
David Megginson <[EMAIL PROTECTED]> said:
> Jim Wilson wrote:
>
> > Yes. In YASim, the 0,0,0 of the fuselage property is the origin. So if ax=0,
> > ay=0, az=0 is used then the nose is origin in YASim.
>
> It would be nice to be able to specify the point in YASim as well, so we
> don't have t
David Megginson wrote:
> Thanks -- your explanation and Jon's has made it all clear, and the
> discussion has been useful. So, as far as I understand, JSBSim
> supports this in JSBSim CVS but not yet in FlightGear. Does YASim
> support setting the reference point yet?
I'm not sure exactly what t
On Thu, 2004-02-12 at 12:53, Jon S Berndt wrote:
> On Thu, 12 Feb 2004 15:35:59 -0500
> David Megginson <[EMAIL PROTECTED]> wrote:
> >Jon S Berndt wrote:
>
> >I'm not sure I see how this helps -- the model code still doesn't
> >know where the CG is, so it still doesn't know where the centre of
On Thu, 12 Feb 2004 21:05:25 +, David Luff <[EMAIL PROTECTED]>
wrote:
Anyone got any wavefile editor recommendations BTW?
I like GoldWave. www.goldwave.com
I used CoolEdit (Windows) for the ATIS, but the trial period is now long
gone, and when I went to buy it I found the guy had sold it to
There still seem to be problems with simgear/environment on the CVS
server. I'm not getting any of the files in that dir when I do a cvs
up. I had to dl them off the web server. Everything else seems to be
updating well though.
Josh
___
Flightgear
> Josh Babcock
> Vivian Meazza wrote:
>
> >
> >I enter the loop in a shallow dive, 2nd stage boost on, 350
> kts, pull
> >baaack the stick and the model rolls violently and does not
> enter the
> >loop ... Works fine in other models so it's not the obvious - the
> >joystick. But I expect
Jonathan Richards writes:
> In what units shall the time index be specified? The sampling rate sets a
> resolution limit on the timing, so for 8kHz we only need 1/8000 sec = 125
> microseconds precision, but if we have an ambition for higher rates, we need
> more. [1]
> In reality, radio comm
Jim Wilson wrote:
Yes. In YASim, the 0,0,0 of the fuselage property is the origin. So if ax=0,
ay=0, az=0 is used then the nose is origin in YASim.
It would be nice to be able to specify the point in YASim as well, so we
don't have to physically alter the models. For the PA-28-161, though, I'l
On Donnerstag, 12. Februar 2004 23:11, Jon S Berndt wrote:
> ?? I thought I had already committed these. You might want to double
> check. In any case, I already committed to CVS the code that reports
> the VRP, as well as to make the corrections to the transforms (as you
> pointed out). These are
On Thu, 12 Feb 2004 22:56:46 +0100
Mathias Fröhlich <[EMAIL PROTECTED]> wrote:
Even JSBSim CVS does not support this visual reference point yet.
There is a
patch pending in Jon's mailbox to report the visual reference point
to
flightgear and define a reference point in each JSBSim aircraft
On Donnerstag, 12. Februar 2004 22:37, David Megginson wrote:
> Thanks -- your explanation and Jon's has made it all clear, and the
> discussion has been useful. So, as far as I understand, JSBSim supports
> this in JSBSim CVS but not yet in FlightGear. Does YASim support setting
> the reference
David Megginson <[EMAIL PROTECTED]> said:
> Jim Wilson wrote:
>
> > That is why the model code does not need to know where the CG is. The 3D
> > model designer does need to know the FDM "origin" or "reference point" or
> > whatever you want to call the vertex in space at which the FDM reports th
Jim Wilson wrote:
That is why the model code does not need to know where the CG is. The 3D
model designer does need to know the FDM "origin" or "reference point" or
whatever you want to call the vertex in space at which the FDM reports the
lon/lat/alt of the aircraft. So if she puts the origin o
Vivian Meazza wrote:
So put the (visual) model origin at or near the CofG - what's the problem?
Seems to work OK in practice.
It depends on the aircraft. A light trainer like the Piper Cherokee or the
Cessna 172 typically allows only about a foot of variation in the location
of the CG along the
Jim Wilson asked
> Vivian Meazza <[EMAIL PROTECTED]> said:
>
> > I moved the origin, then applied an equal and opposite offset. When
> > one differential brake is applied and the model is viewed in or
> > helicopter view tower view it appears to be turning around its axis
> > rather than ar
On Thu, 12 Feb 2004 21:19:25 -
"Vivian Meazza" <[EMAIL PROTECTED]> wrote:
Jon S Berndt tells us
First, the aircraft - like any body - rotates about its CG
(according to the EOM) - not usually the same as the AC.
So put the (visual) model origin at or near the CofG - what's the
problem? See
Vivian Meazza wrote:
I enter the loop in a shallow dive, 2nd stage boost on, 350 kts, pull baaack
the stick and the model rolls violently and does not enter the loop ...
Works fine in other models so it's not the obvious - the joystick. But I
expect I'm doing something wrong.
Yup. Specificall
On Thursday 12 Feb 2004 5:31 pm, David Luff wrote:
> OK, here's some instructions on how to generate new ATC voices for
> FlightGear. Hopefully this will make some sense to somebody, ask if it's
> unclear.
> Two files are required for each voice - a wave file containing the actual
> sounds, and a
David Megginson <[EMAIL PROTECTED]> said:
> Jon S Berndt wrote:
>
> > JSBSim made a change recently that is likely not yet in FlightGear CVS.
> > The lat/lon/alt position now reported by JSBSim (CVS) is the position of
> > the VRP (Visual Reference Point) - i.e. the tip of the prop hub (or
>
> Jon S Berndt tells us
> On Thu, 12 Feb 2004 15:09:15 -0500
> David Megginson <[EMAIL PROTECTED]> wrote:
>
> >So, given that the aerodynamic centre of an aircraft can shift based
> >on loading and flight conditions, how can we report that
> from the FDM
> >back to the 3D model code? Is t
Vivian Meazza <[EMAIL PROTECTED]> said:
> I moved the origin, then applied an equal and opposite offset. When one
> differential brake is applied and the model is viewed in or helicopter view
> tower view it appears to be turning around its axis rather than around the
> braked wheel. That said, in
Jim Wilson added
> Vivian Meazza <[EMAIL PROTECTED]> said:
>
> > Tried that. Looks just the same to me. As I said some time ago: yer
> > pays yer money and yer takes yer choice. Neither is right on the
> > ground for differential braking: with one brake full on the
> aircraft
> > more or le
David Megginson <[EMAIL PROTECTED]> said:
> OK, everyone, here's the problem. I tested watching the PA28-161 from a
> fixed point on the ground, and it does, in fact pivot around its nose still.
Maybe not. Your cvs log shows that you did not make the target offset
correction for the tower view
Hello all,
Just a few comments from a sideline observer following the discussion
for many months. Jon seems to be providing a point representing a
vector from the current (dynamic) CG to an agreed point in space where
the plane nose is expected. If this vector is updated regularly both
in mag
On Thu, 12 Feb 2004 15:35:59 -0500
David Megginson <[EMAIL PROTECTED]> wrote:
Jon S Berndt wrote:
I'm not sure I see how this helps -- the model code still doesn't
know where the CG is, so it still doesn't know where the centre of
rotation for the model should be.
This is precisely *why* the no
On Thu, 12 Feb 2004 15:36:13 -0500
Josh Babcock <[EMAIL PROTECTED]> wrote:
This has all got me thinking a bit. This subject seems to come up
quite a bit, and frankly I have found it a dificult problem too. In
addition, there are some related things that can get hard as well
like placing the w
This has all got me thinking a bit. This subject seems to come up quite
a bit, and frankly I have found it a dificult problem too. In addition,
there are some related things that can get hard as well like placing the
wheels right on the ground, and getting the landing gear elements for
wingti
Jon S Berndt wrote:
JSBSim made a change recently that is likely not yet in FlightGear CVS.
The lat/lon/alt position now reported by JSBSim (CVS) is the position of
the VRP (Visual Reference Point) - i.e. the tip of the prop hub (or
similar nose tip location on non-prop aircraft). As long as
"Jon S Berndt" <[EMAIL PROTECTED]> wrote:
> Is there now a difference in the way that JSBSim and YASim match up
> the 3D model with the FDM?
No, the discussion is only about placement of the 3D model vs. some FDM
reference point, I think (but I'm not absolutely shure if there _might_
be a hidden
Jorge Van Hemelryck <[EMAIL PROTECTED]> writes:
> Try xvidcap... I haven't managed to really make a movie file with it
> yet, but that's what it's supposed to do.
thanks. xvidcap worked great. i put the movie up at:
http://caliban.lbl.gov/fgfs-carrier.mpeg
the file is 33548 kB, and the movie
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> Trust me, I've been all over every line of the viewer code. You aren't really
> seeing what you think you are. It just looks that way.
Jim, do you want to tell me I'm blind ? I must admit that I probably
never looked at the code but I can assure you tha
On Thu, 12 Feb 2004 15:09:15 -0500
David Megginson <[EMAIL PROTECTED]> wrote:
So, given that the aerodynamic centre of an aircraft can shift based
on loading and flight conditions, how can we report that from the FDM
back to the 3D model code? Is this something people worked out in a
previous
On Thu, 12 Feb 2004 19:50:48 -
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
You actually want to be very exact about matching the model to the
FDM origin.
...
Jim (or someone ... *anyone*):
Could you summarize the argument taking place here? I seem to only be
getting parts of it - I guess I did
OK, everyone, here's the problem. I tested watching the PA28-161 from a
fixed point on the ground, and it does, in fact pivot around its nose still.
The problem is that the model code gets the roll/pitch/yaw from the FDM and
then applies it to the 0,0,0 point in the 3D model, which happens to b
Vivian Meazza <[EMAIL PROTECTED]> said:
> I was only using the CofG (and approximately at that) as a better visual
> reference than the nose. I was only concerned to make things look right. I'm
> sure that the FDMs are quite correct, or the models wouldn't fly very well,
> if at all. I take it the
Martin Spott <[EMAIL PROTECTED]> said:
> You _might_ be right, but in the case we are talking abouth things are
> different. For example use the "Tower view" and zoom enough to get the
> details. Take off and stay 100 ft above the ground. Now push the
> elevator violently aband you'll notice that
Frederic BOUVIER wrote:
Josh Babcock wrote:
I think the problem can be with your model. I think of two more points to check :
1. if your objects are included in a branch that is culled, they will not appear.
None of the 6 objects in the problem animation are members of any group.
Vivian Meazza <[EMAIL PROTECTED]> said:
> Tried that. Looks just the same to me. As I said some time ago: yer pays yer
> money and yer takes yer choice. Neither is right on the ground for
> differential braking: with one brake full on the aircraft more or less
> rotates around that wheel. The mode
Martin Spott asked
> Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs]
>
>
> "Jim Wilson" <[EMAIL PROTECTED]> wrote:
>
> > If you put the model back to the nose and use the method
> that the p51d
> > and the pa28-161 use (the target offset) you'll look better on the
> > ground.
>
>
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> If you put the model back to the nose and use the method that the p51d and the
> pa28-161 use (the target offset) you'll look better on the ground.
BTW, it appears to me that the P-51 suffers from the same visual mishap
as the PA-28 does (does this have t
Jim Wilson wrote
> Vivian Meazza <[EMAIL PROTECTED]> said:
>
> >
> >
> > Martin wrote:
> > >
> > > David Megginson <[EMAIL PROTECTED]> wrote:
> > > > Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
> > > > In directory baron:/tmp/cvs-serv12589
> > >
> > > > Modified Files:
> > > >
OK, here's some instructions on how to generate new ATC voices for
FlightGear. Hopefully this will make some sense to somebody, ask if it's
unclear.
If you want to record the phrases in a local accent or even a different
language go right ahead, I'll add code support for it. You'll need to
suppl
Andy wrote
>
>
> Martin Spott wrote:
> > Jim Wilson wrote:
> > > If the camera is tracking the nose, then it moves up and down as
> > > well with the nose. This creates the _illusion_ that the rest of
> > > the aircraft (and of the scene for that matter) is
> moving, and the
> > > nose is r
Andy Ross <[EMAIL PROTECTED]> wrote:
> Martin Spott wrote:
>> Jim Wilson wrote:
>> > If the camera is tracking the nose, then it moves up and down as
>> > well with the nose. This creates the _illusion_ that the rest of
>> > the aircraft (and of the scene for that matter) is moving, and the
>> > n
Josh Babcock wrote:
> Right, this example was supposed to make the stuff disappear at ranges
> greater than 2000, but it makes the stuff disappear alltogether. Here's
> the other LOD stuff right now, none of this stuff appears in any other
> animations except the ones that are selected out when
Martin Spott wrote:
> On the other hand it might be easier to 'preload' the data into
> memory and prevent this memory area to being swapped out (there
> should be some operating system call),
There certainly is. It's called "read()". :)
Andy
___
Flig
Martin Spott wrote:
> Jim Wilson wrote:
> > If the camera is tracking the nose, then it moves up and down as
> > well with the nose. This creates the _illusion_ that the rest of
> > the aircraft (and of the scene for that matter) is moving, and the
> > nose is remaining stationary when in fact it
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> David Megginson <[EMAIL PROTECTED]> said:
>> Martin Spott wrote:
>> > At least in the _outside_ views the PA-28 still rotates around its nose
>> > after the recent changes,
>>
>> That seemed funny to me as well, but when I looked from the outside view, it
David Megginson <[EMAIL PROTECTED]> said:
> Martin Spott wrote:
>
> > I can't withstand the impression that changing the _camera_ position
> > didn't lead to the intended success. Take a simple stick and rotate it
> > around one of its ends. For an observer the phenomenon is still the
> > same ev
Right, this example was supposed to make the stuff disappear at ranges
greater than 2000, but it makes the stuff disappear alltogether. Here's
the other LOD stuff right now, none of this stuff appears in any other
animations except the ones that are selected out when retracted. All
the animat
Vivian Meazza <[EMAIL PROTECTED]> said:
>
>
> Martin wrote:
> >
> > David Megginson <[EMAIL PROTECTED]> wrote:
> > > Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
> > > In directory baron:/tmp/cvs-serv12589
> >
> > > Modified Files:
> > > pa28-161-yasim-set.xml
> > > Log Message:
Martin Spott wrote:
I can't withstand the impression that changing the _camera_ position
didn't lead to the intended success. Take a simple stick and rotate it
around one of its ends. For an observer the phenomenon is still the
same even when he changes his viewpoint.
If you want to rotate the sti
Martin wrote:
>
> David Megginson <[EMAIL PROTECTED]> wrote:
> > Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
> > In directory baron:/tmp/cvs-serv12589
>
> > Modified Files:
> > pa28-161-yasim-set.xml
> > Log Message:
> > Change camera position so that model doesn't rotate arou
"Jon S Berndt" <[EMAIL PROTECTED]> wrote:
> On Tue, 10 Feb 2004 15:06:41 -0800
> Andy Ross <[EMAIL PROTECTED]> wrote:
>>> Jon S. Berndt wrote:
>>> > It is thought that the use of a RAM disk might help.
>>My interpretation was that their problem was latency, not I/O
>>throughput. The program co
David Megginson <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
> In directory baron:/tmp/cvs-serv12589
> Modified Files:
> pa28-161-yasim-set.xml
> Log Message:
> Change camera position so that model doesn't rotate around the nose.
I can't withstand t
Hi Guys!
Long time ago I created my scenery with hi resolution (100 m)
I use 03.09.2003 flightgear simgear and terragear CVS version. All works
fine but now I download from CVS flightgear and simgear and found that my
scenery not loaded :)) but KSFO loaded fine. BTW my btg files has size
approx 440
65 matches
Mail list logo
