1 |
hey,
did
you
guys
know
that
shield
bot
is
also
using
somekind
of
a
"grid"
too.
Its
the
"Shield-Link".
|
1 |
HEY,
did
you
guys
know
that
shield
bot
is
also
using
somekind
of
a
"grid"
too.
Its
the
"Shield-Link".
|
2 |
\n
|
2 |
\n
|
3 |
Each second it loop thru every Shield unit to check which unit is connected and which is not, if this doesn't happen as often then how could it know whether unit walked out of (grid) range or not? -It always do this grid 're-detection' every second to make it work the way it is and I don't think it cause any lag...
|
3 |
Each second it loop thru every Shield unit to check which unit is connected and which is not, if this doesn't happen as often then how could it know whether unit walked out of (grid) range or not? -It always do this grid 're-detection' every second to make it work the way it is and I don't think it cause any lag...
|
4 |
\n
|
4 |
\n
|
5 |
So, I think the grid algorithm (in OD) is not expensive in itself, maybe the fault is in the timing when the grid recalculate... maybe it recalculate in 'burst' instead of 'periodic'? or maybe its not as efficient as Shield-Link? (but I doubt it use different algorithm. I think both use same algorithm)
|
5 |
So, I think the grid algorithm (in OD) is not expensive in itself, maybe the fault is in the timing when the grid recalculate... maybe it recalculate in 'burst' instead of 'periodic'? or maybe its not as efficient as Shield-Link? (but I doubt it use different algorithm. I think both use same algorithm)
|
6 |
\n
|
6 |
\n
|
7 |
Its hard to believe that Shield bots can recalculate grid every second without issues and (we suspect) OD grid cannot?? its just strange...
|
7 |
Its hard to believe that Shield bots can recalculate grid every second without issues and (we suspect) OD grid cannot?? its just strange...
|