Line trace stopped working on random objects

I use line traces with Blueprint Interfaces for many of the interaction systems in my project. Everything was working when I saved last night, but after reopening the project today, I noticed that collision stopped working on several objects that were definitely functioning correctly before.

To troubleshoot, I created a brand new Blueprint with a default cube and a simple Blueprint Interface event that prints a message. Nothing happened. I then deleted the cube, replaced it with a default sphere, and suddenly the collision worked as expected.

Next, I placed a default cube and a default sphere directly into the level. The line trace registers hits on the sphere but not on the cube. I tested this in another level and got the same result.

I’ve checked the collision settings, and both objects are configured identically.

This issue is also affecting several custom imported meshes that previously registered hits without any problems.

Has anyone encountered something like this before?

1 Like

Just try a print of the actor right here, to avoid any confusion

1 Like

Managed to fix this myself. It was an engine issue. I reverified my files and the issue is resolved.

1 Like