I used to use this collisionSphereScale = 1, to cause aircraft collision spheres to be the size I set them in upspring (because stupid engine code halves them). Apparently this tag no longer exists... what took it's place? if the answer is nothing, please remove the stupid halving of collision sphere sizes of airplanes from the engine. That's just silly!

If I wanted my planes to have half size collision spheres, I would set them that way in upspring.

It was replaced ages ago when we got tags for cylinders / boxes et al.

You can now use



+1 to removing the half-sizing if it still happens.

it still happens.

http://springrts.com/wiki/Unit_collision_volumes for (almost) all your boxxy need.

I reported it was told tough titties you should go work around it. Feel free to resurect the mantis ticket

It was me that originally implemented the tag Forb is after, and after discussion with the devs of the time (jcnossen or Tobi I think it may have been?) left the aircraft halving alone.

So obviously I have vacillated about its utility myself.

I mean the lol air get 1/2 collision thing

Not a big deal as I do work around it but was mentioning it

Well I'm sitting around yesterday trying to improve the performance of my fighters, and I have 3 fighters chasing around a scout plane, shooting the shit out of it (ballistic projectile, very fast, burn blow) but never quite hitting it. And so in trying to figure out what the hell is going on, I hit alt B and wtf??? I already fixed that!

So I go into the unitdef, yep the tag is still there. Well obviously it isn't working, so then I go to the unitdef shit on github, and search for it, and find dick. So by this point I'm smart enough to know that it was either replaced or removed outright, but I can't find a replacement. So to the forums I run.

This is probably the most epic noobtrap ever.


That explains why my fighters have sucked dick for ages despite my best attempts to fix them.

ok now I'm getting pissed.

collisionVolumeScales = "1 1 1",

Does fuck all. And collisionVolumeScales = "2 2 2", causes this:



So who the fuck do I get the hitspheres that I set in upspring!?!?

You don't.

You use the ones you define

It sounds like smoth is trying to say that you need to use that method to manually set the spheres back to whatever you wanted them to be in the first place...

I DON"T KNOW WHAT THE FUCK I WANT THEM TO BE INGAME! I WANT THEM TO BE THE SAME AS I FUCKING SET IN UPSPRING BUT THOSE VALUES DON"T MATCH UP EITHER!!!

I take issue
with the idiocy
of scaling down all aircraft arbitrarily
and then NOT GIVING AN EASY WAY TO CHANGE IT BACK!?!?!?!
No!
Instead
I have to go through and get the fucking volume of every fucking aircraft
just because some dev thought he was clever
It's been a known problem for upwards of 4 years
and regardless of any efforts to get it changed
we get ignored
this is why there is fucking tension betwen content devs and engine devs!
[14:54:39] <[Evo]Forboding_Angel> *cleansing sigh*

And then these thin skinned idiots wonder why I come on the forums and start ripping the engine devs a new asshole after I've just spent 8 hours cleaning a mess that they caused!

YEAH, YOU BET I"M FUCKING PISSED!

If you don't like me being upset about it, tough shit, cry me a fucking river. I have a very good reason to be extremely fucking pissed because I just fucked away an entire day on this stupid bullshit!

It's wouldn't be AS bad if the volumes matched the radius in upspring, but they're nowhere close! Jesus fucking christ...

Ok... Since the devs are allergic to fixing gaping bugs because they might affect BA... I propose a compromise.

Add collisionSphereScale = 1, back in, so that we can add it to unitdefs post (along with all the other engine bugs that have to get fixed by lua) and be done with it.

Fair enough?

That way, people like me don't have to spend days or weeks trying to deal with stupid kludges embedded into the engine.

you are not helping by calling the engine devs idiots

They are ~50% the radius.
It is probally some stupid hack that was seemed nessecary 9001 years ago. Like the waterline+5 thing that caused subs to be above water some time ago.
Yeah so basically it sucks and was a stupid idea to solve it like that but now what. Probally was done because nobody else would do it in a better way.

and I want textures to look ingame like in Upspring and also want a threesome with Natalie Portmann and Dirk Bach.
I can make neither happen/fix so I just live with it.
ie "flip uv map" or set doubled radius in Upspring.
Both sucks a bit but is not that hard.

or try boxxy, maybe that works (did not test on aircraft)
viewtopic.php?f=14&t=24882

Seriously, ask yourselves...

Why is it necessary for me to have to go into epic raeg mode (oh and believe me, this time I am livid), in order for this sort of shit to receive any attention?

Flozi is a perfect example of "Asking Nicely" getting nowhere.

We all have known from the start that it's a big problem, but with the previous tag it was an easy fix so no one made too many bones about it (fixed by flozi), but then the fix was removed and replaced with a useful feature for sizing hitspheres and boxes and such, but it actually makes the problem worse, because no longer is there a quick and easy to way to fix it.

So why are the engine devs blatantly ignoring problems like this?

@knorke, I grabbed boxxy, but while it will be useful in the future, I don't want to have to resort to putting boxes on aircraft (thanks for the tip tho).

it isn't necessary.

boxxy is named boxxy but also works with cylinders and spheres

just to make this clear..the solution is imo not to bring back
collisionSphereScale = 1
that is just a hack to get around another hack.
Aircraft should just use 100% volumes, like any other unit. Yes, it will break existing mods but this would be something where it makes sense imo and fixing all airplane models should not take too long. And all future mods with airplanes will be thankfull.

What mods? BA?

My heart bleeds.

no, all mods with aircraft.
which is like, all.
But as i said, imo worth it because lots of other things will probally break anyway etc.

How would it break anything? All it does is change the hitsphere size to the shape that the creator intended it to be in the first place. If anything, it will fix shit.



I completely disagree. Because of my tenacity, no other newbie moddev will read this thread and have any illusions about exactly what is happening, because according to the first 3 replies, you, knorke and flozi were all completely wrong about how collisionVolumeScales = "x y z", works towards fixing half scaled hitspheres. I just saved newbie moddevs a lot of frustration and hot blooded man tears.