When using Lighting Scenario, loading order will affect how it's applied to the instances

When using Lighting Scenario, loading order will affect how it's applied to the instances, resulting in corruption if content is loaded after the lighting scenario

• Create a level containing a ISM component with some instance in it
• Make a lighting scenario & build the lighting
• Setup level streaming to load the lighting scenario 1st then stream the other level containing the ISM component

Without the fix, you should see lighting applied to instance producing weird visual artifact (see UDN for example of the look).

With the fix it should look normal.

"Session Disconnected" UEFN

How to delete some elements correctly when deleting an array loop?

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

How do I set a material as a post-processing material?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

What is the difference between Camera and CineCamera?

UMG RichText not appear image when packaged