Re: [Flightgear-devel] fgfs not using direct rendering with xorg
Josh Babcock wrote: OK, I thought I was cool, but I'm not. When I got Xorg working, I forgot that there's a bug in sawfish that resets LD_LIBRARY_PATH and that I had a hack somewhere that was pointing apps to the old XFree86 radeon driver. So now that's fixed, and glxgears is great (and faster) and blender is happy, but fgfs has different ideas. It's obviously not using direct rendering. Did you recompile 'fgfs' after updating to Xorg ? tower:jbabcock$ ldd `which fgfs` [...] Oh man, what do you need all these shared libs for ? Just for comparison - to avoit typing too much ;-) /opt/FlightGear/bin/fgfs: libpthread.so.1 = /usr/lib/libpthread.so.1 (0x28515000) libz.so.2 = /lib/libz.so.2 (0x28539000) libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0x28549000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0x28582000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x285f5000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x2865a000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x2866e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x286b7000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x286bf000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0x286d6000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x286de000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x286eb000) libopenal.so.0 = /usr/local/lib/libopenal.so.0 (0x287aa000) libm.so.3 = /lib/libm.so.3 (0x28833000) libusbhid.so.1 = /usr/lib/libusbhid.so.1 (0x2884d000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x28851000) libc.so.5 = /lib/libc.so.5 (0x28923000) libXxf86vm.so.1 = /usr/X11R6/lib/libXxf86vm.so.1 (0x289fc000) These (or similars) should be sufficient. Could you try to recompile and link to only what's really necessary ? Also look at the permissions in /dev/dri/ and see if your UID belong to the respective user group, 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] fgfs not using direct rendering with xorg
Hi Josh, Josh Babcock wrote: OK, I thought I was cool, but I'm not. When I got Xorg working, I forgot that there's a bug in sawfish that resets LD_LIBRARY_PATH and that I had a hack somewhere that was pointing apps to the old XFree86 radeon driver. So now that's fixed, and glxgears is great (and faster) and blender is happy, but fgfs has different ideas. It's obviously not using direct rendering. I'm getting about 1/3 FPS about of it, the same I get with GL_ALWAYS_INDIRECT=1. You have to make sure that most options like Enhanced runway lighting, Specular highlight and 3d clouds are turned off. These might trigger some functions that make the driver fall back to software rendering. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs not using direct rendering with xorg
Erik Hofman wrote: Hi Josh, Josh Babcock wrote: OK, I thought I was cool, but I'm not. When I got Xorg working, I forgot that there's a bug in sawfish that resets LD_LIBRARY_PATH and that I had a hack somewhere that was pointing apps to the old XFree86 radeon driver. So now that's fixed, and glxgears is great (and faster) and blender is happy, but fgfs has different ideas. It's obviously not using direct rendering. I'm getting about 1/3 FPS about of it, the same I get with GL_ALWAYS_INDIRECT=1. You have to make sure that most options like Enhanced runway lighting, Specular highlight and 3d clouds are turned off. These might trigger some functions that make the driver fall back to software rendering. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Ok, in answer to some previous questions, yes, I did recompile after switching the LD_LIBRARY_PATH, and I also just recompiled with Melchior's LDFLAGS but to no avail. Here are my rendering settings as of now: Contents of /sim/rendering fog (fastest) shading (true) skyblend (false) textures (true) wireframe (false) horizon-effect (false) enhanced-lighting (false) distance-attenuation (false) specular-highlight (false) bits-per-pixel (16) debug (false) realism (5) static-lod/ random-objects (false) draw-otw (true) specular-lighting (false) If I set draw-otw to false, I get a sky colored screen, with occasional flashes of torn view that look like a horizontal band of what I should be seeing taking up about 1/6 to 1/4 of the screen. The flashes probably only last one frame, and do not occur every frame. The framerate is way up though. I'm not sure where the BPP number comes from, I'm running my xserver at 24 BPP. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs not using direct rendering with xorg
On Wed, 13 Apr 2005 12:37:35 -0400, Josh wrote in message [EMAIL PROTECTED]: Contents of /sim/rendering ... bits-per-pixel (16) ... ... I'm running my xserver at 24 BPP. ..make up your mind. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs not using direct rendering with xorg
Arnt Karlsen wrote: On Wed, 13 Apr 2005 12:37:35 -0400, Josh wrote in message [EMAIL PROTECTED]: Contents of /sim/rendering ... bits-per-pixel (16) ... ... I'm running my xserver at 24 BPP. ..make up your mind. ;o) *I* did. Unfortunately my X has a mind of its own. Actually, I think I am dealing with a symlink problem in my Xorg install as a result of me installing Xorg improperly. I'm in the process of reinstalling all my Xfree libs, which subsequently got blown away. I have to get this stuff in order before I will know how accurate the info I was getting before is. This is probably all due to having the wrong libs in the wrong places. More to come. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] fgfs not using direct rendering with xorg
OK, I thought I was cool, but I'm not. When I got Xorg working, I forgot that there's a bug in sawfish that resets LD_LIBRARY_PATH and that I had a hack somewhere that was pointing apps to the old XFree86 radeon driver. So now that's fixed, and glxgears is great (and faster) and blender is happy, but fgfs has different ideas. It's obviously not using direct rendering. I'm getting about 1/3 FPS about of it, the same I get with GL_ALWAYS_INDIRECT=1. Both glxgears and fgfs are pointing at the same libs: tower:jbabcock$ ldd `which fgfs` libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7fc6000) libz.so.1 = /usr/lib/libz.so.1 (0xb7fb3000) libSDL-1.2.so.0 = /usr/lib/libSDL-1.2.so.0 (0xb7ec3000) libglut.so.3 = /usr/lib/libglut.so.3 (0xb7e97000) libGLU.so.1 = /usr/local/X11R6.8/lib/libGLU.so.1 (0xb7e1d000) libGL.so.1 = /usr/local/X11R6.8/lib/libGL.so.1 (0xb7db1000) libXmu.so.6 = /usr/local/X11R6.8/lib/libXmu.so.6 (0xb7d9b000) libXt.so.6 = /usr/local/X11R6.8/lib/libXt.so.6 (0xb7d49000) libSM.so.6 = /usr/local/X11R6.8/lib/libSM.so.6 (0xb7d4) libICE.so.6 = /usr/local/X11R6.8/lib/libICE.so.6 (0xb7d28000) libXi.so.6 = /usr/local/X11R6.8/lib/libXi.so.6 (0xb7d2) libXext.so.6 = /usr/local/X11R6.8/lib/libXext.so.6 (0xb7d12000) libX11.so.6 = /usr/local/X11R6.8/lib/libX11.so.6 (0xb7c47000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7c43000) libopenal.so.0 = /usr/local/lib/libopenal.so.0 (0xb7bab000) libm.so.6 = /lib/tls/libm.so.6 (0xb7b89000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7acf000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0xb7ac6000) libc.so.6 = /lib/tls/libc.so.6 (0xb7992000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0xb7fea000) libartsc.so.0 = /usr/lib/libartsc.so.0 (0xb798b000) libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0xb7987000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0xb7982000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0xb7902000) libesd.so.0 = /usr/lib/libesd.so.0 (0xb78fa000) libaudiofile.so.0 = /usr/lib/libaudiofile.so.0 (0xb78d6000) libaudio.so.2 = /usr/lib/libaudio.so.2 (0xb78c) libvga.so.1 = /usr/lib/libvga.so.1 (0xb785b000) libaa.so.1 = /usr/lib/libaa.so.1 (0xb783f000) libasound.so.2 = /usr/lib/libasound.so.2 (0xb778c000) libXxf86vm.so.1 = /usr/local/X11R6.8/lib/libXxf86vm.so.1 (0xb7787000) libncurses.so.5 = /lib/libncurses.so.5 (0xb7747000) libslang.so.1 = /lib/libslang.so.1 (0xb76d4000) libgpm.so.1 = /usr/lib/libgpm.so.1 (0xb76ce000) tower:jbabcock$ ldd `which glxgears` libGL.so.1 = /usr/local/X11R6.8/lib/libGL.so.1 (0xb7f7d000) libXp.so.6 = /usr/local/X11R6.8/lib/libXp.so.6 (0xb7f74000) libXext.so.6 = /usr/local/X11R6.8/lib/libXext.so.6 (0xb7f66000) libX11.so.6 = /usr/local/X11R6.8/lib/libX11.so.6 (0xb7e9b000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7e78000) libm.so.6 = /lib/tls/libm.so.6 (0xb7e56000) libc.so.6 = /lib/tls/libc.so.6 (0xb7d22000) libXxf86vm.so.1 = /usr/local/X11R6.8/lib/libXxf86vm.so.1 (0xb7d1c000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7d19000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0xb7fea000) and with GL_DEBUG=verbose I can see that dri is happy and obviously using direct rendering: tower:jbabcock$ glxgears -info libGL: XF86DRIGetClientDriverName: 4.0.1 r200 (screen 0) libGL: OpenDriver: trying /usr/local/X11R6.8/lib/modules/dri/r200_dri.so drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports pci::01:00.0 libGL error: Can't open configuration file /etc/drirc: No such file or directory. libGL error: Can't open configuration file /home/jbabcock/.drirc: No such file or directory. GL_MAX_VIEWPORT_DIMS=4096/4096 GL_RENDERER = Mesa DRI R200 20040929 AGP 4x x86/MMX+/3DNow!+/SSE TCL GL_VERSION= 1.3 Mesa 6.2.1 GL_VENDOR = Tungsten Graphics, Inc. GL_EXTENSIONS = GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_convolution GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_histogram GL_EXT_packed_pixels GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_stencil_wrap
