Build 295.10 - Release Version

Quote from aa2953b4

I was copying the code quickly to show an example, which is why there's this small error. Fixing this line doesn't change anything. I remember having the same issue in another project as well.

Code

* Start of Frame
+ Group.0: Visible is on
	 Group.0 : Set alpha-blending coefficient to 0


* Start of Frame
+ Group.0: Visible is off
	 Group.0 : Set alpha-blending coefficient to 255


// Show obj


* On loop "@Obj_Show"
+ Fixed value of Group.0 = SELECTED_OBJECT_ID( "SPECIAL_VALUES" )
	Group.0 : Set IN_TRANSITION to 1
	 Group.0 : Set Visible on


* Group.0: Visible is on
+ IN_TRANSITION of Group.0 = 1
+ Group.0: AlphaCoef( "Group.0" ) > 0
	 Group.0 : Set alpha-blending coefficient to AlphaCoef( "Group.0" ) - TRANSITION_SPEED( "Group.0" )


* Group.0: Visible is on
+ IN_TRANSITION of Group.0 = 1
+ Group.0: AlphaCoef( "Group.0" ) = 0
	Group.0 : Set IN_TRANSITION to 0
	Special : Start loop ON_APPEARING_ENDS( "Group.0" ) 1 times


// Hide Obj


* On loop "@Obj_Hide"
+ Fixed value of Group.0 = SELECTED_OBJECT_ID( "SPECIAL_VALUES" )
	Group.0 : Set IN_TRANSITION to 1
	 Group.0 : Set Visible off


* Group.0: Visible is off
+ IN_TRANSITION of Group.0 = 1
+ Group.0: AlphaCoef( "Group.0" ) < 255
	 Group.0 : Set alpha-blending coefficient to AlphaCoef( "Group.0" ) + TRANSITION_SPEED( "Group.0" )


* Group.0: Visible is off
+ IN_TRANSITION of Group.0 = 1
+ Group.0: AlphaCoef( "Group.0" ) >= 255
	Group.0 : Set IN_TRANSITION to 0
	Special : Start loop ON_DISAPPEARING_ENDS( "Group.0" ) 1 times


[B]Fix:[/B]


// * Start of Frame
// + Group.0: Visible is on
	// Group.0 : Set BLEND_CONF to 0
	//  Group.0 : Set alpha-blending coefficient to 0


// * Start of Frame
// + Group.0: Visible is off
	// Group.0 : Set BLEND_CONF to 255
	//  Group.0 : Set alpha-blending coefficient to 255


// // Show obj


// * On loop "@Obj_Show"
// + Fixed value of Group.0 = SELECTED_OBJECT_ID( "SPECIAL_VALUES" )
// + BLEND_CONF of Group.0 > 0
	// Group.0 : Set IN_TRANSITION to 1
	//  Group.0 : Set Visible on


// * Group.0: Visible is on
// + IN_TRANSITION of Group.0 = 1
// + BLEND_CONF of Group.0 > 0
	// Group.0 : Sub TRANSITION_SPEED( "Group.0" ) from BLEND_CONF
	//  Group.0 : Set alpha-blending coefficient to BLEND_CONF( "Group.0" )


// * Group.0: Visible is on
// + IN_TRANSITION of Group.0 = 1
// + BLEND_CONF of Group.0 <= 0
	// Group.0 : Set IN_TRANSITION to 0
	// Special : Start loop ON_APPEARING_ENDS( "Group.0" ) 1 times


// // Hide Obj


// * On loop "@Obj_Hide"
// + Fixed value of Group.0 = SELECTED_OBJECT_ID( "SPECIAL_VALUES" )
// + BLEND_CONF of Group.0 < 255
	// Group.0 : Set IN_TRANSITION to 1
	//  Group.0 : Set Visible off


// * Group.0: Visible is off
// + IN_TRANSITION of Group.0 = 1
// + BLEND_CONF of Group.0 < 255
	// Group.0 : Add TRANSITION_SPEED( "Group.0" ) to BLEND_CONF
	//  Group.0 : Set alpha-blending coefficient to BLEND_CONF( "Group.0" )


// * Group.0: Visible is off
// + IN_TRANSITION of Group.0 = 1
// + BLEND_CONF of Group.0 >= 255
	// Group.0 : Set IN_TRANSITION to 0
	// Special : Start loop ON_DISAPPEARING_ENDS( "Group.0" ) 1 times

