Tutorial: Your First 60 Minutes with Mass

Hey everyone! I am looking into this issue. It seems to be caused by a change made so that Mass processors could tick inside the editor for editor utilities. We are working on a proper fix, but a workaround in the meantime is possible.

  1. Open ProjectSettings->Mass
  2. Expand the Mass Entity->Processor CDOs tabs
  3. Expand DebugVisLocationProcessor (Index 0 by default)
  4. Open the Execution Flags dropdown and check the option for Editor

Here is a screenshot of the change

Other processors are affected by this issue as well, but this is the change needed for the debug visualization to properly place the cones for the entities. The entities themselves were at the correct spawn locations as you can see if you open the GameplayDebugger and Pick an Entity. It will show a debug wireshape where the entity is, but since the DebugVisLocationProcessor is not running, the mesh to represent the entity is not moved.

I hope this helps. I will add a reply when a proper fix is added to the engine to address this bug.

4 Likes