Sequencer crash on opening sequence

UE 4.18 Preview 4

We are experiencing a crash whenever we attempt to view a sequencer recording which includes actor “building_1_01” in the urban-city map from Urban City in Environments - UE Marketplace

checkf(ColorVertexBuffer->IsInitialized(), TEXT(“Color Vertex buffer was not initialized! Name %s”), *ColorVertexBuffer->GetFriendlyName()); (line 79 in LocalVertexFactory.h) fails in that case (as shown in screen shots).

If I may ask, do you know what might cause this issue?

Thanks,

Hi,

I’m looking more into the issue, but in the meantime would it be possible to get the callstack and the exact steps that you are taking to have this happen?

To get the callstack:

  • Go to the Launcher
  • Go the the engine version you are using
  • Go to the drop down tab next to it (See screenshots)
  • Go to options
  • Go to Editor symbols for debugging and check that box
  • Apply
  • Recreate the crash
  • You will have a box pop up with what looks like a lot of code
  • Post that here

This will help determine what is causing the error. Also, is it only happening with that one asset for you? I’ve gone through the comments to see if anyone has had a similar issue, and it would appear there was a problem with one of the building assets before.

-Thank you

LoginId:
EpicAccountId:

Assertion failed: ColorVertexBuffer->IsInitialized() [File:D:\Build++UE4+Release-4.18+Compile\Sync\Engine\Source\Runtime\Engine\Public\LocalVertexFactory.h] [Line: 79] Color Vertex buffer was not initialized! Name ColorOnly Mesh Vertices

UE4Editor_Core!FDebug::AssertFailed() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\core\private\misc\assertionmacros.cpp:414]
UE4Editor_Engine!FLocalVertexFactoryShaderParameters::SetMesh() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\engine\private\localvertexfactory.cpp:49]
UE4Editor_Renderer!FMeshMaterialShader::SetMesh() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\shaderbaseclasses.cpp:478]
UE4Editor_Renderer!FPositionOnlyDepthDrawingPolicy::SetMeshRenderState() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\depthrendering.cpp:528]
UE4Editor_Renderer!TStaticMeshDrawList::DrawElement<2>() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\staticmeshdrawlist.inl:210]
UE4Editor_Renderer!TStaticMeshDrawList::DrawVisibleInner<2>() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\staticmeshdrawlist.inl:361]
UE4Editor_Renderer!TStaticMeshDrawList::DrawVisible() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\staticmeshdrawlist.inl:413]
UE4Editor_Renderer!FDeferredShadingSceneRenderer::RenderPrePassView() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\depthrendering.cpp:950]
UE4Editor_Renderer!FDeferredShadingSceneRenderer::RenderPrePass() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\depthrendering.cpp:1300]
UE4Editor_Renderer!FDeferredShadingSceneRenderer::Render() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\deferredshadingrenderer.cpp:772]
UE4Editor_Renderer!RenderViewFamily_RenderThread() [d:\build++ue4+release-4.18+compile\sync\engine\source\runtime\renderer\private\scenerendering.cpp:2081]
UE4Editor_Renderer!TGraphTask

We were not using the launcher, but I reproduced it in a fresh launcher made version.

Thanks!

Hi,

Thank you for the getting the callstack but it looks like it isn’t going to be quite enough info for me to target what it is. However, if it is a bug with the engine it will help me when I record it. Would it be possible for you to send me the asset or the project? If you could send it here to me privately and post back here when you have sent it so I am sure to see it when you do. You may also want to go ahead and contact the seller since it is only happening with that one asset.

-Thank you

Hi,

I am unable to reproduce the issue on my end. Is there a set of direct repro steps that I could follow to get this to happen or would it be possible to get a repro project from you? Also, does this happen for you in 4.17? 4.18 is still in preview phase at the moment but officially releases some time soon. I would recommend keeping an eye on it over the course of the next week or so and trying the project in there to see if you still have the same issue.

-Thank you

Hi,

Due to how long this thread has remained inactive, I will be closing it out. If you find it to be an issue with the asset, you should be able to contact the seller to resolve the issue. If you find that it may be an issue within engine of have any other questions regarding this feel free to reopen this thread.

-Thank you