Build 257.28 (Beta)

Yves · August 30, 2013 at 12:20 AM

Hi everyone,

The beta 257.28 is available.

If the Android exporter is already installed on your machine, just download and install the patch of Please login to see this link..

If the Android exporter is not installed, run the installer below (and then run the patch above to be sure the other exporters are up to date):

Please login to see this link.
Please login to see this link.
Please login to see this link.

If any problem with this version, just re-install the Please login to see this link..

PS: please make backup copies of your MFA files before using this version, just in case...

Thanks for testing!

Yves.

Bug fixes and new features in 257.28

- Fix for OUYA buttons
- Fix for "follow the frame" option of extension objects
- New OUYA InAppPurchase features

Bug fixes and new features in 257.27

- New "Build API" option in the Android properties of the application to allow you to select the Android API you want to use to build your application with (PS: the API you indicate must be installed in the Android SDK). Note 1: even if you choose a recent API your application will continue working on devices with an older API (>= 2.3). Note 2: we've noticed a possible significant speed increase if you build with newer APIs, we would appreciate if you could build your applications with different APIs, test them on different devices and report your results, thanks!

- New Android Dialog object, allows you to display various types of Android controls
- (Dev only) New AdMob object, allowing to change size, color, alignment and others in Admob
- New features in the Android object to show/hide the action bar and retrieve information about the device
- New features in the Android object to show/hide the keyboard and detect if it's visible
- Various crashes have been fixed (waiting for an exact change log)
- Accelerometer object: it should now return values in G identical to the iOS version (it was previously returning values in m/s and these values were different on several devices)
- Fix in Center Display action in previous beta version
- Added security in INI object to avoid it to crash in some error cases
- Fix in radio button objects
- Easing object now ported to Android
- (Dev only) Update in LeadBolt and ChartBoost objects
- Video Android object: you can now pack up to 5 videos in the APK
- Get Object now can handle https and authorization (password and user)
- Security fixes in Listbox and Combobox objects
- Security added to Sound features
- Fixed crashs in OUYA apps
- Active and Background System Box objects: now follow the frame + images in pattern mode are now clipped to the object's rectangle.
- Fix in Location object
- Fix in Active Picture object (was not loading files in some cases)

I probably forget things...

Also I think OUYA InApp Purchase features have been implemented but the actions are not visible in this version, I think I haven't been sent the new OUYA object. I'll upload it later.

Bug fixes and new features in 257.23 & 24

- No fixes in the Android exporter, only fixes in the editor and PC runtime.

Bug fixes and new features in 257.22

- new Required Hardware properties in the Android properties of the application (OpenGL 2.0, GPS, Camera, Bluetooth)
- if Require GPU is selected, then the application no longer appears for devices that have no GPU
- if you select OpenGL 2.0 as graphic mode, the application no longer appears for devices that haven't this version of OpenGL
- new OUYA icon property. This image is displayed by the launcher on OUYA consoles (size = 732x412).
- new OUYA application propery, you have to select this property for the OUYA icon to be included.
- new Calendar Entry object (allows you to read/write in a device calendar)
- new Input Type object (allows you to set the type of keyboard in edit boxes)
- new Video Android object (allows you to play video files on Android devices - mainly .mp4 format, see the documentation)
- [MMF2 Dev only] new ChartBoost object (ads)
- [MMF2 Dev only] new In-App Billing object (In-app Billing is a Google Play service that lets you sell digital content from inside your applications)
- [MMF2 Dev only] new LeadBolt object (ads)
- Unicode version: the Edit box settings were not correctly read in the application
- incorrect indexes in sound channel actions
- List and Combo added recognition to *.ext for file list (pige pas, demander à Fernando)
- Control objects are now resized correctly
- List and ComboBox Objects, added 3D look, custom background and text color
- Clipboard functions now work
- Active/Background System Box, now display correct text color
- Multiple Touch object: new "Touch on an object" and "A touch is active on an object" conditions
- Multiple Touch object: new pinch features

Bug fixes and new features in 257.20

- Fix issues with joystick position
- Transitions are now ignored (instead of crashing the Android application)
- Jump to current frame no longer crashes
- Fixes in decimal properties in counters
- StringBuilder extension has been ported
- Open/Pause debugger actions no longer crash the runtime
- Gradient counter not displayed when you set it to a floating point value
- Array object: crash in the Clear Array action for text arrays

