Erik Hofman wrote:
Andy Ross wrote:
Hrm? I don't think that's possible in the new architecture; the panel
renders into the model's scene graph, it doesn't touch the view
information anymore. Are you sure you have current code? This sounds
like you might be looking at a 2D panel while
I have been using FlightGear since 7.7 and have only recently begun to
follow the CVS snapshot. I worked my way through college and a flight
Instructor and have about 1500 hours in real ac. I also have flown many
tail-draggers. I agree with your view of the tail-dragger ac and pilots.
I
Dave Perry wrote:
1. If the tail wheel is not locked, I find it much easier to take off
after removing the coupling of the rudder with the brakes for both
main gear from the dc3.xml.
I'd be happy to junk this; David always hated it anyway. It was
basically a hack to fix a problem I didn't
I spent some time over the weekend struggling with the jitterbug
(sorry, couldn't resist). I haven't fixed it, but I have pinpointed
the issue.
In essence: yes, it's a precision problem; but no, Jim's calculations
aren't the problem. The problem is actually the organization of the
scene graph.
Andy Ross writes:
I'm not sure that there's a good answer here. We could consider
interning constant strings like property paths into constant
references that don't need allocation. But stuff like
getStringValue() is always going to have to allocate a new string if
we want to do this
Norman Vine writes:
as far as I am concerned creating an ASCII property path
is a waste of time and should not be used anywhere inside
the 'main loop'.
Inside the main loop, it's used only for things like interactive
display in the property browser or through a network interface. It's
Erik Hofman writes:
Well, I know that (for instance) mustang pilots had to land
side-slipping, and taxi zig-zagging to get an eye on the runway.
Forward slipping, probably (since that would have the plane's axis at
an angle to the runway, while a side slip would have it lined up).
All
On Monday 01 July 2002 11:53 am, Alex Perry wrote:
I think I've found the problem. I grab the base package using rsync, and
that version doesn't seem to be up-to-date. Even the new crop textures
aren't included yet.
It's on my machine, but John Check had a cron job that pushd-updated it.
On Monday 01 July 2002 6:14 pm, John Check wrote:
On Monday 01 July 2002 11:53 am, Alex Perry wrote:
I think I've found the problem. I grab the base package using rsync,
and that version doesn't seem to be up-to-date. Even the new crop
textures aren't included yet.
It's on my
I now have a practical solution for saving the compiler warnings: a wrapper script
replacement for the compiler.
rm config.cache # Otherwise it keeps the previous values of CC and CXX.
GCCFLAGS=-Wall -pedantic -Wpointer-arith
CC=saveoutp gcc CXX=saveoutp c++ CFLAGS=$GCCFLAGS
Along the lines of adding the -pedantic option, I would like to add an
ability (probably at ./configure time) to specify additional compile
options. Since one of my platforms is a Mac, I would like to be able to
add -wno_long_double, as it keeps telling me that their size is
non-portable.
David Megginson writes:
Norman Vine writes:
as far as I am concerned creating an ASCII property path
is a waste of time and should not be used anywhere inside
the 'main loop'.
Inside the main loop, it's used only for things like interactive
display in the property browser or through a
Andy Ross [EMAIL PROTECTED] said:
Camera (orientation only, no position change)
|
+-- Transform (move to terrain origin)
||
|+-- Terrain
|
+-- Transform (move to model origin, orient to model frame)
|
+-- Aircraft Model
I got started trying to figure out how
Norman Vine [EMAIL PROTECTED] said:
but see
FGViewMgr::update (double dt)
Yes, all those should be moved to nodes in the view class. How did this look
in the last profiling run?
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Jim Wilson writes:
Norman Vine [EMAIL PROTECTED] said:
but see
FGViewMgr::update (double dt)
Yes, all those should be moved to nodes in the view class.
How did this look in the last profiling run?
Can't remember
FWIW - I don't really trust the profiler with Cygwin as I have learned
CVS for base package is down for a little bit.
I'll have it back up ASAP.
John
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Okay, we're back in business.
J
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
I added an effectiveness=nnn to both the htab and vtab. I was not
able to get good control once the tail was up w/o the change to vtab
also. I played arround with various values between 2 and 3.
I was able to get good control (vtab effectiveness) and early tail up
(htab effectiveness) with
18 matches
Mail list logo
