Difference between revisions of "Talk:Watermelon/Development"
Jump to navigation
Jump to search
(→WaveSurfing adaptation: new section) |
J Litewski (talk | contribs) (→WaveSurfing adaptation: So it's not only me...) |
||
| Line 6: | Line 6: | ||
When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 00:54, 14 June 2009 (UTC) | When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 00:54, 14 June 2009 (UTC) | ||
| + | :I have kinda the same problem. [[GravityWave]] is segmented on distance currently, since adding even one more segment drops his score by 50%. I just thought it was because my computer is old and my code really basic. I know this didn't help you much, but still :P --[[User:J Litewski|Jacob Litewski]] 01:01, 14 June 2009 (UTC) | ||
Revision as of 02:01, 14 June 2009
Hooray!
Glad to see you consider your bot worthy of version tracking now! It's fun to watch people's progress. --Simonton 16:11, 25 September 2008 (UTC)
WaveSurfing adaptation
When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- Synapse 00:54, 14 June 2009 (UTC)
- I have kinda the same problem. GravityWave is segmented on distance currently, since adding even one more segment drops his score by 50%. I just thought it was because my computer is old and my code really basic. I know this didn't help you much, but still :P --Jacob Litewski 01:01, 14 June 2009 (UTC)
