Menu display: potential bug

Monkey · Post by **Monkey** » Fri Aug 29, 2008 8:11 pm

1) I had the menu open in a window and it looked fine.
2) I switched to another vitual workspace in my window manager (fluxbox).
3) I loaded firefox then did some reading and closed it.
4) I switched back to the workspace with the Arma window in it and it looked like the first image below.
5) I pressed the fullscreen key to switch from windowed and it looked fine again.
6) I switched workspace and then switched back again. It looked like the second image below.
7) I restarted Arma and now I can not reproduce this bug.

Note that I took the screenshot using the Arma screenshot function. I am running latest 0.2.8_alpha on Linux with an ATI Radeon 9200.
GL_RENDERER Mesa DRI R200 20060602 AGP 4x x86/MMX+/3DNow!+/SSE TCL
GL_VENDOR Tungsten Graphics, Inc.
GL_VERSION 1.3 Mesa 7.0.2

Shall I file a bug report on Launchpad? If so, what other info should I include?

Post by **epsy** » Fri Aug 29, 2008 9:29 pm

99% chances this is an upstream bug

Post by **Tank Program** » Fri Aug 29, 2008 9:49 pm

Looks like how a bug in the graphics drivers would manifest.

Monkey · Post by **Monkey** » Sat Aug 30, 2008 12:51 am

http://forums.armagetronad.net/viewtopi ... 015#198839

Fonkay · Post by **Fonkay** » Sat Aug 30, 2008 11:04 am

I think the first shot looks purty.

It should look like that all the time.

Jonathan · Post by **Jonathan** » Sat Aug 30, 2008 11:27 am

write_garbage_over_texture_before_upload();

Monkey · Post by **Monkey** » Sat Aug 30, 2008 2:29 pm

The bug has happened again. Here are some more "purty" pictures:

Post by **Tank Program** » Sat Aug 30, 2008 4:06 pm

Is it only affecting text? Something with textured rendering then?

Post by **epsy** » Sat Aug 30, 2008 5:52 pm

i got it to reproduce on trunk with the intel(NOT i810) driver, only with XAA on instead of EXA
it does only work on first start after booting and happens in other OpenGL/SDL games

edit: read: it only happens on first start after booting

definitely upstream

Monkey · Post by **Monkey** » Sun Aug 31, 2008 4:34 am

So am I correct in thinking that this is yet another Mesa related bug?

Post by **epsy** » Sun Aug 31, 2008 7:02 pm

XAA and EXA are handled by the gfx driver, so yes
one of the things which i find strange is that it doesnt only happen to 2D surfaces (HUD and text) but also to some textures

Website · Post by **Z-Man** » Sun Aug 31, 2008 9:23 pm

epsy wrote:XAA and EXA are handled by the gfx driver, so yes
one of the things which i find strange is that it doesnt only happen to 2D surfaces (HUD and text) but also to some textures

Umm, HUD and text are textures as well, not 2D surfaces

And just because it's common in may games does not mean it's a driver bug. In fact, a simple rebuilding of textures (like it's done when you toggle the fullscreen mode) when the arma gets visible again (which we're notified of) may fix this. I just committed the code to bzr.

ivantis · Post by **ivantis** » Wed Sep 10, 2008 12:11 am

dude, there are like a bazillion graphics bugs. stuff like that happens all the time. or maybe its only me. ever get something like this?:... i cant take a screenshot, but sometimes when im connecting to the master server, i open another window like firefox, and it shows the arma window through the firefox window.

Post by **Tank Program** » Wed Sep 10, 2008 12:26 am

It sounds like a compositing window manager sort of thing. Sure you can't get a screen shot? (A photo graph of the screen itself perhaps?)

"Dude, there's like a bazillion graphics bugs" isn't very helpful.

ivantis · Post by **ivantis** » Wed Sep 10, 2008 12:36 am

i cant get a screenshot. when i try to take a fullscreen screenshot, it hides behind the window again (its afraid youre going to bugfix it)