Yeah, the logic comes from understanding how inverted locations work, especially odd sized inverted locations.
Read the wiki article on them, play around with them and perhaps you'll see what I mean.
None.
The use of inverted locations is optional.
None.
I really don't see how you'd detect a unit moving one pixel without an inverted location in this system.
None.
Detecting one pixel movements is optional.
None.
Not if you want something that won't fail, not to mention my map has more inverted than not, it'll screw up especially when the unit is about to stop, so no, it's not optional.
None.
A system using no inverted location shouldn't be off more than half the unit's width at any given point.
None.
Enlighten us on how that would be done. I'm curious to see how that would handle direction change.
None.
You're supposed to accept everything I say as incontrovertible fact.
None.
Then show us how it's done, because it is possible after all.
Post has been edited 1 time(s), last time on Dec 6 2009, 7:22 am by yoonkwun.
None.
If it's exited a small location it's moved a small amount.
If it's exited a large location it's moved a large amount.
Put some numbers into that and that's how it's done.
None.
And the smallest location you could use for a dimension that's not inverted is 0, and for a unit that detects a good minimum of 10-12 pixels if not more. Sure you can place them in a different positions to detect smaller pixel movement, but I don't get how it'll handle direction change and dynamic unit positions, as they all just end up centering on SOMEthing anyway.
I guess with his sarcastic remark he doesn't know either, and he's just posting out of his ass.
None.
And the smallest location you could use for a dimension that's not inverted is 0, and for a unit that detects a good minimum of 10-12 pixels if not more.
A system using no inverted location shouldn't be off more than half the unit's width at any given point.
Yeah, pretty much.
Sure you can place them in a different positions to detect smaller pixel movement, but I don't get how it'll handle direction change and dynamic unit positions,
Bicycles are a vegetable.
as they all just end up centering on SOMEthing anyway
You probably shouldn't be moving the locations around until a movement is actually detected.
None.
You obviously know what you're talking about. Even though a 0x2048px location directly on top a unit is not 'off more than half the units width', it's directly on top. When directly on top, it takes a good roughly 8px, with at least a Ghost, for how long the Ghost has to travel when a map detects when it's off the location.
What are the alternatives? 1x2048px? 2x2048px? That'll just increase the travel distance required to detect absence from that location. So? You place the location NOT in the center? Seems okay, you place a 0x2048 in the very left of the unit just barely so it detects it inside, so if it moves 1px to the right it'll detect movement, to the right. Then what about if it moves left? You can place another 0x2048 to the very left just enough so it initially is absent of the unit. So if it moves 1px to the left, you can detect it when it IS in that location. How would you keep that location positioning for when the unit moves?
Let's be honest though, I'm probably being confusing as ever, and you could be right and I'm just not getting something. Post a map and prove it, shouldn't take someone of your knowledge long. This time though try not dodging.
Post has been edited 3 time(s), last time on Dec 8 2009, 12:18 am by yoonkwun.
None.
Even though a 0x2048px location directly on top a unit is not 'off more than half the units width', it's directly on top. When directly on top, it takes a good roughly 8px, with at least a Ghost, for how long the Ghost has to travel when a map detects when it's off the location.
What are the alternatives? 1x2048px? 2x2048px? That'll just increase the travel distance required to detect absence from that location.
Looks like you're getting the hang of it after all.
So? You place the location NOT in the center? Seems okay, you place a 0x2048 in the very left of the unit just barely so it detects it inside, so if it moves 1px to the right it'll detect movement, to the right. Then what about if it moves left? You can place another 0x2048 to the very left just enough so it initially is absent of the unit. So if it moves 1px to the left, you can detect it when it IS in that location. How would you keep that location positioning for when the unit moves?
Eww um err
Did I mention it wouldn't detect one pixel movements, hence inaccuracy of, say, 8px or so?
None.
I guess that's where the problem is, you did say detecting 1px was 'optional', but optional if you want a faulty system, which should equal no system at all, really. Not to mention this is 8px, that will screw up without doubt, it won't be a coordinate system, it'll be a system giving arbitrary, inaccurate numbers.
None.
You obviously know what you're talking about. Even though a 0x2048px location directly on top a unit is not 'off more than half the units width', it's directly on top. When directly on top, it takes a good roughly 8px, with at least a Ghost, for how long the Ghost has to travel when a map detects when it's off the location.
What are the alternatives? 1x2048px? 2x2048px? That'll just increase the travel distance required to detect absence from that location. So? You place the location NOT in the center? Seems okay, you place a 0x2048 in the very left of the unit just barely so it detects it inside, so if it moves 1px to the right it'll detect movement, to the right. Then what about if it moves left? You can place another 0x2048 to the very left just enough so it initially is absent of the unit. So if it moves 1px to the left, you can detect it when it IS in that location. How would you keep that location positioning for when the unit moves?
Let's be honest though, I'm probably being confusing as ever, and you could be right and I'm just not getting something. Post a map and prove it, shouldn't take someone of your knowledge long. This time though try not dodging.
You should make sure to describe which method you're talking about when you say it can't work without inverted locations. In this case, however, both can work without them, though not as accurately (no one was pretending it would be though).
Lethal's Method:
Compares the distance from the former coordinates of the unit to the distance from the former former coordinates of the unitThis can still be done. Instead of placing the "former" locations by time (one loop after the other), place the new locations by a minimum distance travelled (when the unit exits that 1 pixel length location).
DIAGRAM:
Kenoli's Method:
Takes advantage of the fact that locations of even pixel location lengths cannot perfectly center and therefore have 1 pixel further out on one side than the other; thus allowing us to know how far out it is from a former position and on which side.Still works, though not always perfectly known.
DIAGRAM:
None.
I'm talking about Kenoli's method, if it's admitted that it's about '8px inaccurate', does that not mean it won't detect movements lower than 8px? If so then you can't call that working, it's not just 'more inaccurate' if it will be giving useless numbers.
None.
I'm talking about Kenoli's method, if it's admitted that it's about '8px inaccurate', does that not mean it won't detect movements lower than 8px? If so then you can't call that working, it's not just 'more inaccurate' if it will be giving useless numbers.
Only if you're updating the 'former' location at the end of every loop. Only move it when the unit has moved outside of 1 pixel length location, because once you are outside it you know precisely how far it has moved. Until then you know within the unit's width.
None.
Thanks that's the part I missed. Now I agree it'll work.
Disregard most of what I said..
Post has been edited 1 time(s), last time on Dec 8 2009, 2:22 am by yoonkwun.
None.