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.

    This isn't a big problem, but thought I'd mention it. When opening the Create Object dialog, the search-as-you-type field remembers the previous search term, but doesn't honour it. This is different to other dialogs (eg. create object in Frame Editor) which remember the term and also honour it.

    1. Create new object
    2. Type search term:

    Please login to see this picture.

    3. Hit cancel
    4. Create a New Object again. Search term remains but no longer filters:

    Please login to see this picture.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

    Hmm if I remember well, one of the main reasons we can't flip objects using negative scale is because it breaks collision, right?
    If it just flip the image but keep the original collision mask, perhaps we could just have option to allow flipping, cause it wouldn't be a problem if the person was using embedded hitboxes.
    But, if it breaks collision entirely, perhaps a toggle to disable collision all together that would also enable negative scale for flipping could work, so people that use a paired object as hitbox wouldn't have any issues with it.

    Quote from piscesdreams

    +1 - I've been wanting nested folders for a long, long, long time.

    What do you mean? Fusion already has nested folders (I assumed nested folders just means putting folders inside folders inside folders, but I guess you mean something else? ).

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

    Quote from Volnaiskra

    Oh, never mind. I misunderstood, and thought you were both talking about event folders (groups) and the new event Explorer. Sorry.

    No worries. I'd love to see this for object organization, but would also love to see the ability to sort our Global/Alt Values and Strings - if nothing else, at least alphabetically. I assume this would cause conflicts when trying to refer to values/strings by index though.

    Please login to see this link.

    Quote from haoujey

    +1 too AND the abillity to move multiple objects in the same time. It's a pain to reorganize my objects after a few weeks working without putting each file in the good folder :(

    Hey, you can actually do it, select and drag multiple objects from file explorer to Frame's library toolbar :)
    Please login to see this attachment.

    Game/App developer, artist and a community contributor.
    You can support my work on: Please login to see this link.

    I really feel like we need a option to create a blank child event, it's specially useful when you are converting a non-plus project to use child events...
    I always have to create a child event with whatever condition (usualy vsync one) then delete it and replace with conditions of the event I'm converting...
    It can take a lot more time doing it like this

    Quote from NaitorStudios

    I really feel like we need a option to create a blank child event, it's specially useful when you are converting a non-plus project to use child events...
    I always have to create a child event with whatever condition (usualy vsync one) then delete it and replace with conditions of the event I'm converting...
    It can take a lot more time doing it like this

    Agreed. Though it's easy enough to get a good working solution with a macro. I have a button on my Stream Deck for it, but you could use autohotkey or any other macro program to do the same thing:

    Please login to see this picture.

    As you can see in the gif, I can create an empty new child event very fast. Even if Clickteam added an option for it in the menu, this would probably still be faster. This is the process I use:

    1. Right click on the event number that you want to be the parent (you must manually do this yourself)

    2. Hit your hotkey to activate the macro, which should simulate the following keypresses:
    down
    down
    down
    enter
    enter
    down
    enter
    down
    enter
    delete

    This will create a new child event with the "always" condition, then immediately delete it. It works great in the Event List Editor; I'm not sure if the exact same keypress sequence would work in the Event Editor, as I don't use it.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

    Quote from NaitorStudios

    Select any event by the number, hold ctrl+alt and press up or down, it will create a huge blank space on top of the eventsheet

    This doesn't happen on the Event List Editor, but interestingly, the middle-click problem I reported earlier (which doesn't occur on the Event Editor) produces a gap of almost identical height. I wonder if the two bugs are related.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

    Talking about getting a option to add a blank child event, would also be nice to have the options on the Insert menu up above, and of course these too: "Add new child event" and "Insert new parent event".
    Also feel like "Edit the actions" should be on Edit menu as well...
    I'm talking about these cause if these are added there we can assign a shortcut, would make it a lot quicker to do it without using the mouse.

    Hi! I'm having the same issue. I can't build signed .aab apps, I don't know why. It tells me this:

    Starting a Gradle Daemon (subsequent builds will be faster)
    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 'AndEC9B.tmp', project ':app'
    Warning: Mapping new ns Please login to see this link. to old ns Please login to see this link.
    Warning: Mapping new ns Please login to see this link. to old ns Please login to see this link.
    Warning: Mapping new ns Please login to see this link. to old ns Please login to see this link.
    Warning: Mapping new ns Please login to see this link. to old ns Please login to see this link.
    Warning: Mapping new ns Please login to see this link. to old ns Please login to see this link.
    > 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:mergeReleaseResources
    > Task :app:checkReleaseDuplicateClasses
    > Task :app:compileReleaseAidl NO-SOURCE
    > Task :app:generateReleaseBuildConfig
    > Task :app:javaPreCompileRelease
    > Task :app:checkReleaseAarMetadata
    > Task :app:mergeReleaseShaders
    > Task :app:compileReleaseShaders NO-SOURCE
    > Task :app:generateReleaseAssets UP-TO-DATE
    > Task :app:mergeReleaseAssets
    > Task :app:processReleaseJavaRes NO-SOURCE
    > Task :app:processReleaseManifestForPackage
    > Task :app:desugarReleaseFileDependencies
    > Task :app:mergeReleaseJavaResource
    > Task :app:bundleReleaseResources
    > Task :app:processReleaseResources
    > Task :app:mergeExtDexRelease

    > 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:mergeReleaseJniLibFolders
    > 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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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\Manuel\AppData\Local\Temp\AndEC9B.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: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.FinalizeBundleTask$BundleToolRunnable
    > Java heap space

    * 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 3m 15s
    36 actionable tasks: 36 executed

    If I don't build the app on release mode, then it builds it with no problem.
    I tried changing the org.gradle.jvmargs=-Xmx1536m, but it didn't work either, it gave the error "could not reserve enough space for object heap clickteam". Does anybody knows how to solve this?

    your error is : > Java heap space

    as you mention here follow the recommendation given to Pradeep increase your virtual memory inside runtimeandroid.zip in teh file gradle.properties

    uncomment this line by removing teh # char near the bottom

    #org.gradle.jvmargs=-Xmx1536m

    set this to 1536,1916, 2048,4096 see what value fit your configuration, this is an issue with gradle deamon that doesn't set the right memory amount in all windows system

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    There's a bug in Window Control object where if you set frame width/height to a different aspect ratio with Adjust frame size ON it will just stretch the original image, while setting it to the same aspect ratio or even setting it to the monitor's resolution (even if it isn't the same aspect ratio) will work normally...
    I think somehow the Keep screen ratio is affecting it even when disabled.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login