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
Sava? Yatmaz wrote:
?xml version=1.0 ?
!--
$Id: dual-action.xml,v 1.9 2006-11-06 09:20:00 syatmaz Exp $
--
PropertyList
nameLogitech Logitech Dual Action/name
Currently we don't have a Joystick configuration with such a name tag.
Does anyone object to putting this one into CVS ?
On Wed, 2007-02-07 at 07:36 +0100, woodyst wrote:
Looking at the KAP140.xml file I have found this line:
prop/autopilot/internal/heading-bug-error-deg/prop --gt;
The --gt; 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
While working on 3D cockpit instruments I keep hitting into issues with
internal floating point representation and the textranslatestep tag.
The step tag effectively truncates the property, 29.9199
becomes 29.91, so a (3D) readout reads off one number. The electronics
technician in me
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 textranslatestep tag.
The step tag effectively truncates the property, 29.9199
becomes 29.91, so a (3D) readout reads off
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 textranslatestep tag.
The step tag effectively truncates the property,
John Denker wrote:
Ron Jensen wrote:
The step tag effectively truncates the property, 29.9199
becomes 29.91, so a (3D) readout reads off one number.
I am proposing an new tag, bias, that will act like offset but be
applied before step and scroll
While the bias tag
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. format%02.2f/format. However, we're not exactly printing in
textranslate.
I thought about a
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 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 seen any
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 get back
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
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
Hi Yurik,
Thank you, That was very helpful. I have finished my animations now.
I would like to add, the order in which the animations 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.
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
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 to
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
17 matches
Mail list logo