Display More

Yeah, without an MFA it's too hard to know what's wrong. I can't bugtest it (turn things off and on, change things, observe how it's working, etc.) and I can't see all of the relevant code. But I was curious, so I recreated the 'unfixed' portion of code that you posted here, and it works fine (see attached mfa); I can click around and none of the objects get stuck between fades. So your problem is probably caused somewhere else. Maybe it's something that happens when you call the @Obj_Hide loop, or maybe it happens in the ON_DISAPPEARING loop. Or maybe it's because you test for BLEND_CONF in the "On loop" events in your 'fixed' version, but you don't test for AlphaCoef in the original version.

Thank you for the attempt to help, and I can see that you are a talented programmer. If I get permission, I will contact you privately, so let's not clutter the public discussion.

Works great so far. No build issues with Android for Google Play.
No issues from Google Play on successful upload of .aab.
Keep up the great work!

It seems like expressions that call immediate events still crash, was not the case in 294

"Play sample file" action stopped working entirely in Android runtime. You can no longer retrieve an audio filepath and play it on the application. If you attempt to play a sample file, it returns -1 in channel duration. It worked flawlessly on 295.7, now it suddenly stopped working.

A project of mine heavily depends on this feature, please look into it.

Hello.
I tried to submit my android app on GooglePlayConsole.
But it did not work.

The target application is one that is already available in the store.
This update is for that.

Apps published in the store are created with apk.

The build was performed with the following settings.
API 33
Android target 13
Minimum Android version 5

When I upload the apk I created to GooglePlayConsole, I get the following warning message.

This app is published as an APK with TV support.
　That is, it belongs to one of the main activity's intent filters
　<category android:name="android.intent.category.LEANBACK_LAUNCHER"/>
　is included in the app.
　It should be published as an App Bundle instead.
　
　 *This is a machine translation of the warning text displayed in Japanese.

I believe this is the reason why the application is not successful.
I do not use the TV feature.

In a discord to exchange information about CF2.5, someone made the following suggestion.
　In RuntimeAndroid.zip
　RuntimeAndroid\app\src\main\AndroidManifest.xml
　<category android:name="android.intent.category.LEANBACK_LAUNCHER"/>
　I think we can remove this text.
　
　Is this valid?

If I create it with aab instead of apk, this problem might be solved.
In any case, any workaround for this problem would be appreciated.

Quote from mugimiso

Hello.
I tried to submit my android app on GooglePlayConsole.
But it did not work.

The target application is one that is already available in the store.
This update is for that.

Apps published in the store are created with apk.

The build was performed with the following settings.
API 33
Android target 13
Minimum Android version 5

When I upload the apk I created to GooglePlayConsole, I get the following warning message.

This app is published as an APK with TV support.
　That is, it belongs to one of the main activity's intent filters
　<category android:name="android.intent.category.LEANBACK_LAUNCHER"/>
　is included in the app.
　It should be published as an App Bundle instead.
　
　 *This is a machine translation of the warning text displayed in Japanese.

I believe this is the reason why the application is not successful.
I do not use the TV feature.

In a discord to exchange information about CF2.5, someone made the following suggestion.
　In RuntimeAndroid.zip
　RuntimeAndroid\app\src\main\AndroidManifest.xml
　<category android:name="android.intent.category.LEANBACK_LAUNCHER"/>
　I think we can remove this text.
　
　Is this valid?

If I create it with aab instead of apk, this problem might be solved.
In any case, any workaround for this problem would be appreciated.

Display More

you can handle this in android properties

Please login to see this attachment.

I have a problem that I wrote about in another post with pictures in the new version of Fusion (I updated from 293.10 to 295.7) where the comments are not showing correctly and also what is worse the actual object icons are extremely tiny to the point it is very hard for me to continue work as I have to squint to see the objects:

Please login to see this link.

From what another user wrote (defisym) who have the same problem at least with the comments is that it is a dpi scaling issue. My monitor is a 4k monitor with 300% scaling. This was not an issue in Fusion 293.10 or previous.

Update: Naitorstudios fixed it for me

Setting high dpi scale override to system fixes it in the fusion exe properties

(Not sure if feature requests should go here or another/their own separate thread)

