[PlayerStage-Gazebo] Hardware 3D rendering with CVS Gazebo

[Armin M. <mue...@in...>]

Hi,

I tried the latest cvs version of gazebo.=20

If I use a camera (ObserverCam or SonyVID30) the simulation is running very=
=20
slow. After looking into the output of .gazebo I found that the pbuffer=20
rendering extension isn't present and looking again at the output of=20
configure I found:

checking whether glXCreateGLXPbufferSGIX is declared... no

After setting CPPFLAGS=3D"-DGLX_GLXEXT_PROTOTYPES=3D1" I ran configure agai=
n and=20
now glXCreateGLXPbufferSGIX was declared. After recompiling everything I ge=
t=20
now a segmentation fault, every time I run gazebo. The output of gdb is:

gdb gazebo
GNU gdb 6.1-debian
(gdb) run example1.world
Starting program: /usr/wiss/muellear/local/public/sarge/bin/gazebo=20
example1.world
[Thread debugging using libthread_db enabled]
[New Thread -1226775904 (LWP 21620)]
*** Gazebo 0.5 ***
using display [:0]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226775904 (LWP 21620)]
0x08067d56 in GLContext::InitSGIX (this=3D0x8102730) at GLContext.cc:136
136         config =3D configs[i];
(gdb)

Without the pbuffer rendering extension I can only use the camera with a=20
resolution of 160x120, otherwise software rendering is too slow. Any ideas?

Armin

PS:
I'm running debian unstable on an Athlon XP 2600 with an ATI Radeon 9200. I=
=20
tried both the radeon and the fglrx driver for XFree86.
OpenGL version string: 1.2 Mesa 4.0.4

=2D-=20

=B8=B8,=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=
=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0=
`=B0=BA=A4=F8,=B8=B8

Armin M=FCller
Technische Universit=E4t M=FCnchen             Tel: +49 89 289 - 17750
Lehrstuhl f=FCr Informatik IX                Fax: +49 89 289 - 17757
Boltzmannstrasse 3          http://www9.in.tum.de/people/muellear/
D-85748 Garching bei M=FCnchen               Arm...@in...