Aircraft hit spheres... Da Fuq???

[Forboding Angel]

What the hell? Why are the hit spheres for aircraft miniscule? Why do they not follow the same rules as every other unit???

[knorke]

What the hell? Why are forbodings posting habits silly? Why do they not follow the same rules as every other poster???

[Forboding Angel]

This is obvious an issue with the engine. Ergo, engine forum.

[Forboding Angel]

I found a suitable workaround. Was not aware that this tag had been added: useFootPrintCollisionVolume = true, < box instead of sphere, but who cares?

[FLOZi]

Ugly workaround.

I thought engine half-scaling of aircraft hitvols had been removed a while back, guess not?

[smoth]

Iirc it wasn't because assbackwards compatibility for the lazy projects which, if they were not maintained shouldn't even run to begin with

[FLOZi]

Can't find it in the source anywhere

[smoth]

woot someone removed it!?!

[FLOZi]

woot someone removed it!?!

As I said - thought it went a while back, which begs the question; what version is Forbs post form, and or what else is causing it.

[Forboding Angel]

Flozi, this is in spring 96.

I wasn't going to bring it up, but it there was a unitdef tag that countered the silly scaling, however that tag was removed several engine versions ago. I ranted and raved in a thread about it but never got anywhere.

If you look in the evo sauce, there is a workaround using custom colvols that states in comments --because the engine devs are silly. That is a direct result of that tag being removed.

If you want I could find the thread again, but I imagine I was much less than nice in it due to it screwing my aircraft over.

[FLOZi]

I can't be 100% but I thought it finally died, and can;t find it in present source. It's possible one of your gadgets is actually now responsible? I assume the model itself is s3o and radius is all set hunky-dory in Upspring.

edit: Yep, was removed WAY back in 83 (3 years ago!):

http://springrts.com/mediawiki/index.ph ... ldid=26886

https://github.com/spring/spring/commit ... 61959e7f0d

Note the commit message!

[Forboding Angel]

It's possible one of your gadgets is actually now responsible? I assume the model itself is s3o and radius is all set hunky-dory in Upspring.

Grepped gadgets for
canfly (found awards gadget... unrelated)
colvol (found nothing as expected)
collision (found boxxy gadget by knorke that I use for scaling doing custom boxxen)
volume (found lups manager - unrelated)

I'm thinking that a game gadget is not responsible. Perhaps a gadget in spring's basecontent is doing it?

Evo gadgets:
http://goo.gl/DO2Sk6

Edit: doesn't seem like anything in basecontent would do it.

[knorke]

make numbers bigger

[Forboding Angel]

Found it. Ironically, the workaround that I used ages ago to combat the original problem, was in this case causing it.

[FLOZi]

Found it. Ironically, the workaround that I used ages ago to combat the original problem, was in this case causing it.

Welcome to Spring.

[knorke]

That is a fancy way to say "putting collisionVolumeScales = [[35 35 35]] into unitdef file gave me a 35 sized collisionVolume, but 35 was not what I wanted"

[Forboding Angel]

Yes knorke, it was a workaround because the tag that doubled the hitspheres was removed. As a result I added hitspheres manually. Some spring versions later (so possibly as much as a year or so) the stupid code that halved the hitspheres was removed.

Make sense now?