Spring RTS Engine

Argh wrote:Even so... you know how people are about drivers... it'd be safer to just make sure that the behavior can't happen, tbh.

absolutely, engine fixes for both command lines and water are in master.

it seems catalyst 10.2 fixed this problem. need independent confirmation.

it's really simple: got more than 3GB memory on board? go 64bit.

this infolog doesn't have a crash in it - looks like you've just entered the menu, or something.

i was confused by "don't click on the icons". it wasn't very intuitive that they're not clickable, might want to revisit that part. maybe show a "don't click, let alt go" message or something.

2) On ALL maps, resources are scattered all over the map, and they are never really defended by chokepoints. This is imo exactly the reason why we never see T2 in 1v1 games. It would be very interesting to see how BA plays with "starcraft-esque", "chokey" maps, with snakey, long...

probably because there's no address space left and/or the crash happens in the gfx driver.

Spring 0.81.1.3 (0.81.1.3-0-g725801c{@}-cmake{MT}-mingw32MT-Sim)

doesn't look like you used the version you linked.

i think you may be onto something. haven't tried it though.

just found out about it, and it's absolutely made of pure awesome. fonts need to be prettier (all caps is ugly) but very, very well done otherwise.

lemme check that out. edit: master+ca 6796 (stable) works for me.

got more fixes done. turns out /water 1 and /water 3 were leaking texture memory - glBindTexture(GL_TEXTURE_2D, 0) fixed them. removed immediate mode from there for great justice. moral: clean up after yourself... edit: i guess i'll have to change the topic - from 'do not' to 'avoid if possible beca...

compositing on linux has a history of breaking spring in interesting ways, it's best to disable it anyway. it's also a good idea to play spring in a fullscreen window instead of native fullscreen.

try 9.7.

also, disable reflective (and/or refractive) water.

which driver version you updated to? the one from the infolog is extremely old.

update gfx drivers and post infolog.

if you had a hard lock such that even the magic sysrq didn't work (don't know if you tried it), it's definitely not spring's fault.

unimatrix wrote:Apparently you cannot connect while the game is in progress.
Why doesn't anyone bother to mention this? It's not that obvious, especially if you just want to spectate. In fact it's counter-intuitive as most games out there will allow it.

i haven't heard of a single RTS game that allows it.

BA has it disabled by design. Play a different mod, like XTA.

btw reported this problem on that amd survey site.