Build 283.1 - beta version

[Yves]

Hi,

The build 283.1 (pre-release) is available in the Product Owner's Lounge forum.

Change log

Hopefully this build is stable enough and will be officially released within a few days.

As usual this is a beta version, so make backup copies of your MFA files, just in case...

Let us know if any new problem in this version, thanks!

Thanks!

Yves.

[AndyH]

Thanks! Will start playing with this version.

[SolarB]

Great update, but issues still exist:

http://bugbox.clickteam.com/issues/2361
http://bugbox.clickteam.com/issues/2322

[Olivier]

My app hangs if I try to jump to another frame, and if I have sent a POST call with the Get object prior to that. I didn't try with a GET call.

EDIT: The app hangs when I run it with F8. I didn't actually tried to build it under any runtime.

[Yves]

Hmm, I don't see how this problem could be specific to this patch, the patchs don't update the MFX files of the Get object.

[Olivier]

You are right Yves, I have overlooked this. Looks like my server is lagging today. My apologies.

[paobrasil]

There is some simple USABILITY problems on fusion that it would be amazing if be fixed. I will quote below:

- If you call for first frame of Active on event editor, this first frame starts on 0. But, on image editor, the first frame starts with "Frame 1". This need to be fixed because can confuse the user, just put the first frame on event editor named "Frame 0".

- If you create more than one custom movement to active, in it propierties, this is called "Movement #1" and "Movement #2"....and if you go to event editor to SELECT MOVEMENT....and put on "USE CALCULATION", on this expression popup, on the right its writed "Result should be between 1 and 1024".....BUT, to select the first movement, you need to call 0, not call 1.....so, need to be fixed, just call the first movement "Movement #0" and remove or change the tip "Result should be between 1 and 1024".


Well....maybe there is another problems with this same issue........but these were the ones I noticed at the time.

Best regards

[mcm85]

Great update, but issues still exist:

http://bugbox.clickteam.com/issues/982

http://bugbox.clickteam.com/issues/1991 (I can't publish my game if this bug isn't resolved)

[Outcast]

The bug with iOS inapp where the cancel purchase event are never triggered is still not fixed. I have had to skip iaps completely in my two previous games and had to go back to MMF (where the same exact events work perfectly) in my latest because of this, can it please be fixed? I have waited for months for this. I posted an example here (post 75) http://community.clickteam.com/threads/89024-Build-283-0-beta-version/page8

Also html5 games with music don't work anymore in Chrome even with this version. I uploaded examples here (last post) http://community.clickteam.com/threads/88122-Latest-Chrome-update-breaks-HTML5-games/page2

[Yves]

Outcast, please discuss directly with Anders about the iOS InApp issue, thank you. Please provide him with the simplest example as possible (the fact it works in MMF2 doesn't mean anything, the implementation in 2.5 is different).

Also no offense but I don't see how we would have been aware of the fact your problem hadn't been fixed as you didn't answer the PM I sent you in July asking if it was fixed in the build 283.3, especially as others have reported the problems with InApp were fixed.

For Chrome, please continue posting in the HTML5 forum or better in the HTML5 bug box and either attach a MFA or send a PM to Francois directly. It could be easier for him to see what happens if he can build the app himself.

Thanks.