On Friday 25 July 2003 21:56, Matevz Jekovec wrote:
> I have PII 333 Mhz with GF2MX 32MB on PCI and 256 MB of SDRAM. I have
> Abit LX something motherboard and SBAWE64 on ISA (I'm about to buy Live!
> in the next few days). I would like to run FGFS smoothly (that's about
> 15-20 FPS) on GNU/Debian Linux unstable and using the latest nVidia
> Linux drivers.
> By using the latest CVS version I noticed the following things:
> 1) In mode 24 bpp, FlightGear ran faster than in 16 bpp (I also switched
> the Xfree depth to 24 and 16 then). Is there any known explanation (I
> haven't made benchmark, but judging by the eye I thought it was faster)
> for this. I think it's the textures fault as they are in 32 bit palette
> maybe? (including alpha channel) And FlightGear needs to calculate
> approximates to 24 output palette then?
I'm using Debian unstable too - have you tried including the line
DefaultFbBpp 32
in your XF86Config-4 for 24 bpp mode? This will be in the Screen section and
you can add it below the
DefaultDepth 24
entry. Make sure you have a back-up copy of XF86Config-4 before you change it
and also that you'll be able to re-instate it from the console if it goes
badly wrong and X won't load. It might, or might not make a difference. I
have to run FG in 16bpp on my MGA G550 32MB to get decent frame rates.
> 2) The resolution I had on my X was 1024x768 all the time and I wanted
> to run FlightGear in 800x600, but had no luck. There was a sign when
> starting up that it is about to run in 800x600 mode, but when switching
> to fullscreen, the X mode still stayed 1024x768. I have the possible
> resolution set in xfree86 config file and ctrl+alt++/- work fine and
> others applications do change the resolution as well. Is there any
> parameter to set FlightGear to change the system resolution and runs in
> that in fullscreen? (I searched for man pages, but haven't found
> anything) I know it worked in Windows some days.
As Curt says, FG won't change your screen resolution. I run FG at 1280x960
and then CTRL+ALT+'+' a couple of times to change the X display res down to
match the window. I've not had any problems re-sizing the window when FG is
running.
> 3) --disable-textures parameter is not working.
> 4) Any way to limit the texture size to at most 256*256 or 512*512
> pixels, because when starting up, the limit of 2048*2048 is set AFAIK.
As Curt says, delete the Textures.high directory - sadly, that's what I have
to :(
> 5) Around the default KFSO, the framerate is way slower than in e.g.
> Slovenia. Is there any way to fix that (I know there are way more
> objects, but still I think it should be faster than 6 FPS when looking
> to the city or airfield)
Is that fps in cockpit view or chase view? I get that sort of fps in chase
view at KSFO too, but if in chase view there's also the a/c texture overhead
as well. KSFO is pretty heavy especially if you've still got the high res
textures.
> 6) I tried to disable clouds (and sky blending? Is this the same thing
> because when sky blending is off, there are no clouds) and FPS increased
> from KSFO 5 FPS to about 9, 10 FPS.
> 7) By increasing FOV, the framerate decreases drasticly. I would really
> like to enjoy in a bit wider FOV when playing, but it really hits the
> FPS. Is this normal?
> 8) By decreasing visibility, the framerate increases drasticly. I like
> that:)
> 9) LJLJ airfield (Slovenia) was more or less playable (about 15 FPS
> average) with turned clouds on.
> 10) Sunsets look really nice!:)
>
> - Matevz
The sunsets are lovely - I do lots of flying at dusk just because of them.
Big thanks for your effort Erik.
LeeE
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
