For the crashes, were there any messages in your command window that opened in the background?
We have made quite a few updates to transitions since 2646. I suspect the scale can’t be 0, is to prevent a divide by 0 issue and is probably just a warning.
Do you get the same behaviors with 27xx on Windows 7?
Generally if a line of code doesn’t happen, there was probably a fault that stopped that block of code. We would need to see the error. I know you said it was an error about not being zero, but there is usually a full back trace with an error message. We need the error copy/pasted, not hand typed.
If you can reproduce the error, it would be helpful.
I didn’t try any 27xx versions on Windows 7 yet. I’ll get to that this week.
Also, I’ll get the full error for you, that was just an example where the interpreter stopped executing on a transition, the ship shrunk and the call to relocate player never happened, so you were turned into a dot, albeit a powerful one :)
Corona didn’t crash, the app was still running, just the behavior became screwier and screwier.
In Lua when there is a runtime error, the block that is currently executing. Other things will still run, like a button that executes a different function. So finding out what the runtime errors can help us track the problem.
The last release version of Corona (build #2646) will crash on the *release version* of Windows 10 if your app uses MP3 files. We’ve resolved this issue in daily build #2682.
It’s technically a bug in the release version of Windows 10’s DirectX audio decoders. As in it wouldn’t crash with the beta versions of Windows 10. But that’s life for you.