[BUG REPORT] Differences between Androin and Windows Compilation

There are many changes between those 2 runtimes - some are unavoidable - others I also get upset about, but not the ones you mentioned.

1. Window and Android displays have their own settings. Perhaps the defaults are set differently - but you have many options for both. In the Android section there is great documentation showing how the different screen options work.
2. There is an issue with deceleration and bouncing ball movement in Android and Windows where it's set to 1 and not zero - there's a separate thread on that. But the issue was picked up in Windows actually.
3. Fusion is created to read the lines in order - however, some immediate events get triggered before it's finished reading the Start of Frame events - in Android because the devices have less memory this is more of an issue than in Windows. However, if you're using 2 different objects then of course you'd have 2 different behaviours. I work around it by not activating the "immediate" events until 1 second into the frame so that I know the start of frame events are done.
4. I've never had this error - and none of my games would work if I did get it - because I tend to put the values into the object as a default value rather than create it at runtime.
5. Android is typically downscaling and Windows is typically upscaling and that makes the difference. Also check that you're using Direct X and not Windows Standard for your PC settings. If you are using the actual Buttons object - that doesn't work on Windows Direct X or full screen - it's legacy content - use an active object instead. There aren't many resolutions that make the transition between Android and PC - I found creating the game in 1280x720 gives me the best results. Anything other than that requires me to make the game twice - a larger Windows version and a smaller Android version.