4.17 Instanced static mesh collisions react all at once

every collision of instances react all at once.
If touch one, all the other instances react.

There is no problem in ‘4.16.3’
There is no problem in ‘4.17 PIE’.

‘4.17 Packaged version(Dev,Shipping)’ always has problems.

Hi lizzyvam,

To help me verify what you are seeing, could you provide a screenshot of your blueprint setup?

204166-416.gif

Hi TJ V,
I created a test project.
This is the normal state of the ‘4.16’ ‘packaged’ version.

204167-417.gif

And this is an abnormal state of the ‘4.17’ ‘packaged’ version.
The problem occurs only in the ‘packaged’ version.

Thank you for that. I was able to reproduce this so I’ve created JIRA UE-48361. Our developers will be investigating further. Follow that link to monitor the status.

-TJ

This is not a duplicate… I opened up version 4.18-staging and this bug is yet to be fixed. Stop pushing back a mistake which is so huge it literally breaks many people’s games.

Hi Poke1103, keep in mind 4.18 is not currently including any fixes so it’s mostly 4.17.2, as the branch is in lockdown for now…

Michel, I just wanted to let you know there is another issue which has been around for a while now. It’s a easy fix… Please check this: https://answers.unrealengine.com/questions/574651/foliagecomponent-hitresult-sometimes-returns-inval.html

Basically, when you do a linetrace to a instance, if you have more than int16 number of instances, it will return a negative value (obviously because int16 has a maximum) I have changed it to int32 on my end, but I feel like this could be useful to many other people in the future and its not difficult to change.

this was probably done like this to save on memory, which mean we would have to handle this value as we do for the instance buffer (i.e based on instance count, we use a 16 bits buffer or a 32 bits buffer).

We’ll have to see what would be the best way of handling this.