0.2.8.3_beta1: Release process and bugs

Post by **dlh** » Sat Jan 31, 2009 11:52 pm

No issues yet with linux package either. Tested on arch linux.

noob13 · Post by **noob13** » Sun Feb 01, 2009 3:58 pm

Tested 0.2.8.3_beta1 on Ubuntu 8.10 - Everything works great apart from one little thing.
Not sure if this is a bug in the game or somewhere else, but whenever i take a screenshot all the fonts in the console output and HUD components become "scrambled" (see image below). Its easily fixed by quickly switching to windowed mode and back, so it doesn't really bother me as such. Just thought i'd let you know.
Perhaps relevant information:
GL_RENDERER Mesa DRI Mobile Intel® GM45 Express Chipset 20061102 x86/MMX/SSE2
GL_VERSION 1.4 Mesa 7.2

Website · Post by **Z-Man** » Sun Feb 01, 2009 6:38 pm

There are known texture corruption problems that are the fault of the drivers (disabling Compiz helps there), but just to make sure it's not our png code, can you try bmp and png screenshots by toggling PNG_SCREENSHOT?

noob13 · Post by **noob13** » Sun Feb 01, 2009 7:58 pm

Yes, it seems to happen in both, PNG_SCREENSHOT 1 and 0. I guess its a problem with the driver then? I did about 30 tests and there was one exception when it didn't happen.

wrtlprnft · Post by **wrtlprnft** » Sun Feb 01, 2009 8:07 pm

have you tried binding your screenshot key to some other button (misc settings→global keyboard config)? AFAIK we do screenshots by grabbing the frame buffer after rendering, so there should be no way your buggy driver could know that this next frame is going to be snapshotted.

Maybe your screenshot key actually causes some external program to get active, destroying FTGL's textures…

noob13 · Post by **noob13** » Mon Feb 02, 2009 12:11 am

Yes, i thought about that too. PrtSc-key is default for taking screenshots in gnome, so i changed it to something completely different. Still, same effect.
This is most probably caused by my driver. Intel hasn't been too swift at releasing proper xorg drivers for this chipset, i'm still lacking a large bit of the performance it has on windows.
Fortunately its not a big problem, i get a steady ~100 fps with the new beta (even with a full grid), which wasn't the case with 0.2.8.2. Good work!

Post by **dlh** » Sat Feb 07, 2009 6:15 am

I know this branch is locked down but...

Could the /teams chat command also display the position numbers, for /shuffle usage, etc. Example:

Code: Select all

player 1          Position 2 (or #2)
     player 2     Position 1
player 3          Position 3

Also, maybe I missed it, but is there a command to show just your team's starting positions, and not all teams?

Website · Post by **Z-Man** » Sat Feb 07, 2009 1:20 pm

dlh wrote:I know this branch is locked down but...

Could the /teams chat command also display the position numbers, for /shuffle usage, etc. Example:
Code: Select all
player 1          Position 2 (or #2)
     player 2     Position 1
player 3          Position 3

I think that's doable.

dlh wrote:Also, maybe I missed it, but is there a command to show just your team's starting positions, and not all teams?

No, but how about /myteam?