Instanced Static Meshes in Blueprints collision translates incorrectly

anonymous_user_74aa6a23 · April 6, 2015, 9:54pm

If you create a blueprint with an instanced static mesh. Spawn it in the world. And then translate it after it has spawned, it’s collision will not have moved even though the visible mesh will have moved.

I first produced this using the Top Down Sci Fi Asset Set. I can reproduce this in a new project.

This is causing issues for us as our map generation system relies on moving blueprint tiles after it has spawned.

anonymous_user_b9532c9a · April 8, 2015, 3:17pm

HI Deepfried,

Can you show me your blueprint setup?

anonymous_user_74aa6a23 · April 8, 2015, 7:15pm

I used the third person blueprint default. I imported the top down sci fi asset bundle. Deleted all the obstacles and floor and moved the player start to just above the origin:

Created this blueprint:

And then put this in the level blueprint:

And then when I run I get this:

anonymous_user_b9532c9a · April 8, 2015, 9:15pm

Does this only occur with the sci fi assets or is it any asset that you utilize?

anonymous_user_74aa6a23 · April 8, 2015, 10:31pm

I made a new 3rd person with the starter content and used the Shape_Cube. The same effect happened. I also noticed another bug:
If I set the instancedStaticMesh scale under A here:

Then it changes the scale in the blueprint viewport, however when you run the scale has not been changed. You have to set the scale on each individual instance in the array (B).

anonymous_user_b9532c9a · April 9, 2015, 3:45pm

Are your meshes set to static or movable?

anonymous_user_74aa6a23 · April 9, 2015, 4:13pm

As in the picture they are set to movable.

anonymous_user_b9532c9a · April 9, 2015, 7:54pm

Do you see the same results if you set the object with your make transform?

anonymous_user_74aa6a23 · April 9, 2015, 8:41pm

If you mean if I set the initial spawn location, it can spawn anywhere correctly, its any translation after spawning (using set actor location, or set actor transform) that causes it to disconnect display from collision.

Even moving it in editor causes it to move without its collision.

anonymous_user_b9532c9a · April 10, 2015, 5:23pm

Hi Deepfried,

I was able to reproduce this and have entered a bug report, UE-13673 to be assessed by the development staff.

HuntaKiller · May 6, 2015, 9:04am

that’s the second bug that’s a big thorn in my side. Really hope they’re addressed next patch

anonymous_user_94ed2ecc · July 18, 2015, 6:31pm

Wish I had searched for this a bit more before spending 10 hours on this

Going to watch that bug report, it’s make or break for my project.

wilberolive · December 22, 2015, 8:12pm

Did this get fixed yet?

anonymous_user_b9532c9a · December 22, 2015, 8:17pm

Hi ,

Unfortunately this report is still under assessment. I do not have a timeframe of when a fix will be implemented.

HuntaKiller · January 20, 2016, 7:02am

Priority upgrade please

John_Alcatraz · February 22, 2016, 9:19pm

Oh, please fix this! I need this in 4.11.

HuntaKiller · February 22, 2016, 9:38pm

yes, you put the mesh where it needs to be, then delete it and create a new mesh at that location without translating it

John_Alcatraz · February 22, 2016, 9:21pm

Does anyone here have something like a workaround to make the ISMC update the collision correctly?

Jamendxman3 · February 22, 2016, 11:45pm

Looks like there are no real workarounds, as all of them demolish performance. I’d like to bump up the interest in this.

anonymous_user_fb3ab09b · March 30, 2016, 3:37pm

Hi! Do you have any news?