You know that statement sounds as hollow as a drum, right?
If you actually care about a feature (which implies you would want it to become "better and more reliable", assuming that wasn't already true), you don't rely on others to do the testing. Example: SSMF.
If you do not care or test, there is neither any point in expecting it to nor in saying you will start using said feature only when it does, other than to casually express a useless to anyone (and unfounded?) opinion about its current state.
So what did you really want to say?
Last edited by Kloot on 07 Mar 2012, 13:01, edited 1 time in total.
I tested a little in singleplayer vs bot. My commander stucks near solars very often. http://img407.imageshack.us/img407/677/ ... rstuck.png He don't moving. For example, if I queue to build solars, it can buid some and stuck. Especially if there are wreckages (dead units) near.
I tested at work in a free time. So demo is very stupid. But commander stucks: I give orders at 04:00 -> stuck at 06:00 I give orders at 06:15 -> stuck at 06:50 I give orders at 07:28 -> stuck at 07:40
Don't worry, even stupid demos showing a bug (one that was not even related specifically to QTPFS in this case) are infinitely more valuable and helpful to us than vacuous "feedback" of the kind given earlier.
If you get bored enough to test at work again (which is awesome), grab this installer.
I tested 87.0 again on another map (tabula-v4) and commander stucks a lot during reclaim (with release version 87.0): http://www.2shared.com/file/BHOfsfyu/20 ... v4_87.html take a look at commander at 21:00 - 23:00 ------------------------------------------------ Also, I tested your new build and looks like commander does not stuck anymore during reclaim, but it still stuck sometimes during build and then skip 1 element from queue: http://www.2shared.com/file/h1zuHXly/demos.html take a look at commander at 01:50 - 02:20 (skips llt) 13:20 - 14:00 (dragin's eye) 14:50 - 15:20 (dragin's eye) Also, AI did nothing. Maybe because I see a lot of "Warning: Waiting packet limit was reached for invalid AI #0 [packets dropped]" warnings. Infolog also attached. Take a look at AI at 35 minute for example. It should be the hardest AI and he did nothing.
grab this installer.
P.S. I like portable spring version more than installer version
Users browsing this forum: No registered users and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum