Talk:WaveSerpent/Version History
2.0
I hope it's not too early to say... holy cow, great work! At 400 battles and 0.7% APS above Dookious. Still plenty of battles to go, but you've surely got the #2 spot. Amazing! Congrats! --Voidious 02:06, 29 September 2009 (UTC)
It looks like I've got some competition as an early birthday present! That's a huge jump for a single release! Very impressed =) --Skilgannon 05:03, 29 September 2009 (UTC)
Wow, that must be the greatest robocode comeback of all times, congratulations! :) --ABC 14:22, 29 September 2009 (UTC)
Those are some seriously impressive results there! I'm curious about how you note use of anti aliasing. Do you refer to anti aliasing between segments like I pioneered with SaphireEdge? Or do you mean anti aliasing between bins? Or what? I find it odd how you say that since unless WaveSerpent switched from DC to VCS, I don't see how anti aliasing would be applicable. --Rednaxela 14:52, 29 September 2009 (UTC)
- "Movement now uses anti aliasing" and "Unlike most other surfers, WaveSerpent doesn't use bins" I think this answered your question, unless he changed something. --Nat Pavasant 15:00, 29 September 2009 (UTC)
- Nope, it doesn't answer it at all Nat... You appear to have missed "New main gun with crowd targeting and anti aliasing.". And you also missed my point of asking what anti aliasing could possibly mean in the context of DC (which is what WaveSerpent uses for movement indeed). --Rednaxela 15:12, 29 September 2009 (UTC)
- WaveSerpent doesn't use DC to surf, actually, Hydra does. He definitely mentions segmentation in his movement description - I think it has segmentation but not bins. And fwiw, I did get the impression he switched to VCS in the gun... (WaveSerpent's gun used to be pretty weak.) --Voidious 15:32, 29 September 2009 (UTC)
Very impressive update! Looks like I need to put WaveSerpent back into my test set... --Darkcanuck 15:15, 29 September 2009 (UTC)
- [View source↑]
- [History↑]
You cannot post new threads to this discussion page because it has been protected from new threads, or you do not currently have permission to edit.