Bug fixes and new features in 257.17

- Fix in the Compare to Chrono & Count Down conditions of the Date & Time object, as well as in the Retrieve stop watch time and Retrieve count down time functions

Bug fixes and new features in 257.16

- Accelerometer values are now in the same range as the iOS runtime
- Accelerometer joystick now works (in the Frame properties)
- Various fixes for interoperability with the Unicode export
- Embedded files now work if you pass a full pathname
- List Box and Combo Box objects: Load File List and Load Directory List have been implemented
- Combo Box object: Load & Save List now work
- Combo Box object: the base index was not taken into account in values returned by Find String
- "Mouse in zone" did not work correctly (Fernando)
- For Each object fixes (Fernando)
- String Parser MD5 function did not work correctly (Fernando)
- Fix disappearing image counter objects (Fernando)

Bug fixes and new features in 257.14

- Black screen issue: if the "Force GPU rendering" option was checked in the Android Developer options Android was displaying a black screen for applications created with MMF2. Note: the "Force GPU rendering" option might cause reduced performance (not sure though), you should test your applications with and without this option and if any speed issue you should probably tell your users to turn it off.
- List and ComboBox objects were incorrectly initialized in the Unicode version.

Sparckman · August 30, 2013 at 12:56 AM

Downloading..

happygreenfrog · August 30, 2013 at 1:37 AM

