Thinking outside the cylinder...
- Thread starter FireSlash
- Start date
-
Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.
Yeah, I thought about that to... That's why I'm asking exactly how the Base thing works. I know that if you use a PHYS_Trailing method they will be in exactly the same place, but I'm not sure about the Base method... If someone who has time could test this out...
[EDIT]
Another thing to keep in mind, in case someone didn't figure it out already, is that if you simply use the SetLocation(...) function every tick to keep the parts in the right place, the collision won't work because the Touch(...) and HitWall(...) functions are only called when the collision cylinder comes in CONTACT with the object, not when it encroaches on it (and almost all of the time, with the SetLocation(...) function, you'll end up encroaching on the wall/actor instead of coming in contact with it).
[EDIT]
Another thing I just thought of... Even if all the parts ARE in the same place, it might still be useful to have several collision cylinders in the same place especially for something like the player. Here is an image to illustrate this.
A script could be used to ignore any collision with the head cylinder in the lower half and the leg cylinder in the upper half... Of course, this wouldn't help much if you want to make nice collision for something more complex such as a vehicle.
Eater.
[EDIT]
Another thing to keep in mind, in case someone didn't figure it out already, is that if you simply use the SetLocation(...) function every tick to keep the parts in the right place, the collision won't work because the Touch(...) and HitWall(...) functions are only called when the collision cylinder comes in CONTACT with the object, not when it encroaches on it (and almost all of the time, with the SetLocation(...) function, you'll end up encroaching on the wall/actor instead of coming in contact with it).
[EDIT]
Another thing I just thought of... Even if all the parts ARE in the same place, it might still be useful to have several collision cylinders in the same place especially for something like the player. Here is an image to illustrate this.
A script could be used to ignore any collision with the head cylinder in the lower half and the leg cylinder in the upper half... Of course, this wouldn't help much if you want to make nice collision for something more complex such as a vehicle.
Eater.
Last edited:
"base" means that it moves with its base.
If the base moves 3 units right, so will it.
Now I stress you WILL need to write custom code to handle multiple parts collision. or else parts might fall off...
If the base moves 3 units right, so will it.
Now I stress you WILL need to write custom code to handle multiple parts collision. or else parts might fall off...
Yes... That too... If they can't rotate with it, it's pretty useless.
And we of course realize the part about having to write code that will link all the collision (so if the arm hits a wall, the whole body should stop)
Eater.
And we of course realize the part about having to write code that will link all the collision (so if the arm hits a wall, the whole body should stop)
Eater.
Yeah, that would be annoying in istagib matches, if your arm got stuck someplace and someone hit it... 
One problem is that if you want it to move with the body, you gotta find out somehow, how the mesh is standing.
Take running for example
The legs move back and forth, and seeing from the side, you could shoot the player between the legs when they're apart, if the cylinder isn't moving like the legs...
But that might be a bit picky...
But the very best should be if then engine could cope with realtime polygon-hits on the mesh...
Although it might prove to be bad, since many ppl might cheat by using a smaller mesh, like the female...
I thought that's how it worked before I knew the topic "collision cylinder"...
One problem is that if you want it to move with the body, you gotta find out somehow, how the mesh is standing.
Take running for example
The legs move back and forth, and seeing from the side, you could shoot the player between the legs when they're apart, if the cylinder isn't moving like the legs...
But that might be a bit picky...
But the very best should be if then engine could cope with realtime polygon-hits on the mesh...
Although it might prove to be bad, since many ppl might cheat by using a smaller mesh, like the female...
I thought that's how it worked before I knew the topic "collision cylinder"...
I think you could also do a lot with Pawn.AdjustHitLocation(), but that too would be very hard to get right.
Well yeah, but with that you wouldn't be able to do fancy collision for something like, say, a long car or plane... I still want to know if the Base thing will adjust the rotation as well as the location, because it may be just what I'm looking for.
Eater.
Eater.