I avoid the AMs as well, but it seems to happen with any attachment where I'm using a Site Operation (Local Offset) or, as you said, an explicit rotation. Any normal attachment, e.g. SOpAttachWeaponLeft, sticks tight to the host.
Your weapon obviously has a damage effect, so go to the "Search" field under that damage effect and add a value at the top. From there, just adjust the fields to how big you want the cleave area and what fraction of damage it does.
or...
Instead of damage, make a "Search Area" effect with fields similar to above. Then put your unadjusted damage effect into the value field of your search effect. Put this search effect where the damage effect was on your weapon.
Has anyone noticed that anytime you attach an actor to another actor and offset it with a SOp, the attachment bounces a little as though it's loosely attached to the host? I have tried numerous different model types, actor types, "is local" and everything else I could think of. If anyone has found this annoying little glitch and found a work-around, please let me know.
0
I avoid the AMs as well, but it seems to happen with any attachment where I'm using a Site Operation (Local Offset) or, as you said, an explicit rotation. Any normal attachment, e.g. SOpAttachWeaponLeft, sticks tight to the host.
0
You can do it one of two ways:
Your weapon obviously has a damage effect, so go to the "Search" field under that damage effect and add a value at the top. From there, just adjust the fields to how big you want the cleave area and what fraction of damage it does.
or...
Instead of damage, make a "Search Area" effect with fields similar to above. Then put your unadjusted damage effect into the value field of your search effect. Put this search effect where the damage effect was on your weapon.
0
Has anyone noticed that anytime you attach an actor to another actor and offset it with a SOp, the attachment bounces a little as though it's loosely attached to the host? I have tried numerous different model types, actor types, "is local" and everything else I could think of. If anyone has found this annoying little glitch and found a work-around, please let me know.