GravityWave/Tests/Archive June182009 - Revision history

J Litewski: moved GravityWave/Tests to GravityWave/Tests/Archive June182009: Restarted code to work out bugs before adding new features.

2009-06-18T21:30:33Z

moved GravityWave/Tests to GravityWave/Tests/Archive June182009: Restarted code to work out bugs before adding new features.

J Litewski: No Losses! (Major Bug killed)

2009-06-16T18:17:41Z

No Losses! (Major Bug killed)

J Litewski: Gha

2009-06-16T04:47:15Z

Gha

J Litewski: Modified last installment

2009-06-15T03:35:37Z

Modified last installment

J Litewski: Yay for bugs!

2009-06-15T00:22:24Z

Yay for bugs!

J Litewski: added navbox

2009-06-14T19:26:43Z

added navbox

J Litewski: stupid return :/

2009-06-14T01:31:56Z

stupid return :/

J Litewski: Update :)

2009-06-14T01:31:19Z

Update :)

J Litewski: Added new entry

2009-06-12T00:32:36Z

Added new entry

J Litewski: Saving/Loading Segmented Data Test against DustBunny 3.8

2009-06-11T22:02:26Z

Saving/Loading Segmented Data Test against DustBunny 3.8

@@ Line 119: / Line 119: @@
 Well, this is a test on my pre-buffered array. DustBunny 3.8 still kills me, and there is a very slight improvement against DustBunny 3.5.
 ----
 ----

@@ Line 105: / Line 105: @@
 </pre>
 This concludes what people were talking about, My movement is buggy. Gha. Back to basics... I'm going to work on tightening up everything. There has to be a bug in the EnemyWave Functions or the Array. Those are going to be the two things I start on first.
 ----

@@ Line 74: / Line 74: @@
 I've been slowly tuning and polishing GravityWave over the last couple of days, testing and retesting ideas, segments, basically everything to try and improve the movement. Besides some very minor improvements to the prediction and danger functions, and some slight tweaks to the EnemyWave function, nothing really new to report. I did create a Scan class which is loosely biased off of Voidious' BotScan class. The Scan class stores a complete scan of the current tick, including some more advanced functions and a better workaround for detecting false waves. Once I work out some of the bugs and speed up some things, hopefully I can finally get 85+% on [[DustBunny|DustBunny 3.8]].
 ----
-:22, 15 June 2009 (UTC)
+:22, 15 June 2009 (UTC) (Modified: 03:35, 15 June 2009 (UTC))
 Unmodified BasicSurfer vs Stationary DustBunny 3.8
 <pre>
 st	mld.DustBunny 3.8	44964 (81%)	9900	1980	30920	2164	0	0	198	302	0
 nd	wiki.BasicSurfer	10621 (19%)	7200	3020	0	0	396	5	302	198	0
-</pre><br>
+</pre>
 UnSegmented GravityWave alpha2 vs Stationary DustBunny 3.8
 <pre>
 st	mld.DustBunny 3.8	45758 (80%)	9800	1960	32013	1985	0	0	196	304	0
 nd	hackhalotwo.GravityWave	11296 (20%)	8100	3040	0	0	156	0	304	196	0
-</pre><br>
+</pre>
 Unbuffered Segmented GravityWave alpha2 vs Stationary DustBunny 3.8
 <pre>
 st	mld.DustBunny 3.8	26775 (64%)	4850	970	19980	975	0	0	97	403	0
-nd	hackhalotwo.GravityWave	14804 (36%)	10650	4030	0	0	122	1	403	97	0 </pre><br>
+nd	hackhalotwo.GravityWave	14804 (36%)	10650	4030	0	0	122	1	403	97	0 </pre>
 Buffered Segmented GravityWave alpha2 vs Stationary DustBunny 3.8
 <pre>
 st	mld.DustBunny 3.8	31922 (70%)	6550	1310	22699	1363	0	0	131	369	0
 nd	hackhalotwo.GravityWave	13507 (30%)	9550	3690	0	0	264	3	369	131	0
-</pre><br>
+</pre>
 This concludes what people were talking about, My movement is buggy. Gha. Back to basics... I'm going to work on tightening up everything. There has to be a bug in the EnemyWave Functions or the Array. Those are going to be the two things I start on first.
 ----

@@ Line 73: / Line 73: @@
 :31, 14 June 2009 (UTC)<br>
 I've been slowly tuning and polishing GravityWave over the last couple of days, testing and retesting ideas, segments, basically everything to try and improve the movement. Besides some very minor improvements to the prediction and danger functions, and some slight tweaks to the EnemyWave function, nothing really new to report. I did create a Scan class which is loosely biased off of Voidious' BotScan class. The Scan class stores a complete scan of the current tick, including some more advanced functions and a better workaround for detecting false waves. Once I work out some of the bugs and speed up some things, hopefully I can finally get 85+% on [[DustBunny|DustBunny 3.8]].
 ----

← Older revision		Revision as of 19:26, 14 June 2009
Line 1:		Line 1:
		+	{{Navbox small
		+	\| title = GravityWave pages
		+	\| parent = GravityWave
		+	\| page1 = Versions
		+	\| page2 = Code
		+	\| page3 = Tests
		+	}}
		+	----
	05:00, 7 June 2009 (UTC)		05:00, 7 June 2009 (UTC)
	<pre>		<pre>

← Older revision	Revision as of 21:30, 18 June 2009
(No difference)

@@ Line 62: / Line 62: @@
 </pre>
 I added in a setMaxVelocity() for turning. Other than that and some slight tweaks to the segmentated Array to speed up the execution. After thinking about it, and while looking at the debug data, I noticed that there was a major bug in the distance Segment. The Segment is updated ''every turn''. It should only be the distance when the bullet was fired, not the current distance. So I'm going to work on hacking the enemyWave class to take the distance Segment, then updating and re-polishing things.
 ----

@@ Line 55: / Line 55: @@
 </pre>
 This is a test on the save/load functions and on the 2D Segmentation Array. Both are a success. I'm going to need to polish up the way it picks Danger, since that's not using the 2D Array to it's fullest.
 ----

@@ Line 42: / Line 42: @@
 </pre>
 This is the test for my 2D Segmented BIN Array. It shows a slight improvement all around. I ''know'' it will do better if I went in and polished up the functions for the segmentation. I should test this against DustBunny 3.8...
 ----