* Curtis L. Olson -- Wednesday 23 August 2006 04:45:
I'm really nervous about pasting over a serious bug like this. We
really need to get to the bottom of it. A quick hack like this will
only cause us to accumulate serious (but infrequent bugs) and eventually
We aren't pasting over this.
Curtis L. Olson wrote :
Frederic Bouvier wrote:
Is it supposed to work with the Garmin GPS III Pilot ? this is a portable
unit,
and it happens I own one.
BTW, 295 and 296 are portable too.
I think the answer is yes, it should work with the GPS III, But I don't
have one
* Melchior FRANZ -- Wednesday 23 August 2006 08:34:
Or we can revert all of Mathias' commits in the last four weeks.
This wasn't meant seriously, but rather just as an (undesirable) option
that would be better still than letting fgfs abort for no good reason,
and very frequently, too. Mathias
Ack! I might have screwed up the 737 aircraft in CVS. I think I tried
to copy a bunch of stuff out of the 737, but got the cvs directories too
(dumb) and then when I went to change/remove files to suit my new
aircraft, I didn't realize I was changing the 737 (because I wasn't in
that
Wednesday, 23 August 2006.
Subject: Re: [Flightgear-devel] apt.dat and debugging
I built FG using MSVC 2005, and the release build version works
great. I tried to step through the code using the debugger, but ...
What I did though was I have created a seperate FG root and use
that for debugging
Curtis L. Olson wrote:
Ack! I might have screwed up the 737 aircraft in CVS. I think I tried
to copy a bunch of stuff out of the 737, but got the cvs directories too
(dumb) and then when I went to change/remove files to suit my new
aircraft, I didn't realize I was changing the 737 (because
--- Curtis L. Olson wrote:
Question: what is the very best joystick, yoke, and rudder pedal
hardware available for FlightGear? Preferably USB based.
snip Curt singing the praises of Black Widow or Alienware ... ?
Well, I'd guess the CH products line are going to be high on the list. I
have
On Wednesday 23 August 2006 03:45, Curtis L. Olson wrote:
[snip...]
For what it's worth I can reliably trigger this bug by
running: fgfs --airport=N59 Once FG starts up, hit the v
key to switch to the outside view. This seems to trigger the
bug every time.
Thanks,
Curt.
Just tried it
Curtis L. Olson wrote:
So anyway, I'm looking for suggestions on the best flight controllers
available so these can be offered optionally with the computer package.
Unfortunately the sort of equipment they'd like to bundle with
FlightGear is not the same as Joe Average somehow FlightGear-
Question: what is the very best joystick, yoke, and rudder pedal
hardware available for FlightGear? Preferably USB based.
My best experience with simulation hardware was in a ELITE FNPT II simulator
(www.flyelite.ch) with forcefeedback yoke and pedals and a nice stack of fake
king
* Stefan Seifert -- Wednesday 23 August 2006 22:03:
Before Melchior's work-around I could reproduce the problem with fgfs
--disable-auto-coordination --aircraft=harrier --carrier=Nimitz
Just switch views and it crashes.
But you should still see the error message, as I put the return after
it,
Melchior FRANZ wrote:
* Stefan Seifert -- Wednesday 23 August 2006 22:03:
Before Melchior's work-around I could reproduce the problem with fgfs
--disable-auto-coordination --aircraft=harrier --carrier=Nimitz
Just switch views and it crashes.
But you should still see the error
On Wed, 23 Aug 2006, Stefan Seifert wrote:
Melchior FRANZ wrote:
But you should still see the error message, as I put the return after
it, to prevent the unjustified abortion, but not the justified complaint.
If it doesn't appear, then the bug went away.
It seems like it went away. I do not
Just wondering if it is possible to clip 2d instruments to keep
textures / text from sliding around on the panel /windshield:
AFAIK this has always been a limitation of the 2D panels.
Also could a groundspeed property be added to /velocities property
tree without too much
14 matches
Mail list logo