How to enable the collision in pcg forest demo in electric dreams environment

Development Programming & Scripting Blueprint
,
1

Screenshot 2024-07-17 163742
Screenshot 2024-07-17 163742676Ă—590 50.1 KB

1 Like
2

DID you get the solution? i need to know i have the same issue

3

Did you try setting collision on the mesh so that when you use the PCG volume, all the meshes spawned will have a collision?

1 Like
4

how to set the collision?

5

You can set the collision by going into the mesh settings. There is a collision tab dropdown, and you can choose what kind of collision you want.

6

I have the same problem the mesh is set correctly, I even put an individual mesh in the level and the PCG Mesh and the collision was not applied to the PCG instances but was applied to the individual mesh.

7

I’ve encountered the same issue you’re describing: the mesh itself is set up correctly, and when I place it manually in the level, collision works as expected. However, when the same mesh is used through PCG (Procedural Content Generation), the instances don’t have any collision applied.

After some investigation, I found that the issue stems from the fact that PCG uses instanced static meshes, and by default, collision settings can be ignored or overridden during procedural generation. Here’s how to solve it:

  1. Check Collision Settings in the PCG Graph
    In your PCG graph, make sure that the Static Mesh Spawner or Mesh Component Settings (depending on your version) has the correct collision options enabled. Specifically:
  • Set the Collision Enabled to Query and Physics.
  • Ensure Collision Presets are correctly set (e.g., to “BlockAll” or a custom preset you’ve verified works on the static mesh).
  1. Verify the Mesh Asset’s Collision
    Confirm the mesh asset has proper collision set up in the Static Mesh Editor:
  • It should have a collision mesh (either custom or automatically generated).
  • The collision complexity should not be set to “Use Simple As Complex” if your project doesn’t support that for instanced meshes.
  1. Enable Collision on the ISM Component
    If you’re using an Instanced Static Mesh Component or Hierarchical Instanced Static Mesh, collision may be off by default. In the PCG system, open the node where the mesh is spawned and:
  • Make sure the “Enable Collision” flag is ticked.
  • Check if the instancing system allows for per-instance collision—if not, consider switching to a blueprint spawner if you need dynamic or per-instance collision.

  1. Force Rebuild the PCG Graph
    Sometimes, after making changes, the collision doesn’t apply immediately. Rebuild the PCG graph or clear and regenerate the instances to ensure the new settings are applied.

    I hope this resolves the issue you have

2 Likes