Capsule radius change but shows incorrect

anonymous_user_12c704cc · August 28, 2015, 8:48am

Hi,

It is a bug in Blueprint Viewport.

When editing Capsule Collision Component,

Change “Capsule Radius” to some value larger than “Capsule Half Height”
The wireframe of the capsule starts to seemed strange for the “Capsule Half Height” is changed but Radius is not.
Close the Blueprint Class Window and reopen again, the “Capsule Radius” is correct again.

anonymous_user_bcdd396d · August 28, 2015, 9:18pm

Hi rz1974,

The Capsule Radius is not supposed exceed the value of “Capsule Half Height…” -I don’t know how you have it set so the capsule appears “sideways.” On both my Mac and PC work stations it will not allow me to adjust the values this way by entering them manually or sliding them to adjust.

I’ll look into this further if you can provide me the specs of your work station and some steps to reproduce the issue.

Thanks.

anonymous_user_12c704cc · August 29, 2015, 1:51pm

Hi,
I understood the Capsule Half Height is not supposed to exceed the Radius.
UE4’s default behavior is to set the Half Height along with Radius which greater than it.
But unfortunately, the representation in the view port is not correct. When the Half Height is changed automatically, the radius in the view seemed to be locked.

anonymous_user_bcdd396d · August 31, 2015, 7:49pm

You wrote, “I [undertand] Capsule Half Height is not supposed to exceed the Radius.” It is, in fact, the other way around. The capsule Radius cannot exceed the value of the capsule Half-height. See image below:

Therefore, the radius value input is locked to not allow the user to enter a value that is larger than the value of the capsule half height. This is not a bug. This is intended behavior.

anonymous_user_12c704cc · September 2, 2015, 2:14am

I am sorry, I stated it in the opposite way.
But my question is still there.
Let me restate it again.

I understand “The Capsule Radius is not supposed to exceed the Half Height. When the Radius is greater than half height, the half height will be changed to the same value with Radius.” This is fine and reasonable.

But the problem is when the previous situation happened once, the capsule radius representation will be out of order. Only when the window close and re-open again will get the right result.

Step to reproduce:

Set the radius 50, height 100. (Typical)
Manual type the radius to 200, the Height will forcibly change to 200. That is reasonable. But notice, the representation(in viewport) of radius is now wrong, it is locked to 100.
Change the radius to 50 or 200, it will has no effect in viewport.
Close the window and re-open it, the radius representation is now correct.

anonymous_user_bcdd396d · September 2, 2015, 7:08pm

Hi rz1974,

Thanks for the clarification… Which version of the Editor are you in where this happens? I’ve tested this, following your repro steps in 4.7.6, 4.8.3, and 4.9.0 and these are the results:

Open a Character Blueprint
Set Capsule Half Height: Manually type “100”
Press “Enter”
Set Radius: Manually type “50”
Press “Enter”
Set Radius: Manually type “200”
Press “Enter”

RESULT: Radius field is automatically set to “100” (The largest value available) because the Editor does not allow an entry in the Radius text field to be greater than the Capsule Half Height.

So, in other words, I am not able to reproduce your step “2.”

Let me know if I did not follow your steps accurately or if you are testing in a different version of the engine than those I have listed. Otherwise, this issue seems confined to your machine and is not an actual bug with the engine.

Thanks

anonymous_user_12c704cc · September 3, 2015, 4:12am

Hello ,

I now discover what make you and me different.
I test the Capsule Component of the tutorial Character, that is just what your result you had mention.
But if I add a new Capsule Collision Component, it will do what I have said.
It happens on both 4.8.3 and 4.9

anonymous_user_bcdd396d · September 3, 2015, 4:41pm

Hi rz1974,

I’m glad we finally got to the bottom of why we were getting different results. I have used the information to enter the following bug report: JIRA [UE-20727]. When this issue has been addressed we will add an update to this post.

Thanks for sticking with it until we were able to reproduce the issue here.