BossBrain Radius

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: BossBrain Radius

Re: BossBrain Radius

by Graf Zahl » Mon May 09, 2022 11:52 am

Only if you create a setup where precise distance matters. For boss brains that is highly unlikely.

Re: BossBrain Radius

by ChopBlock223 » Mon May 09, 2022 7:10 am

Graf Zahl wrote:I thoght we had all of these fixed. This one must have slipped through...
So would there be any notable consequences for how splash damage interacts with BossBrain if it was fixed? Part of the calculation is the receiving targets own Radius, I think.

Re: BossBrain Radius

by Graf Zahl » Mon May 09, 2022 12:14 am

I thoght we had all of these fixed. This one must have slipped through...

BossBrain Radius

by ChopBlock223 » Sun May 08, 2022 6:16 pm

Let's see if I got this right, this is me interpreting what I've seen here.

The BossBrain actor has no defined Radius value, making it default to a Radius value of 20, when the value should actually be 16.
This makes no appreciable difference in the vast majority of use cases, but it did cause problems in a level where the BossBrain was supposed to move through a 32 unit wide conveyor path, causing it to get stuck and subsequently get telefragged by the decoration coming in behind it.
In DSDA this wasn't happening.

It occurs to me that this could change how splash damage interacts with the BossBrain actor though, and I don't have a particularly good solution for that.
As said, this is largely a very uncommon issue due to very few levels depending on the Radius of the BossBrain to function (in fact this may be the first example ever), and including a basic Decorate patch would be a trivial fix, but I figure it should be reported at any rate.

Top