This is a known issue with the current firmware and Luban. It can be workarounded by chaning the lights or placing some objects in that area.
Have a look here:
I run into this problem, too.
I was in contact with support about this issue. Its well known and will take them some time to fix.
It seems to be a problem with the generated picture and the used memory.
You can workaround this by changing the light a bit or placing some item in the area it fails to capture.
This is what support told me:
Hi Thomas,
Thanks for reaching out to Snapmaker. I am sorry that you encountered such a problem.
It is a known issue. Such a problem happens because the s…