Bug on Android: Text isn't showing up when using Button is Checkbox mode, probably happens to some other modes as well.
Build 293.10 - Release version
Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
-
Seems fine here, to check:
if you have check "use system fonts in text objects"
many new devices with dark theme use white fonts, and if you are using a white frame for sure you will not see it.
possible solutions
1.- not to use system fonts
or
2.- uncheck System colors in button object and set the text color you need for your implementation.
-
Unchecking System Colors is completely broken on Windows if I have transparent checked (at least on Windows 11), it completely ignores the selected colors, becomes a black rectangle.
Now, on Android, it behaves in a lot of different ways, having a inexistent font doesn't affect it...
System colors unchecked gets the selected colors, but if it also has transparent checked it behaves as if System colors was on, showing white text, this is happening no matter if using light or dark mode.
It also seems like there's no background color, it's transparent all the time, completely ignores the Transparent checkbox, but like I said above, it override System colors making text appear white.Just for reference, I'm using a Samsung S21 Ultra.
Also, I noticed that some samples may play all distorted the first time it plays on some devices, it's pretty annoying and can be problematic... -
Please login to see this attachment.Why does it exit when you open an MFA file and are not sure when you accidentally exit
-
Not a bug just a request as i see many requests for things added. Current dark skin only changes part of the GUI.
Please add native support for Windows Dark Colors. So when you choose to use dark colors in windows the whole Fusion GUI will default to dark mode. I realize you can use a skin and install third party stuff to windows like blinds or other apps to force fusion to do this. I just thinks that is a bit Meh. So how about a mode that actually changes the whole GUI in fusion like almost every other app on windows has now. If there is a reason this cant be done please share. -
Unchecking System Colors is completely broken on Windows if I have transparent checked (at least on Windows 11), it completely ignores the selected colors, becomes a black rectangle.
Now, on Android, it behaves in a lot of different ways, having a inexistent font doesn't affect it...
System colors unchecked gets the selected colors, but if it also has transparent checked it behaves as if System colors was on, showing white text, this is happening no matter if using light or dark mode.
It also seems like there's no background color, it's transparent all the time, completely ignores the Transparent checkbox, but like I said above, it override System colors making text appear white.Just for reference, I'm using a Samsung S21 Ultra.
Also, I noticed that some samples may play all distorted the first time it plays on some devices, it's pretty annoying and can be problematic...About the colors, not sure I tested here with a Samsung A50, it could be something in this device theme, better post a small mfa for me to check, I will recommend to open a new post for this in android forum, since is not related to 293.X version
also for the samples play all distorted add a small mfa with the sound that is giving problem to check here.
-
Build 293.6 - Beta version. (Build API30, Target android version 11.0)
unable to compile my app (application.aab) for android, got this error message:
WARNING:: Please remove usages of `jcenter()` Maven repository from your build scripts and migrate your build to other Maven repositories.
This repository is deprecated and it will be shut down in the future.
See Please login to see this link. for more information.
Currently detected usages in: root project 'AndB785.tmp', project ':app'
> Task :app:preBuild UP-TO-DATE
> Task :app:preReleaseBuild UP-TO-DATE
> Task :app:writeReleaseApplicationId
> Task :app:analyticsRecordingRelease
> Task :app:compileReleaseRenderscript NO-SOURCE
> Task :app:generateReleaseResValues
> Task :app:generateReleaseResources
> Task :app:createReleaseCompatibleScreenManifests
> Task :app:extractDeepLinksRelease
> Task :app:processReleaseMainManifest
> Task :app:processReleaseManifest
> Task :app:processApplicationManifestReleaseForBundle
> Task :app:compileReleaseAidl NO-SOURCE
> Task :app:checkReleaseDuplicateClasses
> Task :app:generateReleaseBuildConfig
> Task :app:checkReleaseAarMetadata
> Task :app:javaPreCompileRelease
> Task :app:mergeReleaseShaders
> Task :app:compileReleaseShaders NO-SOURCE
> Task :app:generateReleaseAssets UP-TO-DATE
> Task :app:mergeReleaseAssets
> Task :app:processReleaseJavaRes NO-SOURCE
> Task :app:desugarReleaseFileDependencies
> Task :app:processReleaseManifestForPackage
> Task :app:mergeExtDexRelease
> Task :app:mergeReleaseJniLibFolders
> Task :app:mergeReleaseJavaResource
> Task :app:mergeReleaseResources
> Task :app:collectReleaseDependencies
> Task :app:configureReleaseDependencies
> Task :app:parseReleaseIntegrityConfig
> Task :app:writeReleaseAppMetadata
> Task :app:validateSigningRelease
> Task :app:mergeReleaseNativeLibs> Task :app:stripReleaseDebugSymbols
Unable to strip the following libraries, packaging them as they are: libES1Renderer.so, libES2Renderer.so, libES3Renderer.so, libRuntimeNative.so, libgdx.so.> Task :app:extractReleaseNativeSymbolTables
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libES1Renderer.so because unable to locate the objcopy executable for the arm64-v8a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libES2Renderer.so because unable to locate the objcopy executable for the arm64-v8a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libES3Renderer.so because unable to locate the objcopy executable for the arm64-v8a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libgdx.so because unable to locate the objcopy executable for the arm64-v8a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libRuntimeNative.so because unable to locate the objcopy executable for the arm64-v8a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libES1Renderer.so because unable to locate the objcopy executable for the armeabi-v7a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libES2Renderer.so because unable to locate the objcopy executable for the armeabi-v7a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libES3Renderer.so because unable to locate the objcopy executable for the armeabi-v7a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libgdx.so because unable to locate the objcopy executable for the armeabi-v7a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libRuntimeNative.so because unable to locate the objcopy executable for the armeabi-v7a ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86\libES1Renderer.so because unable to locate the objcopy executable for the x86 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86\libES2Renderer.so because unable to locate the objcopy executable for the x86 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86\libES3Renderer.so because unable to locate the objcopy executable for the x86 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86\libgdx.so because unable to locate the objcopy executable for the x86 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86\libRuntimeNative.so because unable to locate the objcopy executable for the x86 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86_64\libES1Renderer.so because unable to locate the objcopy executable for the x86_64 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86_64\libES2Renderer.so because unable to locate the objcopy executable for the x86_64 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86_64\libES3Renderer.so because unable to locate the objcopy executable for the x86_64 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86_64\libgdx.so because unable to locate the objcopy executable for the x86_64 ABI.
Unable to extract native debug metadata from C:\Users\Praveen\AppData\Local\Temp\AndB785.tmp\app\build\intermediates\merged_native_libs\release\out\lib\x86_64\libRuntimeNative.so because unable to locate the objcopy executable for the x86_64 ABI.> Task :app:bundleReleaseResources
> Task :app:processReleaseResources> Task :app:compileReleaseJavaWithJavac
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.> Task :app:dexBuilderRelease
> Task :app:mergeDexRelease
> Task :app:buildReleasePreBundle
> Task :app:packageReleaseBundle
> Task :app:signReleaseBundle FAILEDFAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:signReleaseBundle'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.FinalizeBundleTask$BundleToolRunnable
> java.lang.OutOfMemoryError (no error message)* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at Please login to see this link.
BUILD FAILED in 52s
36 actionable tasks: 36 executed -
for this
java.lang.OutOfMemoryError (no error message)
go to data/runtime/android and find RuntimeAndroid.zip
open it and uncomment this line #org.gradle.jvmargs=-Xmx1536m (near the bottom) by removing the # char.
then save the file and update the zip, you should be Ok to build.
if you have this installed in Program file (x86) you may need to do this outside this protected folder.
-
A new expression to get the number of animation frames / last animation index would be extremely helpful for lots of use cases
-
A new expression to get the number of animation frames / last animation index would be extremely helpful for lots of use cases
Building on top of that, it would also be quite nice to have a condition to check whether or not an object has any animation frames stored in one of its 32 directions.
For example:Code* Active1: Direction 8 has frames Select Direction Number 8 Button : Enable * Active1: NOT Direction 8 has frames Select Direction Number 8 Button : Disable
It's not essential of course, but there are some use cases I can think of that would be very useful when making various editor tools for my game.
-
A new expression to get the number of animation frames / last animation index would be extremely helpful for lots of use cases
Try Animation Info object
-
Fernando here's a mfa/apk that should contain the bugs I was talking about on Android runtime... And here's the list of problems:
-Samples (specially wave) may play all distorted on some devices (I guess older ones) the first time it plays.
-Loop Samples may cut off or get a weird distortion for a sec randomly (I'm not sure what causes it, but I've seen it happen)
-Test Position will not consider "Fit inside and adjust window size", meaning objects will get destroyed if it gets to the extra area.
-All Frame expressions to get X/Y coordinate of visible edges also will not consider "Fit inside and adjust window size", meaning these cannot be used to make responsible interfaces the way it is.Here's the mfa/apk, I suggest testing in more than one device, specially a older one.
Please login to see this link.Fortunately it seems like the problem I was having a while ago with my SMW camera remake seems to work properly on Android now, but I'll have to do some more testing.
Another one for Windows: having a button then switching to a frame with more buttons (in checkbox mode for example) with Transparent enabled will not only show a black rectangle in its place but will also show the button for the previous frame within it.
-
for this
java.lang.OutOfMemoryError (no error message)
go to data/runtime/android and find RuntimeAndroid.zip
open it and uncomment this line #org.gradle.jvmargs=-Xmx1536m (near the bottom) by removing the # char.
then save the file and update the zip, you should be Ok to build.
if you have this installed in Program file (x86) you may need to do this outside this protected folder.
From : gradle.properties?
If yes, then I then Remove line #org.gradle.jvmargs=-Xmx1536m (near the bottom) by removing the # char.
Problem not resolve.
Please login to see this link.
Same problem in steam version.
Steam verson install in E
When using build 293.1, app (application.aab) build. -
how big is this application, seems more than 400 MB, you might try using 1916m instead of 1536m
this line allow you to reserve memory for the building process, but you have to have at least 4 GB of memory in your PC.
====================
you shoudl try 293.6 in beta
-
The "Display as a Sprite" option of the subapp object won't work. It's could be nice to be able to add subapp on frame preserving alpha and that can be placed rear of some other objects.
-
Right, so a friend and me tested the 'bugs' I told about Android, also in iOS.
So the samples are all messed up on iOS (not only on the first time it plays, wave sounds, depends on the file tho), checkboxes didn't showed any text (but I guess it was because of the size of it), the expressions for screen edges behaves the same, so I guess it was supposed to work like this.But, on Windows runtime if you manually resize it adjusting window size, the expressions for the edges of the frame and Test position reflect the change, which is odd, I was expecting this on mobile.
And I noticed that resizing the frame area will make so the expressions and Test position adjust accordingly, but then this means mobile needs a way to get the visible edge of the screen that doesn't rely on the frame size.
Cause "Fit inside and adjust window size" is something exclusive for it (honestly would be nice on Windows as well tho), so expressions to get the visible edges that consider the "adjust window size" part would help resizing the frame accordingly so Test Position wouldn't fail.Here's a video of the sound glitching out on iOS, please reduce your volume cause it will be loud and distorted lol
Please login to see this link.
-
From : gradle.properties?
If yes, then I then Remove line #org.gradle.jvmargs=-Xmx1536m (near the bottom) by removing the # char.
Problem not resolve.
Please login to see this link.
Same problem in steam version.
Steam verson install in E
When using build 293.1, app (application.aab) build.When using build 293.1, no issues (build aab and apk properly).
293.6 buld apk properly but aab not build -
actual version have latest changes in gradle plugins, google plugins and latest framework for android10+, they require more memory.
during the internal testing never require more than 1596m, I knew a specific game did required 1916m, but more than that not sure will depends on your PC.
But comparing 293.1 to 293.2+ is not possible and should not be a rule since new version requirements.
-
how big is this application, seems more than 400 MB, you might try using 1916m instead of 1536m
this line allow you to reserve memory for the building process, but you have to have at least 4 GB of memory in your PC.
====================
you shoudl try 293.6 in beta
Processor Intale Core i7-6500U @ 2.50GHz 2.60 GHz
Installed Ram 16.0 GB (15.9 GB usable)(1) Image Size 63.4 MB (embed external files) (in Binary data)
(2) apk size buld by 293.6 112 MB
(3) aab size 106 MB buld y 293.1
(4) mfa size 1.85 MB (Total Frame 5) -
please set to 2048m and see if it works, if not the only thing that comes to my mind is to delete the .gradle folder inside your user folder, of course the first time will take more time to build since have to download all needed framework, libs, and plugins
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!