Re: [Flightgear-devel] RenderTexture bug

2005-11-27 Thread Timo Saarinen
On Thu, 2005-11-24 at 10:06 +0100, Stefan Seifert wrote:
 I just wanted to note, that when it is clear, that it's a bug in ATI's 
 drivers, someone should post a bugreport in the ATI driver Bugzilla:
 http://ati.cchtml.com/
 This is actually a place where driver developers are watching and a good 
 chance that such bugs get fixed. Before posting, you should read the 
 instructions at: http://www.rage3d.com/board/showthread.php?t=33799828
 which is btw. a thread in _the_ most useful forum for Linux using ATI 
 card owners: http://www.rage3d.com/board/forumdisplay.php?f=88

I don't think it's ATI's binary driver fault. I have Ubuntu 5.10 with
open-source radeon driver for ATI Radeon 9250 SE. After compiling 0.9.9
and SimGear 0.3.9 the following messages are printed after fgfs startup:

[EMAIL PROTECTED] iso]$ /opt/fgfs/bin/fgfs
opening file: /opt/fgfs/share/FlightGear/Navaids/carrier_nav.dat
/opt/fgfs/share/FlightGear/Navaids/TACAN_freq.dat
X Error of failed request:  GLXUnsupportedPrivateRequest
  Major opcode of failed request:  143 (GLX)
  Minor opcode of failed request:  16 (X_GLXVendorPrivate)
  Serial number of failed request:  40
  Current serial number in output stream:  41

Timo



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


Re: [Flightgear-devel] RenderTexture bug

2005-11-27 Thread Timo Saarinen
On Sun, 2005-11-27 at 13:14 +0100, Frederic Bouvier wrote:
  [EMAIL PROTECTED] iso]$ /opt/fgfs/bin/fgfs
  opening file: /opt/fgfs/share/FlightGear/Navaids/carrier_nav.dat
  /opt/fgfs/share/FlightGear/Navaids/TACAN_freq.dat
  X Error of failed request:  GLXUnsupportedPrivateRequest
Major opcode of failed request:  143 (GLX)
Minor opcode of failed request:  16 (X_GLXVendorPrivate)
Serial number of failed request:  40
Current serial number in output stream:  41
 
 Why not installing an X11 error handler to trap this instead of letting the
 default handler simply exiting ?

How do I install an X11 error handler? This is completely new concept
for me. Quick googling didn't help much. Is there a command line option
or should I modify FlightGear source or even X11 source?

Timo



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


[Flightgear-devel] Autopilot bug?

2005-04-05 Thread Timo Saarinen
Hi,

I have tried the altitude and heading hold features of the autopilot (ctrl-A 
and ctrl-H with arrow keys or F11 autpilot dialog box). They work very well 
with j3cub aircraft but with the default cessna 172 either of them don't 
work at all. I suppose this is a bug.

-Timo

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


Re: [Flightgear-devel] Autopilot bug?

2005-04-05 Thread Timo Saarinen
On Tuesday 05 April 2005 21:22, Curtis L. Olson wrote:
 Timo Saarinen wrote:
 Hi,
 
 I have tried the altitude and heading hold features of the autopilot
  (ctrl-A and ctrl-H with arrow keys or F11 autpilot dialog box). They work
  very well with j3cub aircraft but with the default cessna 172 either of
  them don't work at all. I suppose this is a bug.

 The particular autopilot included with the default C172 (KAP-140) must
 be operated by clicking on the panel buttons.

Shouldn't the keyboard controls and the dialog be disabled then? Of course it 
would be nice to get some kind of message that you must operate the panel 
with mouse instead of the standard keyboard shortcuts.

-Timo

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


[Flightgear-devel] Problem with airport ENSB

2005-04-05 Thread Timo Saarinen
Hi,

Trying to start the Flightgear 0.9.8 with Svalbard airport ENSB (78 15 N  -  
15 30 E) the aircraft ends up to sea. I have correctly downloaded the tile 
and extracted it to correct location (Scenery/Terrain/e010n70). The Svalbard 
island can be seen east from the airplane. The other airports seem to work 
fine.

-Timo

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