Build 292.7 - 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.
    Quote from Dobermann

    Please login to see this attachment.

    Why does the "timer equals" events Don't show in green? They are triggered only once, right? The old "timer equals" of my app are still in green but the new one i add are black.

    Probably it was a mistake in an old build (not sure which one) and this condition incorrectly contains a flag that says it's a triggered condition. This condition is not triggered, it's a normal condition, evaluated every loop.

    Hi Yves,
    Sorry to bother, but could you let me know if the issues with the Surface object described in my previous post are reproducible, and whether there are any plans to update the object to address them? My tool depends on using many instances of this object, and after the update my application is a lot slower than it used to be. I could possibly rewrite it without using the alpha-related actions at all, but it would be a relatively big workaround. I really hope I don't end up switching back to MMF2 because of this.

    Quote from PkR

    Hi Yves,
    Sorry to bother, but could you let me know if the issues with the Surface object described in my previous post are reproducible, and whether there are any plans to update the object to address them? My tool depends on using many instances of this object, and after the update my application is a lot slower than it used to be. I could possibly rewrite it without using the alpha-related actions at all, but it would be a relatively big workaround. I really hope I don't end up switching back to MMF2 because of this.

    I can reproduce the issue, with both the current version of Surface and the previous one. I can't say why this happens until I've more time to take a look, I'm too busy right now. Maybe next week... What's the last modification date of surface.mfx in your copy of MMF2? (I guess it's the one you used to build surface_fast.exe?)

    Hi Yves,
    Here's the surface.mfx file from my pre-update extensions folder.
    Please login to see this attachment.
    Now that you mention it, I remember what happened when I ran into these problems back in 2016. I originally started my project in MMF2 and upgraded to Fusion 2.5 mid-development. With the version of Surface included with Fusion 2.5 I ran into the crash issue (the one you fixed a couple days ago) so I had to replace "Draw a line on the alpha channel" with "Draw a rectangle on the alpha channel". That worked, but then the performance issue showed up. I ended up using the MMF2 version of the extension, which still has the "Draw a line on the alpha channel" crash issue in Fusion 2.5 (but not in MMF2), but other alpha channel functions work a lot faster in it.
    So that's the full story. I guess something was changed in the extension during the 2.5 transition that massively degraded alpha channel actions' performance.

    potential bugs/issues:

    Android Runtime issue:
    I move an Active object or Layer repeatedly into one direction and at some point something gets messed up with my position related events on the device.
    (with my project it took 9-10 minutes to see the issue on a test device - I can provide a .mfa example per PM, if I get the permission)

    questionable restriction in Event Editor:
    In the Create Object window for X and Y, it seems that you can't enter a value higher than 32768(when entering a higher value it jumps back to a lower one).

    some minor cosmetic things:
    - spelling error in Frame Runtime options "Direct3D: don't erase background if the frame has an efffect."
    - two things in the image below:
    (2. is not important/debatable, but eventually you could fix the confusing Direction 24 preview image under 1.)

    Quote from Fernando

    Please post a small mfa that reproduce the issue you mention for me ot try


    OK, my fault. I forgot that staff member PM are no longer supported.
    I post the mfa example in the Jason Citron app, if you don't mind.

    Currently working on ... [SIGPIC][/SIGPIC] ... a Puzzle Platformer

    Is it possible to make the divider in the Alterable Values properties (a) remember its last position, and/or (b) start off further to the right by default? (as in the right of the screenshot)

    At the moment, it defaults to how it looks on the left of the screenshot. You can move it manually, but it eventually goes back to its default (I think after restarting Fusion?).

    Since most users will mainly have zeroes, integers, or simple floats (eg. 20.75) in the right-column, the default spacing gives that column much more room than is typically needed. On the other hand, the names in the left column are much more likely to run out of room.

    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.

    To be able to organize global values and strings into folders, or to be able to re-organize them etc and access them easily. +1

    What about adding comments to values too? (So that we know what a value does at a glance)

    Quote from Volnaiskra

    Is it possible to make the divider in the Alterable Values properties (a) remember its last position, and/or (b) start off further to the right by default? (as in the right of the screenshot)

    At the moment, it defaults to how it looks on the left of the screenshot. You can move it manually, but it eventually goes back to its default (I think after restarting Fusion?).

    In the build 292.8 the divider will remember its last position in each tab after restarting Fusion.

Participate now!

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

Register Yourself Login