Projects are able to "crash"
-
Tyller_ aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa last edited by
Projects are able to “crash”, mainly possible with 2D and 3D physics blocks, when a “crash” happens the project freezes up completely, the stop button is not grayed out but clicking it does nothing neither does clicking the green flag, the editor still works but the preview won’t work and the only fix is refreshing the page, I have seen it happen in different situations but I recreated it simply with https://play.creaticode.com/projects/6511e3017ace4f296fd39457
Where the debug being on causes the “crash”. -
@jaysen4games-gmail
Hi, some blocks may not handle all edge cases well yet, and the specific reason depends on what the block is failing to do.
In your example, the 2D physics block tries to create a circle object to represent the sprite by reading the shape of the costume, and it finds the costume has a width of 0, so it doesn’t know how to proceed in this case.
We will add a guard to prevent this from causing the project to freeze. But bear in mind that even if the project does not freeze, it will still not be successful in this case, since the sprite’s costume can not be empty if we need to add a physics body to it.
Thanks for pointing out this issue.
CreatiCode Support
-
Tyller_ aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa last edited by
@info-creaticode thank
-
Tyller_ aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa last edited by
@jaysen4games-gmail sorry, I was making sure I didn’t have to refresh, a safeguard would be very useful as when a crash happens I have to refresh which takes a while because I mainly use an iPad, I run into crashes semi frequently and a fix to not need to refresh but still knowing an error occurred via the console (assuming you would add a warning in console because it would let people know why something didn’t run) would make debugging and creating projects a much shorter experience when dealing with crashes
-
@jaysen4games-gmail
Noted. We will make sure proper warning messages are given when invalid requests are received.
Thanks for the suggestion.
CreatiCode