x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Did collision handling change between 4.7 and 4.10?

I'm having an issue where a 4.7BP is behaving differently than a 4.10BP. I'm using a mesh to determine if a player is inside an arbitrary volume. (It's a complex shape so actual volumes don't work for this case). The blueprint would essentially use ActorBeginOverlap and ActorEndOverlap to tell the game if a player was inside of it or not.

This worked great as of 4.7 but as of 4.10 completely entering the volume such that the player isn't touching outer edges of the volume I get an "ActorEndOverlap" message even though they are still overlapping. I have attached a diagram to show the issue more clearly.

On the left side of the line we have the case where the player is touching the outside edge of the mesh volume.

On the right side the player is "inside" the volume from the top view but should still be considered overlapping from the front view. In 7.10 as soon as the player moves to a position not on the outer edge of the volume as seen from the top I get an undesired ActorEndOverlap message.

Any thoughts as to what might have changed?

alt text

Regards,

ook

Product Version: UE 4.10
Tags:
overlap.jpg (89.2 kB)
more ▼

asked Jan 13 '16 at 01:11 AM in Bug Reports

avatar image

00k_
219 11 21 31

avatar image 00k_ Jan 13 '16 at 01:19 AM

I noticed through further debugging of the blueprint that once the player is "inside" the outer boundary of the mesh that it generates a constant stream of Begin and End overlap events simultaneously.

avatar image 00k_ Jan 17 '16 at 03:45 AM

Any help out there? Is this normal to be seeing all these Begin and End overlap events when the player is overlapping a static mesh?

Regards,

ook

avatar image Matthew J Jan 18 '16 at 09:50 PM

Hello ook,

Does this only occur with your specific static mesh or any static mesh that you use? I would be interested to see the collision settings / blueprints for the involved actors as well. Would it be possible to get a copy of the project or some screenshots to see this information?

avatar image 00k_ Jan 24 '16 at 05:47 PM

So I did some more testing and was able to put together a test case pretty quickly in the example map. Basically if you add a BP to: StaticMesh'/Game/Shapes/Shape_Cube.Shape_Cube'

Then set the collision settings I attached.

alt text

Then make it handle input from Event ActorBeginOverlap and Event ActorEndOverlap.

alt text

(scale it and position it so a player can fit/walk completely inside it)

alt text

It works as expected. If you watch the BP while walking over it you will see a single event for begin and when you walk out of it you will see a single event for end.

If you take that same actor and swap the mesh out for: StaticMesh'/Game/Architecture/Wall_Door_400x300.Wall_Door_400x300'

(Rotate it so it's laying on it's side and scale and position it so a player can fit/walk completely inside it)

alt text

Then do the same test and you will see that when you move into the mesh Begin and End will fire a whole bunch of times rapidly and then stop. Another odd aspect of this is that you very carefully approach the edge of the mesh in this case and just barely touch it you will get a single Begin event.

alt text (these all happen basically at the moment the player enters the shape)

beginend.jpg (31.4 kB)
cube.jpg (35.8 kB)
arch.jpg (36.5 kB)
beginendtext.jpg (12.5 kB)
(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Thank you for the reproduction steps ook. It seems that this issue is related to using the "Use Complex Collision As Simple" setting for the Collision Complexity inside of the Static Mesh editor. The Wall_Door_400x300 uses this by default while the cube uses the "Default" setting. I've placed a bug in for the issue under the number UE-25923. In the meantime, as a workaround, I'd suggest using Default and creating the collision via "Auto Convex Collision" in the Static Mesh Editor.

Have a nice day!

more ▼

answered Jan 25 '16 at 03:11 PM

avatar image 00k_ Jan 25 '16 at 05:06 PM

Yeah I assumed this was the issue after finding the repro. Unfortunately the mesh I am using is complex and I'll need to break it up into concave chunks to make this work but it should be fixable.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question