So, basically, now we can make games for the OUYA (if it actually works right (which I'm guessing it does))? AWESOME! I don't have an OUYA yet, but I'm considering getting one once I can get the money to do so from selling games.

Koji_Kabuto · August 30, 2013 at 3:20 AM

Congratulations Clickteam for OUYA update!

Matriax · August 30, 2013 at 7:52 AM

Well! I hope this finally solve all the problems to get the game on OUYA! and thanks for the In-App purchases! TIme to download and test...

Matriax · August 30, 2013 at 8:28 AM

Errr.... It's me or the games still crash when you press multiple buttons between the change of frames?

Now the buttons works again, but again the crash problem between frames comes back and seems now is worst and the problem occurs more times.

Its me or every body have the problem again?

Sparckman · August 30, 2013 at 1:56 PM

Well yes and no. Certainly is not worse.

This test has been done using API 18.
Here is a test I did. Using a value instead of a button to change frames, you can pin-point the issue easier.

On button press O ------------- Add +1 to counter;
Counter >= 1 ------------------- Counter +1;
Counter >= 40 ------------------ Nextframe;

Using a counter during frame change and Holding all the button will not crash the app.
Holding one button during frame change during change.... will not crash the app.
Repeatedly pressing any button during frame change will crash the app.

Here is the test file.
Please login to see this attachment.

You cannot crash the game if the OUYA object is not included.
I even tried
On button press O ------------- Add +1 to counter && delete OUYA object;

but the app still crashed if you press any button rapidly during frame change.

Here is another test still using API 18 but without the OUYA object:
Please login to see this attachment.
As far as I know it's impossible to crash this app, as long as the OUYA object is not used.

I would say that as soon as function nextframe is called
the OUYA object should be disable.
and re-enable as soon as the frame loads again.
Since the app only crashes on load.

Matriax · August 30, 2013 at 2:12 PM

Quote from Sparckman

Well yes and no. Certainly is not worse.

This test has been done using API 18.
Here is a test I did. Using a value instead of a button to change frames, you can pin-point the issue easier.
On button press O ------------- Add +1 to counter;
Counter >= 1 ------------------- Counter +1;
Counter >= 40 ------------------ Nextframe;
Using a counter during frame change and Holding all the button will not crash the app.
Holding one button during frame change during change.... will not crash the app.
Repeatedly pressing any button during frame change will crash the app.
Here is the test file.
Please login to see this attachment.
You cannot crash the game if the OUYA object is not included.
I even tried
On button press O ------------- Add +1 to counter && delete OUYA object;
but the app still crashed if you press any button rapidly during frame change.
Here is another test still using API 18 but without the OUYA object:
Please login to see this attachment.
As far as I know it's impossible to crash this app, as long as the OUYA object is not used.
I would say that as soon as function nextframe is called
the OUYA object should be disable.
and re-enable as soon as the frame loads again.
Since the app only crashes on load.

Display More

I tried this in the 257.24, create the ouya object only after 0.5s after the next frame is loaded and get the same.

Also i test and my game crashes including if the OUYA object not is in the frame

BTW, this still not solved and i believe if we try to upload to the OUYA revision will be denied again .

Edit: I go to download your examples and test again in these new beta

Edit 2: Ok, now seems that without OUYA object no crashes. But i noticed that sometime the game when is clicked appear a black screen but well maybe is my OUYA that goes crazy after too many tests XDD

Edit 3: With the OUYA object included in your example as you said even with counters,etc... still crash

Fernando · August 30, 2013 at 2:52 PM

Hi,

Try jumping using on button released condition, should be a better performance.

BTW I am waiting for my OUYA!

Sparckman · August 30, 2013 at 3:23 PM

What API are you using to export the .APK? I am using API 18.
Sideload this .APK on your ouya.

Let me know if you can make it crash. :pacman::pacdot::pacdot::pacdot::pacdot:
Please login to see this attachment.

Matriax · August 30, 2013 at 4:01 PM

Quote from Sparckman

What API are you using to export the .APK? I am using API 18.
Sideload this .APK on your ouya.
Let me know if you can make it crash. :pacman::pacdot::pacdot::pacdot::pacdot:
Please login to see this attachment.

I'm Using API 14.

Without the OUYA object the game not crash in the last tests, but with the OUYA Object with your counters,etc... i can get it crash pressing/holding buttons. Yes is more difficulty to get it crashed but still.

Your "OUYA crash test no OUYA OBJ.apk" is tested and i can't get it crashed, but i suppose this example not have the OUYA object, right?

Sparckman · August 30, 2013 at 4:22 PM

Quote from Matriax

I'm Using API 14.
Without the OUYA object the game not crash in the last tests, but with the OUYA Object with your counters,etc... i can get it crash pressing/holding buttons. Yes is more difficulty to get it crashed but still.
Your "OUYA crash test no OUYA OBJ.apk" is tested and i can't get it crashed, but i suppose this example not have the OUYA object, right?

OUYA crash test no OUYA OBJ.apk Doesn't have the OUYA Object.

This .APK was exported using API 18. It only uses Keyboard buttons.

Example: UP,DOWN, LEFT, RIGHT = the D-PAD in OUYA
SHIFT = O
ENTER = O
CTRL = O
Backspace = A

Matriax · August 30, 2013 at 4:31 PM

Quote from Sparckman

OUYA crash test no OUYA OBJ.apk Doesn't have the OUYA Object.
This .APK was exported using API 18. It only uses Keyboard buttons.
Example: UP,DOWN, LEFT, RIGHT = the D-PAD in OUYA
SHIFT = O
ENTER = O
CTRL = O
Backspace = A

Works perfect. And is not possible get the other keys for L1, L2, R1, R2,etc.... of the OUYA controller? I know not is the sollutio but if is possible after see that with this there is no problem we can upload games until the problem is solved.

Sparckman · August 30, 2013 at 7:06 PM

You can upload free now using those two buttons and the d-pad. But they would have to be free games since the OUYA object would make the app crash. I am doing a lot testing to see if there is a way around it. until the next release.

Sparckman · August 30, 2013 at 9:00 PM

Here is a test for OUYA - Crash seems Solved!

Please login to see this attachment.
Please login to see this attachment.

Please login to see this attachment.
Please login to see this attachment.
Sideload these two .APKs and cannot be crashed holding the buttons while changing frames.

Try it out. :pacman::pacdot::pacdot::pacdot::pacdot::pacdot::pacdot:

Fernando has the new runtime.

Matriax · August 30, 2013 at 9:07 PM

Quote from Sparckman

Here is a test for OUYA - Crash seems Solved!
Please login to see this attachment.
Please login to see this attachment.
Please login to see this attachment.
Please login to see this attachment.
Sideload these two .APKs and cannot be crashed holding the buttons while changing frames.
Try it out. :pacman::pacdot::pacdot::pacdot::pacdot::pacdot::pacdot:
Fernando has the new runtime.

Hi,

I also get the Fernando AndroidRuntime and after minutes i was unable to crash the app without counters and nothing.

Unfortunately i have another type of error and is that after launch the APP and exit using the double tap of "OUYA OFF"(i don't know how name this button) the next times when i try to execute the APP i get a BlackScreen and other time runs normally. But i thinks more times i get a blackscreen than runs

You have the same problem? I thought was that i have an OUYA object in the first frame but after remove it the problem continues.

Edit: I go to test the "with ouya object" of your news .apk and test if do the same thing,

testing.....

Edit 2: Nothing i have the same problem with your .apk Sparckman. The first time runs, but the second time i try to run the crash test i get a BlackScreen . I used your exported .apk. It's me or you have the same problem?

Sparckman · August 30, 2013 at 10:16 PM

Well you can hard-crash a game by Holding the System Button for 3 Seconds.
The proper way to exit the game is double tapping the system button.

But yes you are right, well this is not as bad as crashing. But it seems that the game lingers in the background.

You have to manually FORCE STOP under applications. ( Manage / System / Advanced / Apps )

This doesn't happen without the OUYA object. I tested both.

A solution could be disable that System button and replace it with a menu where you can pick Exit.
Or just end the app upon touching that button.

Edit:
Please login to see this attachment.
Please login to see this attachment.
Now it seems that the system button doesn't respond. I attempted to exit the app if the system button is pressed but
i doesn't work. And as said the game lingering in the background only happens when the OUYA object if present.

Matriax · August 30, 2013 at 10:35 PM

Quote from Sparckman

Well you can hard-crash a game by Holding the System Button for 3 Seconds.
The proper way to exit the game is double tapping the system button.
But yes you are right, well this is not as bad as crashing. But it seems that the game lingers in the background.
You have to manually FORCE STOP under applications. ( Manage / System / Advanced / Apps )
This doesn't happen without the OUYA object. I tested both.
A solution could be disable that System button and replace it with a menu where you can pick Exit.
Or just end the app upon touching that button.

Mmm i don't know if the OUYA revision will aprove remove the system button adding an "exit button" in the main menu. Always that starts a game appears a text saying "Double Tap System Button to exit" that means OUYA want to use this system in all the game like use "O" as enter or "A" as Back (I get this feedback from the OUYA revision).

BTW, this not happens in previous betas, maybe the crash solutions between frames affect to this or is a new bug? And well i think with some time Fernando or other will fix the balckscreen problem, i hope!

Again, we need to wait

Sparckman · August 31, 2013 at 1:36 AM

I'm working on a game you only need to push one button. But the OUYA object yes. Needed. Well, it's a lot closer now.

Fernando · August 31, 2013 at 2:42 AM

Hi,

Now the runtime is using the last version of the ODK/LIB 1.0.6, and many of the buttons have been deprecated.

Also seems that SYSTEM button was deprecated in the early ODK, now changed to MENU.

let me see what it can be done, to translate SYSTEM to MENU.

BTW thanks for your help testing the modifications!

Quote from Matriax

Hi,
I also get the Fernando AndroidRuntime and after minutes i was unable to crash the app Please login to see this picture. without counters and nothing.
Unfortunately i have another type of error and is that after launch the APP and exit using the double tap of "OUYA OFF"(i don't know how name this button) the next times when i try to execute the APP i get a BlackScreen and other time runs normally. But i thinks more times i get a blackscreen than runs Please login to see this picture.
You have the same problem? I thought was that i have an OUYA object in the first frame but after remove it the problem continues.
Edit: I go to test the "with ouya object" of your news .apk and test if do the same thing,
testing.....
Edit 2: Nothing i have the same problem with your .apk Sparckman. The first time runs, but the second time i try to run the crash test i get a BlackScreen Please login to see this picture. . I used your exported .apk. It's me or you have the same problem?

Display More

Please provide us a Log, this seems to be more texture issues than controllers, so a log is a most to check what is occurring

Log in or register!

Looking for Customer Support?

Build 257.28 (Beta)

Participate now!

Useful Links, Resources & Information

Fusion 2.5 Resources

Crowdfunding Focus