Where did Tremulous go wrong?

[Nux]

remember each letter is 2 tris

Aren't there open-source text rendering engines out there for this? Like Freetype?

You know something's wrong when sprites eat more fps than models do.

which is a vacuous fact, because sprites do NOT eat more FPS than models.
however, LOS traces (up to 9 per buildable) do eat a lot of FPS. see the relevant bug report.

True, this FPS drop is caused by the traces. On the other hand it doesn't follow that "sprites" are fast. In fact just opening the armoury menu halves my FPS.

I imagine he was being pedantic and was simply comparing a single ideal sprite with some many-poly model. Regardless, there's always a way to code something simple, badly and this was the point of my post.

Am I to understand the reason the health-bars have these frequent checks, yet the models don't is because the health-bars are rendered above everything and so would show through walls otherwise? If so, why not simply make them obscurable?

[vcxzet]

yes, using pre-rendered static text could help a little
for example:
instead of drawing A R M O R Y you'd draw ARMORY
so instead of 6x2 tris you'd need 1x2 tris
(btw a full menu border is 4x2 tris )
(I use a fixed size menu/hud with (pre rendered at start) image background/foreground/words. It is readable at any resolution but covers more of the screen at low resolutions)

imho it might help a little. however adding low detail models would help more.

but hey you should just kill yourself if you have a video card that can't handle tremulous.

[TANK]

The buildables don't slow down the engine as much as you think:

ZOMG fps rate.
But its didn't solve problem for me.

What OS system, videocard/driver, trem_client?

I have on R Unlimited on Geforce 440(440 GT ~= 8800 GT) GT and Xubuntu 11.04 + Nvidia 270.41.06 Driver:

When i use build mode on UBP its can down to 12 fps.
Classic localhost EU like server:

[vcxzet]

lawl it is a bad comparison

you should stay at the same spot and maintain your PoV