Increasing Hit Box for Giant Sized Units?

[DEE-BOO]

In this picture, this Giant Grunt only gets hit by 4 bullets, when he should get hit by much more, the bullets fly through his feet.

These bullets are triggered: via
Pick 1 Random Unit In 50 Range of Bullet, Add Picked Unit to BulletTargets
Matching, Matching Unit is Alive, etc.
Set 1 Random in Bullet Targets = BulletMainTarget
Cause OwnerOfBullet to Damage BulletMainTarget

Is there a way to increase the grunt's 'hitbox' so it can be detected by a bullet much easier?

 

[Dr Super Good]

You tried increasing the selection circle and collision radius of the grunt?

 

[DEE-BOO]

Yeah, it's Collision size is at 200, But it's selection circle is at negative to hide the HP Bar, do you think that has something to do with it? EDIT: just did a quick test, selection circle doesn't matter if it's at -1 or 4, he has the same hit box. I've even went into Game Play Constants and changed the Collision - Maximun Radius to the Max.

 

[Dr Super Good]

Based on this one must assume the area search only applies to the unit origin. Hence it will only see the unit if the origin is inside the searched area. This means it is possible for the unit collision to fill the entire search area but still not be returned as a search result because its origin is not in the search area.

My only suggestion would be to expand the search area. You could store unit collision radius inside a hashtable and use that to adjust search distance. Another approach would be to give large units special collision handling where they search for the missiles in a collision corrected area rather than the missiles search for them since the missiles are much smaller than they are.

Mechanically this is probably down to how the search is performed. I would imagine a data structure like quad-tree is used to map units for spatial queries. Each unit is represented as his origin point in this structure so all searches will only return a unit if his origin point is in the query area. The structure has no idea about the area the unit takes up, only where its origin is and will only return it if the origin is in the query space.

 

[DEE-BOO]

I kinda get what you mean, I think I was going to resort to that if nobody here could help me find an easier alternative, thanks for your input. +rep

 

[Zwiebelchen]

If you use "pick every unit within x radius" to apply your collision, you need to add the collision size of your unit into the calculation, as picking units only considers the origin of said unit.

So basicly, check 50+collisionsize[unit]. Unfortunately, you can not get a unit's collision size by trigger... you need to basicly define them manually for each unit type. DSG's hashtable approach is the clever solution here.