Scene Capture Component 2D Generates Map Check Warnings

Development Programming & Scripting
, ,
1

Scene Capture Component 2D generates a map check warning: Static Mesh Actor has NULL StaticMesh property

2

Steps to Reproduce
Add a Scene Capture Component 2D to an actor in a level. Run a Map Check. The Actor will report a warning: Static Mesh Actor has NULL StaticMesh property.

3

Hi,

That error comes from validating a StaticMeshComponent and should not be related to a SceneCaptureComponent2D. Did you validate that the StaticMeshComponent of the actor in the message is properly set? The StaticMesh property should be referencing a StaticMesh.

Does the scene capture need to be attached to a specific actor in the scene or you are simply looking to place it? A Scene Capture 2D actor might be what you are looking for if you are only looking to place it.

If this doesn’t help, please share a level that demonstrate the problem or precise reproduction steps.

Regards,

Martin

4

Hi [mention removed]​ , thank you for replying. This is a strange one! I have put together a test case to reproduce this map check warning, and the only actor I have added to the base map has only a Scene Capture Component 2D. There are no static mesh components at all, which is why this is especially weird to me. I thought I had attached a project to this post that repros the warning, but I’m not seeing it anywhere now. I will attach it again. If that fails, you can easily reproduce this in 5.6 by adding an actor with a scene capture component and running a map check.

5

Hi Joseph,

I was able to reproduce the problem thank to the sample. It appears to be specifically related to Blueprint Actor instantiation. The BP instance is missing the proxy camera mesh that should be visible in the viewport and this triggers the error. That code is editor only an will not affect the package but it can be annoying to not see the mesh. You can use the SceneCapture2D actor from the `Quick add` dropdown which doesn’t have the instantiation problem while we work on a fix.

Regards,

Martin

6

Hi Joseph,

I submitted a fix that you can integrate to get the problem resolved. CL44556650

Martin