We don’t have a slowdown.
We have a game hanging issue, and it’s most likely tied to saving a file just before doing a transition.
Is your new scene actually being loaded? Anything useful in the log?
Check for things like transition.cancel() in code somewhere that could be stopping the onComplete handler firing.
Nothing useful in log. We have no empty transition.cancel() calls in our code.
It’s an interesting bug…
What I do with these weird bugs is sprinkle lots of print(“1”), print(“2”), print(“3”), etc. calls in and see what numbers print (or don’t print) when it goes wrong.
Sometimes it’s the only way to localise a problem when on trappable errors are being raised.
The problem is that this doesn’t happen to us, just to players on PCs. We saw it a couple times over two years but couldn’t figure out what is causing it and players have no idea why because there’s no error dialog popping up.
We also get rid of all print() functions for a published version for speed, so they wouldn’t show up in a console.
Oh debugging installed apps is problematic unless you can log all errors to a server somewhere.
I don’t strip my print statements but do this, which nulls the print on a public build
if not \_debug then print = function() end endYes, that’s basically what we do.
John, is this still a problem?
Thanks
Rob
Hi Rob – we won’t know until we put out another release. We have almost never seen this bug. We never develop with Windows, so that makes it tough to see the problem.