Problem with destructible meshes in packaged builds.

Development Rendering
, , , ,
21

Hi guys, it seems I managed to fix this issue on my side - can’t wait till EPIC fix it properly. These changes are experimental/workaround use them at your own risk :slight_smile:

Here is the patch for the engine sources(4.7):

https://drive.google.com/file/d/0B0atPna9kPYkS2FzRnJaV2I2UHM/view?usp=sharing

and for 4.8:

https://drive.google.com/file/d/0B0atPna9kPYkMWVOYUtCRzV5N2M/view?usp=sharing

As you see I reverted some changes from the 4.7 source,

Apply patch for your engine version and observe if this issue still exists. Of course these changes may break something else, so you have test it:)

22

https://github.com/EpicGames/UnrealEngine/commit/6da256d2de16c85173be59feb8fafb1e192c1fb3

This commit looks like a remedy for this issue:)

23

Thanks for posting that .

Once I have a build that I can confirm this fixed on and have closed out the ticket in our JIRA database, I’ll post back here.

24

Probably a noob question but how do you apply these patches?

25

With this:

but first of all try EPIC’s commit:

https://github.com/EpicGames/UnrealEngine/commit/6da256d2de16c85173be59feb8fafb1e192c1fb3

26

The commit leads to a 404 error. :frowning:

27

You have to login on Github and have your account linked to UE account to see the repository, it’s private.

28

Guys,

Just a heads-up that with UE4.9 and the destructible components set to always be skinned on the CPU (I had a variation of the patch where only the destructible meshes would be cpu-skinned), we had a crash of the nvidia driver for versions 355.XX and up. Before that (353.XX and older), we didn’t have any crash. I’m unsure on why this change made the driver crash, but anyhow, reverting that patch to stock-UE4.9 code has fixed the driver crash and the flickering seems to be gone too.