| www.ClassicTW.com https://mail.black-squirrel.com/ |
|
| Move Delay https://mail.black-squirrel.com/viewtopic.php?f=52&t=30567 |
Page 1 of 1 |
| Author: | Parrothead [ Mon Nov 08, 2010 4:09 am ] |
| Post subject: | Move Delay |
Testing on Toyman's beta site has no move delay. Moving thru 3 sectors with hitting or dropping figs averaged 112 ms. Packet holding time is still 100 ms as verified on a local server with ckping. Therefore it is now impossible to hit anyone with anything on BETA unless they STOP in a sector to twarp out etc. I don't have the fastest puter but (time - ping) per move is about 102 per move + another 100 for the twarp lock out. setprecision 10 send "*" waitfor "(?=Help)? :" getTimer $startTicks gettime $time1 "ss:zz" settexttrigger xone :_xone "]:[15656] (?" send "m 16530* m 11040* m 3507* m15656*yy" pause :_xone getTimer $stopTicks setVar $durationTicks ($stopTicks - $startTicks) setVar $seconds ($durationTicks / 2790000000) gettime $time2 "ss:zz" write "00.txt" $seconds& " "&$time1&" "&$time2 send "m23907*yy" "00.txt" 0.7374881312 05:109 05:843 0.6662779140 14:390 15:46 0.6838038366 12:937 13:625 ---------------- Min: 219 Max: 297 Average: 252 High/Low Removed Average: 251 Min:Max Split: 78 Mild Intermittent Lag Detected -- I want Mango Cream Pudding! You do the math. No move delay. Just processing time for the game. Increase Time when fig attack/fig lay added send "m 16530* za999* f1*ct m 11040* za999* f1*ct m 3507* za999* f1*ct m15656*yy" 0.8969576753 28:375 29:296 0.9346597244 31:718 32:671 0.9318180667 04:828 05:765 While killing enemy figs....not much difference 0.9813719022 14:515 15:484 0.9269804308 19:781 20:703 0.9118322387 16:937 17:843 |
|
| Author: | Singularity [ Mon Nov 08, 2010 4:15 am ] |
| Post subject: | Re: Move Delay |
LOL. Yeh, that needs fixed. |
|
| Author: | Parrothead [ Mon Nov 08, 2010 4:53 am ] |
| Post subject: | Re: Move Delay |
Why was it broken in the first place? We need to set MD to 1/4 from zero and retest. |
|
| Author: | Singularity [ Mon Nov 08, 2010 5:02 am ] |
| Post subject: | Re: Move Delay |
Factoring out your initial ping, it looks like 2 move delays are happening... just the others aren't. I'll do some research on what's left of HHT and let you know. |
|
| Author: | Singularity [ Mon Nov 08, 2010 5:21 am ] |
| Post subject: | Re: Move Delay |
Ok. I'm not a fan of getTimer because CPU cycles can actually vary based on power draw in modern CPUs. So I used a gettime approach, it's a little less percise but good enough for determining this stuff. I also use a leading and trailing bit of text so I can time just the macro, factoring out my ping. Code: # --------------------------------------------------------- setVar $macro "m20210*<" # --------------------------------------------------------- killTrigger macro_start killTrigger macro_end setTextLineTrigger macro_start :macro_start "Average Interval Lag:" setTextLineTrigger macro_end :macro_end #179 & "Turns " setVar $macro "@" & $macro & "/" send $macro pause # --------------------------------------------------------- :macro_start getTime $start "hh mm ss zz" pause :macro_end getTime $end "hh mm ss zz" getWord $start $hh 1 getWord $start $mm 2 getWord $start $ss 3 getWord $start $zz 4 setVar $start_mm (($hh * 60) + $mm) setVar $start_ss (($start_mm * 60) + $ss) setVar $start_ms (($start_ss * 1000) + $zz) getWord $end $hh 1 getWord $end $mm 2 getWord $end $ss 3 getWord $end $zz 4 setVar $end_mm (($hh * 60) + $mm) setVar $end_ss (($end_mm * 60) + $ss) setVar $end_ms (($end_ss * 1000) + $zz) setVar $elapsed ($end_ms - $start_ms) echo ANSI_14 & "**Elapsed: " & $elapsed & "ms**" halt # --------------------------------------------------------- $macro: "m20210*<" Elapsed: 361ms $macro: " m20210* < " Elapsed: 149ms $macro: " m20210*< " Elapsed: 186ms $macro: "ddddd" Elapsed: 77ms In a 6 way setVar $macro "ddddd" Elapsed: 121ms Interesting how display sector takes so much time. So let's try move w/o displays. $macro: " m 3789* < " Elapsed: 165ms Obviously no move delay there What about a longer run? $macro: " m2855* m19838* m21118* m8965* m2862* m29533* m20526* m25307* " Elapsed: 207ms What about a twarp? $macro: " m5* y y p t * * * m 206 * y y " Elapsed: 403ms What about without getting ore? $macro: " m5* y y m 206 * y y " Elapsed: 0ms !!! So I do believe this confirms that there is no move delay in the beta. |
|
| Page 1 of 1 | All times are UTC - 5 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|