Distance vs BFT?
← Thread:Talk:SegmentedData/Segments/Distance vs BFT?/reply (2)
I use neither of them, not in my gun nor in my movement. I tested distance in my gun long ago and apparantly it brought not enough to compensate the scattering of data. I have been thinking about BFT lately though, but only because I want to make a bigger distinction between my guns. BFT seems then a better choice than distance, but that is just my gut feeling.
Well, I never tried to drop distance/bft ;) although I don’t know why to include it. Anyway, my guns tend to weight distance relatively low, maybe that segment is really not that important.
Assume we kept our distance really good and it kept 450 ~ 500 most of the time. Then I think whether 450 or 500 makes no big difference, especially against movement that distributes latvel evenly among different time, e.g. random movement. But imagine you got to ~75 distance occasionally, where bot width is not ignorable. If you have distance segment it will automagically take advantage of that, as well as not polluting normal distance. But yes, when distance is concentrated, scattering the data may be more noticeable than the increase in accuracy.
It also depends on how you process each segment. From your words I assume you use multiple separate arrays (segments) and accumulate them with a weight. I use one multidimensional array, which means that I can't give different weight to segments. This works a bit like a tree, going deeper into dimensions when enough data is present. Bringing one more dimension (segment) into such a structure will scatter the data, so I really only add it when it has proven that it helps. As my bot tries to keep its preferred distance, against the majority the distance segment gives no additional info about the movement of the opponent.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:SegmentedData/Segments/Distance vs BFT?/reply (7).