If you create an editablemesh in a plugin, and have it under a mesh instance, then alt+tab to do something else and come back, the editablemesh will be gone and the mesh will be back to rendering an empty cube.
Before:
After:
Update:
Seems it’ll happen while studio is just idle too.
Probably that it can’t save all data of a editable mesh in memory, it probably attempts to store all triangle data and other data, but that memory has to be cleaned up or overwritten for studio to keep running, so it gets corrupted and defaults to a cube, i don’t really know what is happening here but that is the best thing i could think of. Short explanation i got from google: When a program requests memory, the heap manager allocates a block from the heap. If the program writes outside the bounds of this allocated block, it can overwrite adjacent memory, leading to corruption. This often happens due to buffer overflows or incorrect pointer arithmetic .
There’s no point in guessing what causes a bug because the engineers are gonna have look into it at some point to fix it, and then they’ll know regardless. So I wouldn’t throw guesses around for causes of bugs unless you know with 100% absolute certainty that that is causing the bug.
Thanks for reporting the issue. We’re going to release a new version of EditableMesh in Studio soon, which would require updating of the existing scripts. Sorry for the inconvenience and please let us know if the issue still exists after updating the scripts.
