jobel
tarek2
WackyToaster
Grimmy
It looks like this major issue will continue to be ignored until and if either
Grimmy can change the status of his original bug report back to "open" or if one of us simply creates a new bug report reporting the same bug.
github.com/Scirra/Construct-3-bugs/issues/4422
Ashley This issue is definately back and completely blocking many of your customers from finishing their games. What's our proper course of action for you to take this seriously? Does Grimmy have to reopen the bug report or do we need to make a duplicate report?
If you try your own or the original example project 10 times and don't get the bug on your end, (even though we've said repeatedly the bug definately occurs, but often after many runs without the problem occurring) Then shouldn't we find out what is the difference between your set up and ours? Maybe it's a matter of browser, OS, system specs?