By default it will calculate using only integers (as long all values involved are also integers).
There's a crashy bug related to child events becoming active when undoing turning their parent events inactive, trying to run the app will crash Fusion, I wonder if saving a file in this state could lead to corruption...
Basically the parent keeps inactive with child events active. I'll see if I can list steps to get this glitch...
The Ctrl-F hotkey for "find" seems to be hardcoded. Removing it from keyboard settings doesn't prevent it from still working. Apropos, it would be nice to also get the ability to remap "Find All" (including to Ctrl-F).
I don't know if this is related to this beta or not, but I was getting a Crash To Desktop when I ran my MFA with R293.5. The MFA worked fine the first few times I ran it in 293.5 (several days ago), but then was crashing on launch all day yesterday. I still had the problem when I reverted to R293.1 yesterday. But today the problem is (for now) gone. Like I said, I don't know if the problem is related to the beta or not, or if it's purely related to my system. But I've got Event Viewer details of it in case it helps. I posted this on another thread, but I'll repost here:
This has started happening to me (again) as well. Running my MFA just crashes to desktop. It's probably not antivirus (I use ESET NOD32, but this happens even when I disable it). I guess it's probably not Windows corruption either, as I've very recently done a fresh install of Windows. Yves, there's no point me sending you my file, as it's basically the same file I sent you last time. I'm using R293.5
Here's what Windows Event Viewer says. I believe the exception code means it's a Memory Access Violation
Faulting application name: edrt.exe, version: 3.0.293.5, time stamp: 0x60edc78b
Faulting module name: ntdll.dll, version: 10.0.19041.1110, time stamp: 0x8a32a22a
Exception code: 0xc0000005
Fault offset: 0x00048215
Faulting process ID: 0x3b30
Faulting application start time: 0x01d7835a9543a104
Faulting application path: G:\SteamLibrary\steamapps\common\Clickteam Fusion 2.5\Data\Runtime\Unicode\edrt.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 021eb732-5d52-4083-b73b-a6151eeb790f
Faulting package full name:
Faulting package-relative application ID:
Yves, I know I ask for too much but... Could we please get a Error/Warning/messages log toolbar someday? (It could be a 2.5+ exclusive feature)
I mean, it's something to replace that popup that opens a .txt file and bring attention to issues that isn't resolved, cause constant popups with buttons when you know the issue already can be annoying...
I know some popups have a "Don't show again" checkbox, but that's even worse: once you check that you'll never know about the problems ever again, on any mfa!
It could show stuff in a line, double clicking the line could open the usual txt file with more details about.
It could be color coded, perhaps could bring attention to other stuff found on the project, like bad objects, shortcuts leading to non-existing objects, even that problem of deleting a object that is created through events that can cause corruption...
(if we can't fix it, at least warn the users, cause I still see people doing that and getting corrupt mfas...)
I think it would be a fantastic addition.
In the future it could display stuff like performance hogs, optimization tips, etc
I found this strange layer related bug, it appears to not happen with Direct3D11 (NaitorStudios tested it on the discord server)
Everything is explained in the mfa:
Thanks for all your hard work Yves!
Sorry for double posting, I can't edit my any of my posts.
I recently been having lots of frame editor graphical problems, so can we (if possible) have a new refresh button work in similar way of zooming in/out as it fixes the graphical glitches
Why does it exit when you open an MFA file and are not sure when you accidentally exit the program, or when you open an event that cannot be editedAttachment 30375
Quick update: build 293.6 is available.
did you get a chance to look at the object selection/scoping bug I found? it seems really strange to me at least :)
What was this, please? I released an update on 293.5 for Android that uses multi-touch, is this something I need to worry about?
Android: fix in Multiple Touch object, not behaving like the PC version.
If you are not using multi touch true conditions as not first event then test your application with new version. If only multi touch conditions as first event nothing to worry about it
Found another bug with child events!
Seems the old bug (I think?) with just having a "break" action as the only action in a child event does not work when running as exe. (It works when running from editor)
I've isolated and made an example, this does not work for me at least using the latest build (293.6)
@SirEatAlot basically a lone Break works the same as a call to a non-existent loop, it's just disabled and discarded during building build.
It simply thinks it has no actions. Of course this shouldn't work this way, but that's the explanation.
Same happens on events that only has Debugger actions for example.
That's the point, it shouldn't.
Since it's isn't doing anything to any object, variable or option, it gets deleted for "Optimization purposes".
Probably just a overlook, Fusion by defaults removes any "blank" event during building.
What I end up doing now is insert "fake" actions that sets a temp global value to 0 just to ensure the break events actually triggers X)
calling a loop that doesn't exist or a loop with no actions now causes the application to crash >__<
Bug on Android: Text isn't showing up when using Button is Checkbox mode, probably happens to some other modes as well.
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.
1.- not to use system fonts
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...
Attachment 30386Why 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.
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 http://developer.android.com/r/tools...end-of-service 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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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\ap p\build\intermediates\merged_native_libs\release\o ut\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 FAILED
FAILURE: 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.FinalizeBu ndleTask$BundleToolRunnable
> java.lang.OutOfMemoryError (no error message)
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 https://help.gradle.org
BUILD FAILED in 52s
36 actionable tasks: 36 executed
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
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.Code:
* Active1: Direction 8 has frames
Select Direction Number 8 Button : Enable
* Active1: NOT Direction 8 has frames
Select Direction Number 8 Button : Disable
@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.
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.
If yes, then I then Remove line #org.gradle.jvmargs=-Xmx1536m (near the bottom) by removing the # char.
Problem not resolve.
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
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.
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