|
* I think a lot of my movement pains are self-inflicted, because of me choosing the GotoSurfing? approach =). The hardest part was getting the second-wave surfing down, and even now I think there are a few bugs in that. I know one of my speed optimizations occasionally malfunctions, especially when I'm WallSmoothing. But my movement would be at least 3x as slow (which would mean skipping turns) if I fixed it 'properly', so now I need a fancy detection algorithm to check when it's not returning the correct results...you get the idea =). I also need a major restructure....there hasn't been any refactoring in the movement since 0.3.0 =). Let me just add another parameter here, that can't hurt....and what about some different functionality when I call it with a null value...that sounds cool ;-) -- Skilgannon |
![[Home]](/images/RoboWiki.png)