Difference between revisions of "Talk:Cannon"

From Robowiki
Jump to navigation Jump to search
(Some suggestions)
(170 codesize now)
Line 8: Line 8:
  
 
With only 142 codesize to spare.... you probably can't fit a movement more advanced than any you see in a NanoBot. My suggestion would be to go with either a simple random movement with musashi trick, or if you feel really daring try a so called 'velocity surfer' movement like a few recent NanoBots have tried. For overall strength of the bot though, I think it'll be kind of critical to slim the gun codesize further so you can fit a movement better than a NanoBot movement. --[[User:Rednaxela|Rednaxela]] 02:34, 1 October 2009 (UTC)
 
With only 142 codesize to spare.... you probably can't fit a movement more advanced than any you see in a NanoBot. My suggestion would be to go with either a simple random movement with musashi trick, or if you feel really daring try a so called 'velocity surfer' movement like a few recent NanoBots have tried. For overall strength of the bot though, I think it'll be kind of critical to slim the gun codesize further so you can fit a movement better than a NanoBot movement. --[[User:Rednaxela|Rednaxela]] 02:34, 1 October 2009 (UTC)
 +
 +
Now have 170 codesize, if that's any better (BTW, are the units of codesize bytes?) --[[User:Starrynte|Starrynte]] 04:14, 1 October 2009 (UTC)

Revision as of 06:14, 1 October 2009

Ah, another Dynamic clustering micro bot! I made one not long ago, it's called MagicD3. Good luck with yours--CrazyBassoonist 16:04, 20 September 2009 (UTC)

  • How did you fit the Waves into the micro? (I couldn't figure out how, so I decided to go with PM for now) --Starrynte 17:05, 20 September 2009 (UTC)
  • Well, you can take a look at the source code if you want, I wouldn't recommend it though; there are other micros that do the same thing with better wave tracking and smaller codesize. But basically what I do is gather data when the enemy fires, then put it that data into an ArrayList(maybe LinkedList, I don't remember). Then I go through the List and check to see if each wave has passed the enemy, and if it has I remove it from the list and put it into a log of firing angles to use. Right now my targeting is segmented on lateral velocity, advancing velocity, a rolling average of the enemies lateral velocity, and distance.
  • RaikoMicro or Aristocles would be good places to look for examples of waves in a MicroBot. --Voidious 17:26, 20 September 2009 (UTC)

Any suggestions for movement (I have around 142 bytes)? --Starrynte 01:57, 1 October 2009 (UTC)

With only 142 codesize to spare.... you probably can't fit a movement more advanced than any you see in a NanoBot. My suggestion would be to go with either a simple random movement with musashi trick, or if you feel really daring try a so called 'velocity surfer' movement like a few recent NanoBots have tried. For overall strength of the bot though, I think it'll be kind of critical to slim the gun codesize further so you can fit a movement better than a NanoBot movement. --Rednaxela 02:34, 1 October 2009 (UTC)

Now have 170 codesize, if that's any better (BTW, are the units of codesize bytes?) --Starrynte 04:14, 1 October 2009 (UTC)