So, the bug with Set Start and End on Spline Meshes not setting collision in Construction Scripts WAS fixed, which is great.
But as of 4.10, hitting a Set Start and End on Spline Meshes at RUNTIME will not update the collision. If your spline mesh asset has a simple collision shape (not set to use complex) you can actually see this with the show collision flag enabled in-editor. Though the meshes DO deform properly, the collision shapes are left behind.
HI RhythmScript,
Thank you for the report. This is a known issue that our developers are investigating and we have it logged as JIRA UE-8565.
I’ll update the JIRA to make reflect that other users are reporting this issue.
Cheers,
TJ
I’m having this same problem. Any thoughts perhaps on work-arounds or maybe an estimate for when it will be fixed? Or is there a way for me to actually track JIRA UE-8565?
Cheers,
Seb
Hi Fotosynthesis,
Currently our JIRA system is not publicly view-able, however this is something that we would like to implement later on.
We do not have a timeline of when the issue will be fixed, but our developers are still investigating it.
Unfortunately, a workaround for this has not been found yet. You can find more discussion on this here on the original post.
Thanks a lot for the timely response! I’ll keep an eye on both these threads.
Cheers, Seb
This is currently a pretty substantial blocking issue for us. Any news on if it’s fixed in any upcoming builds?
Hi HighlySpammable,
This is still being investigated by the developers. I added to the JIRA report that other users are being effected and it is a blocker for your team.
Just FYI, the feature request UE-8565 to Support runtime generation of spline mesh collision on platforms that have runtime physx cooking enabled has been implemented in Perforce CL-2937854 by accepting pull request 2064. This change should make it to GitHub the next time the perforce stream it was added in is merged to main, and we plan to include that change in the 4.12 release.
Thanks!
You’re the bomb. Thanks for that!
