Questions about limitations

Hi :D

I know than a definitive version is under development, but I've some doubts. I believe that the answers will be useful for those already developing something aiming to export to apk.

1. There will be limitations (frame size, number of events, etc.)?
2. Due to the variety of devices (with different hardware), there will be minimum requirements for run the MMF's applications?
3. We will have a feature to resize the screen according to the display device?

I am developing a platform game for Android devices. I'm avoiding the use of extensions and effects for better compatibility, but some information was not yet clear.
By the way, the error in scrolling was resolved?

Thanks!

Something I would say is that I'd wait to use the exporter before building something to 'port to it'. I've had no success 'porting' my older games to iPhone or Android, it's much better to design the game on paper (or in your brain if you're one of those types) and start building it once you can properly test it. Just a suggestion.

1) Any hard limits will be the same as the other exporters. What you're really limited by is what the device can handle.

2) The device must have a GPU. Anything else depends on how resource intensive the game is.

3) Yes, in beta 6

Hi, thanks for the answers! I know than I'm running a risk, but I'm not using extensions, effects, etc. I believe than compatibility issues I will not have, my problem is the performance and trivial features such as scroll and frame size. In addition, PC versions are best to distribute beta versions :D

Jamie, the beta 6 will have the option to show a load screen like we have in Flash?

What would the load screen be used for? It's not loading the application from the internet like with Flash.

Generally in mobile games (Java ME also has it), before starting the game, there is a screen "loading", some games for Android have this feature. When export to Java ME, for example, before the game starts, appears a white screen and a few seconds after the application starts. The loading screen would serve to show the progress of loading.
Do not know if it was very clear, my English is limited :(

Well, you could put a loading frame at the beginning of your application with "Start of Frame -> Go to Next Frame". The actual initialization of the application should be nearly as instant as it is in the standard runtime, since all the data is already on the device.

Hm... I'll try this in the Beta 6. Thanks, Jamie :D