I've been getting a lot of use out of the 'pick the closest (Object A) from (Object B)' event - I was wondering if similar events could be added, such as
- pick closest (Object A) from specific xy coords
- pick furtherest (Object A) from (Object B/specific xy coords)
- pick (Object A) with the lowest/highest alterable value

Quote from Yves

Hello everyone,

EDIT: Build 295.7 has been replaced by build 295.8.

The build 295.8 is available in the Please login to see this link. (and on Steam as beta version).

This is a beta version so be careful as usual. You can reinstall the build 294.14 if any issue (you don't need to uninstall first, just reinstall the patch of the build 294.14). You can also, if you want, duplicate the Clickteam Fusion [Developer] 2.5 folder to a new folder and install the patch to this second folder, so that you can use both versions (just run mmf2u.exe in this folder to launch the product)

Some optimizations have been done in the runtime, especially on non-Windows platforms. We would appreciate if you could test as many games/apps as you can and let us know if there is any issue specific to this build. Thanks!

Please login to see this link.

If any question or issue specific to this build, please post it here, thanks!

PS: the CF 2.5 patch updates all the installed exporters, as well as the 2.5+ DLC, you do not need to reinstall them.

Thanks!

Display More

Works flawlessly. I built our largest app both in .apk and in .abb.
No issues and it looks like the app sped up a bit.
Load times on my LG STYLO 5 were like 3 seconds.
Now Load time is roughly 1 second.
Impressive! Keep up the great work!

Quote from marbenx

(Not sure if feature requests should go here or another/their own separate thread)

I've been getting a lot of use out of the 'pick the closest (Object A) from (Object B)' event - I was wondering if similar events could be added, such as
- pick closest (Object A) from specific xy coords
- pick furtherest (Object A) from (Object B/specific xy coords)
- pick (Object A) with the lowest/highest alterable value

That last one already exists. It's called Pick with minimum/maximum expression value. Just place your desired altVal in the expression editor, and it will pick the object that has the highest/lowest value for that altVal. You can use it to compare not just altVals, but all sorts of things (eg. pick the object with the biggest scale, highest alphaCoef, highest X position, etc. ). Which means that you can use it to achieve your first request, by referencing an object's Odistance. The following example will pick the explosion that's closest to x1000, y2000:

Please login to see this picture.

In case it's unclear, you can access the Odistance function here:

Please login to see this picture.

Quote from VBEinc

Works flawlessly. I built our largest app both in .apk and in .abb.
No issues and it looks like the app sped up a bit.
Load times on my LG STYLO 5 were like 3 seconds.
Now Load time is roughly 1 second.
Impressive! Keep up the great work!

Look for me in Discord, i want you to test the changes in Active Picture Object

Quote from Fernando

you can handle this in android properties

Please login to see this attachment.

It passed the android review.
Thank you very much!

Also I tested to build an exe with 293.10 and one with 295.7. Both are the exact same just built with different Fusion version and the old one get 1 virus flag while the new build get 4 flags.

Any input on why this could be the cause and if possible to reduce it as before?

Please login to see this link.

Please login to see this link.

First build (293.10) get this:

Bkav Pro
W32.AIDetectMalware

The second build (295.7) get:

Bkav Pro
W32.AIDetectMalware

Cynet
Malicious (score: 100)

Rising
Trojan.Generic@AI.100 (RDML:cQEjUgAMsYS1yvGdEJehZw)

SecureAge
Malicious

Is GDPR object fixed for iOS? The deadline is for January 2024...

Not sure if this is the right place to make a suggestion but it feels unnecessary that the Layer Toolbar is visible in the Event Editor even if it is pinned for the Frame Editor. It should only need to be seen in the Frame Editor? The actual layers still vanish in the Event Editor but the toolbar is still there and taking up unnecessary space.

Quote from Volnaiskra

That last one already exists. It's called Pick with minimum/maximum expression value. Just place your desired altVal in the expression editor, and it will pick the object that has the highest/lowest value for that altVal. You can use it to compare not just altVals, but all sorts of things (eg. pick the object with the biggest scale, highest alphaCoef, highest X position, etc. ). Which means that you can use it to achieve your first request, by referencing an object's Odistance. The following example will pick the explosion that's closest to x1000, y2000:

Please login to see this picture.

In case it's unclear, you can access the Odistance function here:

Please login to see this picture.

Ah, cheers! I'd completely missed these