[General] Tiny rects

[gusanomental]

I need kind of a precise way to detect whenever a unit enters a really small area. Is it possible to set a rect to lower than 32x32? If not, is there any workaround available?

Thank you in advance.

 

[Dr Super Good]

I need kind of a precise way to detect whenever a unit enters a really small area. Is it possible to set a rect to lower than 32x32?

Yes it is possible. I do not think there is a limit as to how small a rect can be.

However be aware the unit enters/exits region event uses a region and not a rect. Regions work in map cells so the smallest region one can represent is 32x32 units.

 

[nedio95]

Yes it is possible. I do not think there is a limit as to how small a rect can be.

However be aware the unit enters/exits region event uses a region and not a rect. Regions work in map cells so the smallest region one can represent is 32x32 units.

That was a pretty roundabout way to say "No. Watch the terms you are using..." :|

I guess you could have a region around the area you need and when a unit enters it start your own box collision checking if the coordinates of the unit correspond with the coordinates of the tiny area.

@Dr Super Good Would that work, or ?


-Ned

 

[Dr Super Good]

@Dr Super Good Would that work, or ?

That would work, however there might be scaling issues if you have dozens or thousands of such regions with units in them.

 

[gusanomental]

So rects can effectively have any size but now I can't find the way to prevent the leak when setting the point in 'Unit enters rect' event. Am I doing something wrong? For now, I'm using 'A unit comes within X of' along with invi dummies and I haven't found any bug... yet.

Thanks for the help.

 

[Chaosy]

More importantly, why do you need rects?

They are mostly useless as there are better options available.

 

[gusanomental]

Well, my unit is fixed to vertical/horizontal rails and there's a region in every intersection where it can make 90-degree turns after stepping over. 32x32 is not small enough to make the rail change smooth.

 

[Kaijyuu]

Stick a dummy unit there and use Unit Within Range events.

 

[Dr Super Good]

So rects can effectively have any size but now I can't find the way to prevent the leak when setting the point in 'Unit enters rect' event. Am I doing something wrong?

Sounds like it since the even does not even take a location object to leak...

Well, my unit is fixed to vertical/horizontal rails and there's a region in every intersection where it can make 90-degree turns after stepping over. 32x32 is not small enough to make the rail change smooth.

This is usually done by state machine of sorts. When entering a corner you use different movement logic than when going along straights, the movement is in a different state then.

 

[Pyrogasm]

The solution without region enters or 'in range' events is to use a low-timeout (<0.5s) repeating timer that compare's the unit's coordinates to the min and max x/y coordinates of each rect. Store all the rest edges in arrays at map init and it won't be a memory hog, just real number comparison. You can turn the timer off when no units are moving.

//pseudocode, you can do this in GUI
loop through all such units you want to check, using index1 as counter
    Set U = units[index1]
    Set UX = X coordinate of U
    Set UY = Y coordinate of U

    loop though rects using index2 as counter
        Set mx = rectsmx[index2] //min x
        Set Mx = rectsMx[index2] //max x
        Set my = rectsmy[index2] //min y
        Set My = rectsMy[index2] //max y
        //There are functions to get these min and Max coords in jass, may have to look to locactions to do it in GUI

        if (UX <= Mx) and (UX >= mx) and (UY <= My) and (UY >= my) then
            //The index1'th unit is in the index2'th rect
            //Do whatever here
        endif
    endloop
endloop