On Tue, 29 May 2007 09:34:43 -0400 Dennis Schridde <[EMAIL PROTECTED]> wrote: >Am Dienstag, 29. Mai 2007 schrieb [EMAIL PROTECTED]: >> I no sure if I am only one, but game not playable with all >asserts >> going off. Would be better to still assert, and then activate a >> forced crash so we can find all problems? We need this so we can >> get stack dump, to find what is going on. >> (in debug builds, so not to mess release builds) >> I have to go back hundreds of revision to get back to playable >game. >There is branches/2.0 for stable and playable games... > >> Problem must be stack corruption some place I think. Maybe bad >> code, but we must fix problems, back to a playable state. >> >> Maybe devs will stop with code modification and now everyone go >on >> bug(s) hunt? >You are using SVN trunk, after all. If you want something stable, >use 2.0. > >Sure even the trunk shouldn't crash all the time, but lately I >heard several >people saying that it got quite stable again and they even played >a network >game which lasted significantly longer than an hour. So it can't >be all that >bad. > I mean if you start play game in debugger, then you can no longer play without getting assert dialogs. Then you must hit i (ignore) every few moves. If you play game with no debugger or play 'release' builds, then, yes, you can play it without those dialogs, bad data don't crash game. This is what I mean when I can't play game. Before builds, I never saw asserts while play game in debugger. I use debugger to finds memleaks, and other errors. If someone has lots time, enable #define DEBUG_MEMORY for MSVC, even on dual core 3GHz system, it is very slow. I tried over 35 mins, and didn't get to any game.
-- Click to find great rates on health insurance, save big, shop here http://tagline.hushmail.com/fc/CAaCXv1QUc1I4bT63UTLWT0DdHvqXiRR/ _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
