You want the debug builds (which can crash more than release builds, since it has extra checks in it to catch 'bad' values).
We don't want you to use debug mode or cheats while testing though. Those can & do cause issues if you don't know what your doing.
i might be able to do that, as i just went from 2.0 to 2.1 b5 on Thursday.
is it simply playing & reporting annoying stuff?
or are there specific things to do?
mission one annoyances noticed.
unable to set multiple structures with shift key.
queue orders doesn't seem to be working at all actually.
could it be that i changed the key mapping?
the build menu behaviour doesn't change regardless of being set to reopen or not.(it just wont re-open)
might i suggest its behaviour is changed to "closes" or "stays open until closed/replaced"
path finding is feels more responsive, though seems dumber.
after exiting game in windowed mode & restarting with normal shortcut, game resumes in windowed mode.
game wont start if you specify "--fullscreen"
have to change it back to fullscreen in video options.
specify that the game launches fullscreen unless specifically told not to?
alt-tab caused a hang of some kind
game became unresponsive
curser changed in reaction to the edge of the task bar & the buttons(smils etc) on this page, yet visually the game did not exit.
ctrl+alt+del did not bring up task manager, at least not visually.
winkey + L / L to log off & log on again to get back to desktop, didnt work, winkey + U / U didnt work.
had to hard off the system.
though this might be due to ati.