I’ve added a new VR test project built in 4.15.1 please review this too and if it’s a different issue, let me know if i need to create a new bugreport for that to keep things seperate?
Here’s Video showing the issue.
And here’s the test-project that reproduces it Project
om/s/f0a1958dpheme0o/VRCollisionBug4.15.zip?dl=0
Hi Jonas,
Please post the VR test project issue as a new report in the Bug section.
I’m investigating the attached components issue now.
Thank you for the test project. I was able to reproduce this behavior so I’ve created JIRA UE-45693. Our developers will be investigating further. Follow that link to monitor the status of the report.
As for a workaround, instead of attaching each actor to the next, you could attach all actors to one parent. Or attach all actors to a single parent using the AttachToActor node. Both seem to fix the overlap issue. Although the warnings still occur.
-TJ
This bug report is kinda weird. StaticMeshComponents attached to each other report overlap just fine using ComponentOverlapComponent when they’re not simulating physics.
Once they simulate physics, they report overlap also but only for the first two attachments.
I’ve uploaded a video to demonstrate the setup here:Video
And provided a template project that reproduces this here: Project
I also get these warnings, which may be related:
Warning Trying to simulate physics on ‘’/Game/UEDPIE_0_Untitled.Untitled:PersistentLevel.Cube4_11.StaticMeshComponent0’’ but no physics body.
Warning Trying to simulate physics on ‘’/Game/UEDPIE_0_Untitled.Untitled:PersistentLevel.Cube3_8.StaticMeshComponent0’’ but no physics body.
Warning Trying to simulate physics on ‘’/Game/UEDPIE_0_Untitled.Untitled:PersistentLevel.Cube2_5.StaticMeshComponent0’’ but no physics body.
Correction: I don’t get this behavior in 4.15.