I have a decent sized forest made from 1 Speedtree and 2 meshes. When trying to erase the forest with ctrl + shift and the Foliage brush, I can get a small part of the area erased before the engine crashes. So far it has crashed every time I’ve tried to erase it, which has been a little over a dozen times now. It is working to erase part, save, erase a little more, save, and so on until crash, then load the latest save and continue, but obviously that’s very tedious. Not sure if anyone else is experiencing this, and I don’t really need a workaround or fix as I’m slowly getting the entire forest erased. but I thought I should say something.
Hi Joe,
I’ve tried replicating this on my end with 4.4.3 with no luck.
Can you provide a little bit of information to help me get a repro or at the very least offer some suggestions. 
- Can you attach a copy of your DxDiag and your Crash Logs?
Crash logs are located in this folder path:
C: \ Users \ [Your Computer Name] \ AppData \ Local \ Microsoft \ Windows \ WER \ ReportQueue
**Note that the AppData folder is hidden so if you don’t have hidden folders shown in Window you will not see it. You can alternatively get to it by going through your start menu > Run > and type in the file path here to directly open the folder.
- Are you able to reproduce this in a new project or is it only happening with this one? If it’s with any project, is the SpeedTree asset one that is provided free from their sample content on their website or one that you created?
Thank you!
Tim
Hi Tim,
I haven’t had a chance to grab 4.4.3 and test it out there yet, this was in 4.4.2. I was able to reproduce it in a new project, but only with a large brush removing somewhat dense areas. The brush was 8k and took a little time before it caused a crash. I wasn’t able to get a crash with a brush half that size or smaller, The Speedtree I used was a sample tree from their site, Broadleaf_Mobile.
Hope this helps.
link text
Thank you for the details! I’ll be testing this shortly to see if I can get a repro with this. I’ll get back to you and let you know what I find.
Tim
Hi Joe,
I’ve been trying to get this to crash on my end but am still having no luck, even with the Broadleaf and the 8K brush size.
I will say that my performance while running this test and trying to get the same effect was barely manageable. My FPS was low enough that it was freezing the editor while it was thinking. It may be best to avoid using such a large brush size when clearing out. Also, looking at your DxDiag we have a very similar setup.
If you’re still getting the issue with the smaller brush size This may be more cause for concern, but if you’re going through a lot of foliage with a large brush and many assets being deleted this may be the root cause.
Thank you for providing the crash logs!
Tim
Ok, thanks Tim.
It didn’t seem to be a problem with a smaller brush, I just had a lot of landscape to erase. But it was lagging a bit on my end too with a large brush, so maybe it’s just a drain on performance. I’ll avoid anything above 4k for brush size.
No problem!
It’s more than likely just deleting so many references at once that it’s hanging and crashing here in this instance. This is partly due to system specs and how many objects are being erased. If you start seeing this behavior with smaller brushes deleting fewer objects it may be more cause for concern and if that happens please post here and I’ll see if I can replicate on my end.
Thank you!
Tim