Posts by GKProduction

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.

    In fact, this problem appeared in previous builds of Fusion. When I try to open one of my mfas, Fusion crashes while opening. But, if I enable compatibility mode for Windows 7 in mmf2u.exe properties, there will be no crash.

    Unfortunately, this is all the information I can provide. I have nothing more to describe, only if I could provide the mfa file itself.

    UPD:
    This is an error log from Event Viewer:

    I found a bug in the event editor. You can select a folder if it is highlighted in the object selection and if you then press OK button or Enter:
    Please login to see this attachment.

    How to do this: Please login to see this link.

    Perhaps the bug also works in other places where such a window is called.

    not sure if i understand so you are using f8 to build an aab with expansion, can you give us full steps.


    ==========================

    tested with several application and device and can't reproduce this here.

    No no. I created a build with the specified type "AAB with expansion" using "File -> Build -> Application", then uploaded an aab file to Google Play. Then after installing this build from Google Play, there was a problem with a blank screen when starting the application.

    As for text pixelation, that's another issue. I believe both rendering options have their place, but this should be controlled separately from the smoothing mode.

    It would be very good to implement an option in the application properties that would affect whether the text is pixelated (when smoothing mode is disabled or always) or not.
    (Moreover, text pixelation would fit very well in work on other platforms, also on Windows)

    Please login to see this attachment.

    (Please don't think I'm demanding. :o It is a feature suggestion)

    Not sure i understand if you set smoothing uncheck this is the correct way opposite to smooth which will show also the text correctly.

    Are you trying to make a pixelated game with non pixelated text?

    Game styles are very different and even unexpected, so yes, I needed a regular (non-pixelated) text rendering, as it usually always looks in Fusion.
    But what I really wanted to report was not that pixelated text is wrong (although regular text is also needed), but about incorrect rendering behavior.

    Please excuse me for not being able to clearly explain the issue from the beginning. Let me explain what I am really trying to show. Follow these steps:
    1. Launch an application from the very beginning;

    First you see pixelated text. It became such from the start of the frame, because initially smoothing mode was disabled.

    2. Turn on the smoothing mode;

    The text will appear blurry, but it will still be pixelated.
    Please login to see this attachment.

    3. Tap on any string.

    The pressed string became smooth only when clicked, although it should have become so even earlier when changing smoothing mode.
    Please login to see this attachment.

    4. Go to the next frame without changing anything.

    All text is smooth from the frame start.

    5. Turn off the smoothing mode.

    Now (as well as after the fourth step) we observe the correct rendering of the text. This is how text has always been rendered in Fusion.
    Please login to see this attachment.

    6. Tap on any string.

    It only became pixelated when it was pressed, although it should have become pixelated only when changing smoothing mode.
    Please login to see this attachment.

    To describe the problem briefly, the display of the text is not updated when smoothing mode is changed, but when the text is changed.

    Hey Yves. Hope you get better soon. Stay healthy. ❤️*🩹

    I'll just leave a bug report in this thread.

    Actually, I made this example to demonstrate another bug, but I noticed another bug, which I will report here already.
    When moving to frame number 2, strings are not displayed correctly. They become the same size and use the wrong font. I have shown in the screenshot how the text looks in the frame editor, and how it is at run time.

    Screenshot: Please login to see this attachment.
    MFA: Please login to see this attachment.

    Fernando, I have prepared a small example for a visual demonstration of incorrect text rendering. Try to build mfa, then install and run it.

    Please login to see this attachment.

    During the test, try switching between frames, switching the smoothing mode and clicking on the strings to see the results.

    Previously, there was no pixelation of text. I think this should either be fixed or given control over it to the Fusion user.

    I installed the application from Google Play on a completely clean emulator (Android Studio Emulator), and still got a blank screen on startup. Could this be due to the fact that I am building in "AAB with expansion" format? Because to Google Play I always upload aab, not an apk.


    I just checked it by building an app into a simple AAB format (without extension expansion). The game now works!! I checked the launch on the device and on the emulator. No more blank screen.

    Fernando, maybe you forgot to do something with AAB Expansion?

    may i suggest remove the compatibility with Windows 7 and try again to see


    Already tried. No good results.

    By the way, for one of my testers, a game that was installed from an apk with the correct package name started without a gray screen, but the same build from Google Play still does not start.

    Maybe I can give you access to my internal testing so that you can try to run the build that was uploaded to Google Play?

    ah, and also post here what android studio you have and if you have the latest version of platform 34 (remember still in beta) and for your production case is better to use platform 33 and android 13 and finally is windows 10/11?

    I have Android Studio Electric Eel 2022.1.1 Patch 2, in mfa I used API 34, target version is 14, and my OS is Windows 11, but Fusion is set to Windows 7 compatibility mode, since one of my mfas does not open in normal mode, but that's another story...

    Using API 33 and target version 13 still gives same result. But also I clean Gradle cache and that didn't have any effect either. :(
    I also tried using File -> Invalidate Caches in Android Studio, turning off Fusion's compatibility mode and even completely reinstalling Fusion, but nothing helped. App still has empty gray screen after launch.

    Fernando, I have new information.

    Now the information that the application must be installed over the old one does not matter! After a complete uninstall and reinstall of the application, the problem still exists.

    I built the same application with different package names. The first package name is original and is used in Google Play, and the second package name is changed. Try to install and run each of these apk:

    Please login to see this link. (Original package name)
    Please login to see this link. (Edited package name)

    The problem may be related to the fact that the application has already been installed on the device before. You have never had this game installed, so you may not have this problem at startup, or it may still occur.

    Oh, I noticed, I still have old build after "Build and run"... But anyway this problem with blank canvas also have my testers after game update. I provide new builds through internal testing in Google Play Console, so the app has a signature and a new build number anyway.

    If Fusion is unable to update the build on my device for some reason, what else can I do to provide you with more information?

    I think I didn't explain myself well; please take the log while doing F8 from the fusion editor. This will show me when the app is ready by the fusion build process, and it is installed on your device; at that moment, the app is essential to log in to find out what your device says when it is being installed.

    The tests were carried out by having fusion 295.5 building the application and later the same application with 295.6. Obtain the log to verify what your device says when this process is executed.

    Log from "Build and launch" action:

    And this is more detailed log just in case (with arguments ActivityManager | Finsky | ru.gkproduction.mysterychamber2015classic):