Debian testing/etch and wierd FPS problems

[DarkCarnival]

Preemptive strike: Lava, don't mention MS -- it is *NOT* a solution

Ok.. On the the real topic.

I have this:
E6600 Core 2 Duo @ 3.3gHz
8800GTX 768MB
4GB DDR2-800 @ DDR2-1000 (can't remember timings, though near-standard)

The system itself is Debian 64bit, installed from an etch netinstall cd (so it's currently using the 'testing' branch!).

Drivers are fetched from Nvidia's homepage, 9755 and 32bit compat-libs were installed alongside the driver package itself.

When I go inside tremulous I change my resolution to 1280x1024 and set everything to high. Some maps it runs with 70-90'ish FPS and others can get it as low as 20FPS which *obviously* screams to me that something is wrong here..
Aside from resolution I've just left it as it was during boot-up.. All on high..


Now.. I have a laptop like so: 2gHz Pentium M, 2gb ram and 7800GTX go and it runs trem with most on high at a resolution of 1920x1200 so surely my pc should be able to run tremulous at 1280x1024 with all on high....

[next_ghost]

If you want help, post these things:
1) per-map framerates
2) tremulous terminal output (standard error).

[tomek-k]

and are you using the procompiled x86 version or you compiled trem yourself (for x86_64)?

Yes - I read all your post and noticed the part about ia32 compat drivers, but it's better to be sure

[DarkCarnival]

Unfortunately I'm still using the 32bit binary seeing as the installer won't present me with the option of installing the sourcecode anymore.. This option disappeared after my first install.


As for per-map framerates.. What do you mean ? Are there timedemos or somesuch that I can run to give a better clue of the performance ? As for the stdout output, I'll try and run the game and if something interesting happens to surface, I'll be sure to post that !

Thanks in advance

[tomek-k]

The x86 binary is still a better choice - the 64bit version runs slower (for some people the slowdown is almost unnoticable, for others its a big slowdown - it's caused by the q3 engine as some of it's parts are written strictly for 32bits) and that's why I've asked about that.

As for the maps - some of them are known to have low framerates in specific locations.
eg. uncreation in the default human's base or transit (in general I think).


But there could be some issues with your gfx driver's configuration. Maby xorg.conf or nVidia Settings (a GUI tool to configure some settings of the driver) would be helpful.
If you've installed the drivers by the nVidia Installer then the Nvidia Settings shortcut should appear in the menu of your graphical environment (or just run nvidia-settings from console, as a normal user - it does not require root priviliges)

[DarkCarnival]

Well I just compiled a 64bit binary and that solves all my slowdowns I'm now running all @ highest settings and things are yielding a consistent 90FPS (I think the com_maxfps is set to 90 ? ). So all is good

I definitely recommend at least trying to make a 64bit build if a person has FPS problems.

Maybe it's got to do with the fact that the new binary is built against my own libraries, who knows ?

Anyway.. All is good now and so I'm happy ! =)

Thanks anyway

[Caveman]

My advice would be to set com_maxfps to 43|76|123

[kevlarman]

My advice would be to set com_maxfps to 43|76|123

that's 125, not 123

[Caveman]

aye, i stand corrected