Category: SDK
Reproducibility: Always
Summary: Creating a Landscape, using the Visibility tool and then viewing the thumbnail of the Landscape MIC in the content browser causes a Bugsplat.
Description:
If you create a landscape and apply one of the Landscape Materials (Blackforest or ZedLanding, etc), once you start painting, the Landscape will start creating instances of the MIC you use as a base for the Landscape.
When you use the visibility tool to hide areas of the Landscape - the tool works fine, however when you go to the Content Browser and scroll past the MICs it creates, the engine will bugsplat. The Launch.logs mentions issues of being unable to create Thumbnails.
The visibility tool is used in Zed Landing and Nightmare, so I was hoping we could use it as well - but this critical bug stops that from happening.
I've attached a map that will cause the issue - just click on the external packages in the Content Browser and scroll past it on the public build of the SDK to witness a crash:
https://drive.google.com/open?id=1pTKXe15Ol6VPKG-9LDS6g2XHNciboenb
I've also attached the Launch log:
https://pastebin.com/ChAR9F2M
Reproducibility: Always
Summary: Creating a Landscape, using the Visibility tool and then viewing the thumbnail of the Landscape MIC in the content browser causes a Bugsplat.
Description:
If you create a landscape and apply one of the Landscape Materials (Blackforest or ZedLanding, etc), once you start painting, the Landscape will start creating instances of the MIC you use as a base for the Landscape.
When you use the visibility tool to hide areas of the Landscape - the tool works fine, however when you go to the Content Browser and scroll past the MICs it creates, the engine will bugsplat. The Launch.logs mentions issues of being unable to create Thumbnails.
The visibility tool is used in Zed Landing and Nightmare, so I was hoping we could use it as well - but this critical bug stops that from happening.
I've attached a map that will cause the issue - just click on the external packages in the Content Browser and scroll past it on the public build of the SDK to witness a crash:
https://drive.google.com/open?id=1pTKXe15Ol6VPKG-9LDS6g2XHNciboenb
I've also attached the Launch log:
https://pastebin.com/ChAR9F2M