On Thu, 24 Feb 2005 08:03:36 +0100, Jorge wrote in message <[EMAIL PROTECTED]>:
> On Tue, 22 Feb 2005 11:09:04 +0000 > Steve Hosgood wrote: > > > If I just type "fgfs" or "fgfs --disable-sound", all I get is the > > splash screen and plenty of disk-grinding noises followed by the > > splash-screen disappearing and the single-word message "Killed" on > > stdout. (I tried the --disable-sound option to try and avoid > > possible troubles with OpenAL). > > > > (...) > > > > It does seem that the length of time between the splash-screen > > appearing and the "killed" (or "aborted") message might be dependant > > on the amount of RAM (or maybe the amount of swap) available. > > > > Actually, I've seen the exact same behaviour, and even managed to see > how fast RAM was being filled, by switching to a terminal and using > the "top" command. > > My system : > laptop > P4 2.4GHz > 1Gb RAM, 800Mb swap > ATI Radeon Mobility 9000 ..' lspci -v |grep -A 15 VGA '? (My 9250 on DRI is reported as a 9200 PRO) > Mandrake 10.1 > Linux kernel 2.6.8.1 > xorg 6.7.0, "radeon" open-source driver > > When the fgfs process reached 1.8Gb, it got killed by the kernel's > "out-of-memory killer" (I saw it in /var/log/messages afterwards). > > glxinfo said that direct rendering was enabled, but my fgfs (CVS > compile from a few days ago) behaved the same as Steve's. I haven't > had a chance to try it with Simon's suggestion (disabling dlists) yet. > > However, I have managed to make ATI's closed-source "fglrx" driver > work now, and have had a nice increase in the framerate, compared to > what I had with the "radeon" driver on XFree86 4.3.0 (which I had > before I switched to xorg). > > Here's a table to sum up what I have found using different drivers > > (fgfs figures are for sparse areas, at a reasonable altitude i.e. near > the ground or on the ground, and for a default visibility value). > > without acceleration > glxgears ~240fps, fgfs ~1fps > > XFree86 4.3.0, open-source "radeon" driver > glxgears ~2100fps, fgfs ~5-25fps depending on view direction (?) > I usually had to disable specular highlight... > > xorg 6.7.0, open-source "radeon" driver > glxgears ~2180fps, fgfs ~35-50fps (yay!!) > specular highlight enabled > > All this may point to the fact that the 3D driver is often responsible > for these drops in framerate, maybe because of unsupported features > that make the driver fall back to indirect rendering. > > Which brings us back to try and detect features at runtime ? Is this > possible ? ..yes, even while booting up the box; for an example, boot a knoppix with ' expert ' on the boot command line. -- ..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
