"Show Collision" Causes Instanced Meshes (foliage) to Vanish

Development World Creation
, , , , ,
1

Hi, has anyone else seen that using the “show collision” command in packaged builds causes instanced mesh geometry, including all foliage, to vanish. This seems to not only effect the visibility, but any collision is also removed from the world. It stays removed even after turning “show collision” off.

Appreciate any help, thanks.

2

Hey rujuro,
I’m having trouble reproducing this issue on my end. Are you able to provide a sample project or instructions to reproduce it in a clean project so I can look in to this?

3

Hi Jon,

Well, it was pretty straightforward in our project, but we are using our own modified version of the engine. As far as I know we haven’t touched anything that should affect collision visualization.

Just to make sure you had the same repro steps, it should go like this:

  1. Add instanced foliage to your map, such as trees or grass using the foliage system (you can also do this with an instanced mesh component and multiple instanced meshes on an actor)
  2. Cook and package a standalone executable via the PackageProject->Windows->Windows(64-bit)
  3. Run the executable and using the console type “show collision”

You should see the foliage disappear and turning off collision debug does not bring it back.
This was in 4.17.1, we do not know if it still occurs in 4.18

4

Hey rujuro,

It’s possible that modifications you’ve made are causing the issue. I am not able to reproduce the issue in 4.17; can you reproduce this in an unmodified version of the engine? Unfortunately we can’t take any further action without repro steps in a vanilla version of UE4.

5

OK, thanks Jon. I’ll try and have a look in a vanilla project to see if I can repro it. Thanks for looking into it for us.

6

Hi rujuro,
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

7

FWIW we updated to 4.18.1 and the problem is no longer happening. So if it was something we did it was unique to 4.17