SplineComponent no longer visible in game in 4.3
It looks like your change for SplineComponent from a PrimitiveComponent to a SceneComponent has prevented in-game rendering of the spline from functioning.
In 4.2 I could add a spline component to an Actor and set the appropriate flags in the viewport to show splines, call MarkRenderStateDirty, and have the spline visible in the game (I'm using it for realtime visualization of player movement).
Upgraded to 4.3 yesterday, the ability to set the spline's color is gone, and the spline is no longer visible in game, even just a simple Blueprint Actor with a Spline Component added does not show up. I've :
all to no avail. I'd think that it was something to do with SceneComponent's definition of MarkRenderStateDirty() being different to PrimitiveComponent's one, but that shouldn't have prevented my blueprint-created spline from rendering because its spline data would have been set before anything was rendered.
Setting the spline color should be simple to add back in again, but I can't see the spline to verify that my changes are functional.
asked Jul 28 '14 at 09:07 PM in Bug Reports
We moved the spline rendering code from the component itself to the FSplineComponentVisualizer class. This lets us do all the cool stuff with editing splines in the level. Spline's now are really intended as a shape that drives some other behaviour, whether it is deforming meshes or animation/spawning other objects. It is no intended as a rendering primitive itself. As was mentioned, we do plan to change SplineComponent back to a PrimitiveComponent at some point, but that is to allow derived classes to implement custom rendering code. Sorry that didn't make 4.5! I hope that helps clarify things.
answered Oct 07 '14 at 11:22 AM
Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.
If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.
answered Oct 03 '14 at 03:49 PM
I've reproduced this problem and added it to our internal tracking system (TTP #348722) for further investigation.
answered Oct 06 '14 at 03:19 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here