[Flightgear-devel] [RFC] bug in $FG_ROOT/Input/Joysticks/Logitech/wingman-extreme-digital-3d.xml ?

2005-03-10 Thread Melchior FRANZ
It doesn't make much sense to have two joysticks identifying themselves
with the same name. I guess the second one cheats, when it says it is "Pro"!?

  $ grep 'Logitech Logitech Extreme 3D Pro' *.xml
  extreme-3d-pro.xml: Logitech Logitech Extreme 3D Pro
  wingman-extreme-digital-3d.xml: Logitech Logitech Extreme 3D Pro

Someone had a problem on IRC because his (non-"Pro") "Logitech Logitech Extreme 
3D"
was not recognized.

m.   ??

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Running Flightgear on Mac OS X

2005-03-10 Thread Felix
That did it! Rebuilt SimGear and FlightGear and fgfs fired right
up...Loaded quickly too. Very nice!!!

Thank you guys!
Felix


On Thu, 10 Mar 2005 11:53:47 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Felix,
> 
> Erik put into CVS a few hours ago a simgear/sound fix that will fix
> your problem.
> 
> You will still see a white box on a black background, but this time it
> will eventually end with one of the fg startup pictures being shown.
> 
> The problem was an infinite loop specific to mac os x that only showed
> up (I think) with gcc 3.3 and greater compilers (which is in the latest
> dev tools for mac os x) I think.  Earlier compilers didn't seem to have
> this problem (at least for me they didn't 8-)).
> 
> You can see which version of the compiler you have with
> 
> gcc --version
> 
> Mine is:
> 
> gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1671)
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is
> NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> I don't know why it's taking so long to put up a picture on the white
> box. It will need looking into on one of my better days (darned
> weather)! 8-)
> 
> It would definitely be calmer for users (at least THIS user) to see a
> picture on the splash screen as soon as possible after the white box
> (or hold displaying the white box until the picture is ready, but then
> users might think FlightGear is not  responding). Perhaps someone could
> figure out how to display a text message like "loading
> FlightGear-required components. Please wait." in the white box until
> the picture is ready for display. (All the pictures are cool, but I
> especially like the triplane picture, BTW).
> 
> Thanks to Eric for putting this in, and thanks to all the developers
> for the great flightsim AND for supporting Mac OS X!
> 
>  TTFN (ta-ta for now)
> 
> Best regards,
> 
> Ima
> 
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] Running Flightgear on Mac OS X

2005-03-10 Thread ima . sudonim
Felix,
Erik put into CVS a few hours ago a simgear/sound fix that will fix 
your problem.

You will still see a white box on a black background, but this time it 
will eventually end with one of the fg startup pictures being shown.

The problem was an infinite loop specific to mac os x that only showed 
up (I think) with gcc 3.3 and greater compilers (which is in the latest 
dev tools for mac os x) I think.  Earlier compilers didn't seem to have 
this problem (at least for me they didn't 8-)).

You can see which version of the compiler you have with
gcc --version
Mine is:
gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1671)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is 
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.

I don't know why it's taking so long to put up a picture on the white 
box. It will need looking into on one of my better days (darned 
weather)! 8-)

It would definitely be calmer for users (at least THIS user) to see a 
picture on the splash screen as soon as possible after the white box 
(or hold displaying the white box until the picture is ready, but then 
users might think FlightGear is not  responding). Perhaps someone could 
figure out how to display a text message like "loading 
FlightGear-required components. Please wait." in the white box until 
the picture is ready for display. (All the pictures are cool, but I 
especially like the triplane picture, BTW).

Thanks to Eric for putting this in, and thanks to all the developers 
for the great flightsim AND for supporting Mac OS X!

 TTFN (ta-ta for now)
Best regards,
Ima
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Re: Anyone using TomTom POI files for scenery

2005-03-10 Thread Martin Spott
"jj" wrote:
> I'd surely like to see an Observatory bulding (such as mine, see
> http://kingmont.com and ftp://kingmont.com for pictures of it).

We have the model in the database for some days - does anyone bother
refining a bit ? Please look here for a thumbnail:

  http://fgfsdb.stockill.org/modeledit.php?id=161

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Running Flightgear on Mac OS X

2005-03-10 Thread Erik Hofman
James Turner wrote:
It is pretty much impossible for any recent Mac to use software 
rendering - even a G3 iBook has some kind of Radeon in it as standard. 
What this could be is something that caught me ought the first few times 
- FG is now taking an looong to startup on OS-X, something on the order 
of 90 seconds on my PowerBook G4 1GHz.

The first few times I assumed it had hung, but then I waited and it 
actually got as far as showing the splash screen.

I have spent some time doing some profiling and spot timing of startup, 
and unfortunately there are no really obviously bad things happening; 
there's just an awful lot of work to be done, much of it greedily, and 
it takes a while. If you run with the logging level put back up (as it 
used to be), you can see all the work that's going on.
I've committed a patch from Ima Sudonim against SimGear (sound) that 
should take care of this. I've had this patch in my inbox for some time, 
but I'm rather busy lately.

Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Running Flightgear on Mac OS X

2005-03-10 Thread James Turner
On 10 Mar 2005, at 05:02, Josh Babcock wrote:
I've successfully compiled Flightgear from CVS (thanks for the help),
but for some reason it won't run. FlightGear loads and all i see is a
Black screen with a white box in the middle (where the splash screen
should be). The CPU usage goes to 100% and stays there until i kill
fgfs.
Sounds like it is using software rendering.  Do you have a 3D card and 
the appropriate driver installed?  It would help to know what OS, 
driver and 3D card you are using.
It is pretty much impossible for any recent Mac to use software 
rendering - even a G3 iBook has some kind of Radeon in it as standard. 
What this could be is something that caught me ought the first few 
times - FG is now taking an looong to startup on OS-X, something on the 
order of 90 seconds on my PowerBook G4 1GHz.

The first few times I assumed it had hung, but then I waited and it 
actually got as far as showing the splash screen.

I have spent some time doing some profiling and spot timing of startup, 
and unfortunately there are no really obviously bad things happening; 
there's just an awful lot of work to be done, much of it greedily, and 
it takes a while. If you run with the logging level put back up (as it 
used to be), you can see all the work that's going on.

Of course, your problem could be something completely unrelated - you 
could run under gdb and ctrl-c once it seems to have stopped, to find 
out where.

H&H
James
--
The lack of planning on your part does not constitute to an emergency 
on mine

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d