To everybody who is interested in ufo alternatives,
the runabout and both shuttles are now out of development, and have undergone
substantial improvements.
http://www.geocities.com/sandreas41/flightgear_aircraft.html
Enjoy!
Stewart
Joacim Persson wrote:
> Ha! You can run but you can't hide from
Laurence Vanek wrote:
> After fresh updates & builds of osg, simgear& fg I get this when
> executing flightgear from command line (sorry for the long post). This
> is new behavior for me. Im running Fedora Core 6 with nvidia geforce
> 7600 GS graphics card (256 megs VRAM). No problems prior t
On Wed, 2007-02-07 at 07:09 -0700, Dave Perry wrote:
> Related File locations:
> Aircraft/Generic/kap140.nas -- KAP140 logic engine
> Aircraft/Instruments/KAP140TwoAxis.xml and
> Aircraft/Instruments/KAP140TwoAxisAlt.xml -- 2d KAP140 Instruments
>
Hi Yurik,
Thank you, That was very helpful. I have finished my animations now.
I would like to add, the order in which the s are placed in the
.xml file is also important. As long as the xml.animations are in the same
order as the ac.objects, back to front, then everything looks good.
Stewart
hi,
I was just happy to test the fresh airport and the rebuilt tile I've
made with taxidraw and terragear.
But... at the first passing by above the airport I hit an invisible
hill/thing! Hopefully, it's safer in real life :)
Well, first, I didn't noticed it with the ufo but now I can see the ag
Improved code. Previous version went against the POSIX convention.
# Following the POSIX convention,
# halfway cases are rounded away from zero,
# to the extent this is possible given the inherent
# inexactitude of the floating-point representation.
round = func(arg, quantum=1){
if (quantum ==
On 02/07/2007 02:14 PM, Andy Ross wrote:
> > The patch itself looks sane and easy. But I think I agree with
> > John, this is a workaround for a design flaw in the step animation
> > that we should just fix.
:-)
> So you want to pass in the floating point value 29.92 and a step of 10
> and g
On Mon, 2007-02-05 at 19:55 -0500, Durk Talsma wrote:
> John Denker wrote:
> >1.2 Memory leak
> >
> Megs or Gigs (See WIKI text) :-) Anyways, kidding aside: Is anybody else
> seeing this? I routinely let FlightGear run for several days at the time
> when I'm testing AI stuff. I've never se
I wrote:
> The patch itself looks sane and easy. But I think I agree with
> John, this is a workaround for a design flaw in the step animation
> that we should just fix.
Nope, it turns out we really do want truncation. The reason is that
the input property to the animation, at least in Ron's
On 02/07/2007 12:26 PM, Ron Jensen wrote:
> How would the step function know to round to the proper number of
> decimal places? In the 2D instruments a printf-style statement is used,
> i.e. %02.2f. However, we're not exactly printing in
> .
>
> I thought about a "" tag where we could tell
> h
John Denker wrote:
> Ron Jensen wrote:
> > The tag effectively truncates the property, 29.9199
> > becomes 29.91, so a (3D) readout reads off one number.
> >
> > I am proposing an new tag, , that will act like but be
> > applied before and
>
> While the tag seems reasonable eno
On Wed, 2007-02-07 at 11:32 -0500, John Denker wrote:
> On 02/07/2007 09:47 AM, Ron Jensen wrote:
> > While working on 3D cockpit instruments I keep hitting into issues with
> > internal floating point representation and the tag.
> >
> > The tag effectively truncates the property, 29.919
On 02/07/2007 09:47 AM, Ron Jensen wrote:
> While working on 3D cockpit instruments I keep hitting into issues with
> internal floating point representation and the tag.
>
> The tag effectively truncates the property, 29.9199
> becomes 29.91, so a (3D) readout reads off one number.
> I
While working on 3D cockpit instruments I keep hitting into issues with
internal floating point representation and the tag.
The tag effectively truncates the property, 29.9199
becomes 29.91, so a (3D) readout reads off one number. The electronics
technician in me says, "but digital read
On Wed, 2007-02-07 at 07:36 +0100, woodyst wrote:
> Looking at the KAP140.xml file I have found this line:
>
> /autopilot/internal/heading-bug-error-deg -->
>
> The "-->" is in the file, line 114. I think it may be a bug (I
> suspect it may be a mistake with keyboard, copy and paste, or
> somethi
Sava? Yatmaz wrote:
>
>
>
>
>
>
> Logitech Logitech Dual Action
Currently we don't have a Joystick configuration with such a name tag.
Does anyone object to putting this one into CVS ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
-
Am Dienstag, 6. Februar 2007 23:11 schrieb Stuart Buchanan:
> There are still a number of problems
> - Transparency issues with the windshield - wing/fuselage disappears when
> seen through two surfaces.
Hi Stuart,
I had the same problem with the Seneca and now use a select animation for the
wind
17 matches
Mail list logo
