clever_nick_here

I can't play 0ad currently. The problem seemed to start when mesa and related packages were updated to mesa 10.3.1-1, though this could have been a coincidence as i don't get to play but once a week or two. I was still using 0ad 16.4(? or whatever was previous to 17.1 in arch repos) then. the problem persists with 17.1 unfortunately. the problem: when i start 0ad the graphics are very corrupted looking and i can't get any button in 0ad gui to do anything except make input sound effects. 0ad also shows javascript errors. I have to exit runlevel 5 and restart gdm to get back to my desktop, though there may be a shortcut i'm not aware of to get out of crashed 0ad. thanks in advance crashlog.txt

thanks for the info. my rendering stays somewhere between 15ms and 25ms(30 maybe?) but sim update is spiking to 125-210ms or so right at/after the freeze occurs so i'm guessing it has something to do with that (unless that's just a coincidence/indirectly related and is within acceptable limits). I'm not seeing anything else taking any time to speak of. also, turning off all graphics extras in settings doesn't seem to have a noticeable effect and i never had to turn any of that off before, either(assuming i keep it at or below 3 players on a 4 player map with default pop limit).

well i certainly don't mean to criticize anyone's work. 0ad is the only game i play. just seems like it's something with the game to me, but i'm not 100% sure that a package update didn't cause it. environ details: mesa and related: 9.1.1-1, xf86-video-ati: 1.7.1.0-3, xorg 1.14.0-2, linux 3.8.5-1.

this appears to be a regression. I think there was a previopus alpha that did this(2-3 versions back?). my desktop is fairly well spec'd (fx8350, 16GB 1866mhz ram, 990fx MB, Radeon HD 5800 Series) and the previous alpha ran just fine at least until 3-4 players on 4 player map with all eye candy had reached their full population, chaotic war on all fronts, etc. Now it's freezing as if on a timer from early in the game.