Posts by Yves

Sorry for the delay. I've got a 4 TB SSD and have no problem with it. How much space is used and how much is free on yours? (I'll try to reproduce it with similar values, just in case...)

EDIT: ah, and what's the size of your patch?

Quote from YesNoYes

As the title says, in some cases, trying to reorganise some events in an existing project into this structure, occasionally causes a very nasty crash.

The point at which this occurs is when I try to run the application or frame, and the crash doesn't simply ANR the runtime, the runtime never even starts, and the Clickteam Fusion editor itself completely shuts down without so much as a warning, and is unable to restore the project when relaunched. In fact it launches as if nothing happened.

My project is so large, that it would be very tedious to try and isolate where exactly this happens to see if it's related to any events I have. In any case I don't think it matters, because on some blocks of code, it seems to work, but on others blocks of events, ones which seem to me to be completely unrelated to each other in the event list, it nonetheless causes this crash.

My only real question is, is any dev or anyone at all, aware of any known specific ways of eventing parent/child events, that could cause a total crash of the entire software, at the point when you try to run the application?

If its a case of a particular set of circumstances or event/group arrangements that could cause the crash (and I suspect it is), as my project is quite far along, I'd have make a decision of whether it's just better to avoid using them altogether.

Thanks in advance

Display More

Were you able to locate the problem? If possible could you send me the MFA and explain how to reproduce the problem? Thanks!

Quote from jimboboi

i know this is old but do you still possibly have this file?

Hmm, this file is now the official version, do you use this version? (the size of PatchMaker.exe is 718 552 bytes)

Quote from Fadzior

I tested the performance of various events in fusion, events for objects are executed even when there are none in the frame.

Behaviors are added to the frame events at build time (same for global events), so they are executed like normal events.

Une version béta intermédiaire permettant d'enlever ce warning a été postée ici: Please login to see this link.

+1: to reset the window size and positions just delete the sp2, wp2, wp3 and xh2 values.

What you should do:

1. Reinstall the latest update patch of Fusion (required if you installed a possibly old version of the Android exporter after the last update).

2. Make sure you've followed the installation instructions described in the Help (Distributing your app / Android) or in this thread: Please login to see this link.

Quote from Yves

The Steam version is now available as "beta version", i.e. to install it you need to suscribe to beta versions in the settings of Fusion in your Steam client, and enter the code x243TNkwZS1239

hey guys, the build 296 is almost completed here, we're just debugging it, so I'm not sure we can add new features at this point (I'll take a look at the option for the layer toolbar perhaps, though I remember I already thought about that and I was not convinced or thought he was not really intuitive - but that was a long time ago, maybe with fresh thoughts I'll change my mind). Here is the current change log from the moment (not complete, some things are still being tested and could / should be included when the new build is released):

- App properties: the "Unpacked EXE" option (Windows tab) is now selected by default for new applications. Reason: this option is the most appropriate as it avoids most of false positives from some anti-virus programs with unsigned applications.
- Output window (2.5+ DLC only): this new window displays messages when you build your application, for example warnings about missing objects, effects, actions, conditions, etc. This allows you to avoid always clicking OK in warning message boxes when you build your app, and may give useful information like unresolved group names. Note: 2 new options have been added to the preferences, to allow you to disable this window (and come back to normal warning message boxes) and to automatically display it when you build an application.
- Main menu: new Tile Vertically command.
- Preferences: a new option, in the Skin options, allows you to use button bitmaps from previous versions of Fusion (note: not suited for dark skin modes)
- Frame editor: layer window display refresh is now faster.
- Frame editor: Copy no longer marks the app as modified.
- Frame editor: auto-scroll in grid setup edit boxes.
- Frame editor: when you paste, or drag and drop, a global object that has the same name as a global object in the frame but is different, you now get a message that allows you either to keep the existing object or add a new one with an incremented name.
- Event editor: missing effects in events are now reported when you load a MFA.
- Event editor: the "Select group" dialog box now also allows you to enter the name of a group to activate or deactivate. This allows you to (de)activate groups in global events, an included frame or a behavior.
- Event editor: object icons in the global event editor are now updated from objects in base frame first.
- Event List editor: when you click an object's icon its properties are displayed in the property window.
- Event List editor: for a better readability, "Insert your new action" lines are now hidden for parent events without actions. A new "Add a new action" entry in the condition popup menu allows you to add new actions to these events.
- Expression editor: lists of expressions from extensions are now cached, to fix lags with the DarkScript object.
- Extension Manager: some extensions were incorrectly displayed as outdated, it's probably not 100% fixed but should be much better.
- Picture editor: import in box mode didn't work for images with alpha channel if the pixels outside the boxes are not transparent.
- Data Element editor: when you update the name of a sound, this name was not updated in global events.
- Properties: incorrect menu entry height in menu editor.
- Properties: a rare crash has been fixed.
- Properties: application not marked as modified after changing frame effect.
- Properties: leading and ending spaces in HTML5 project name and pathname are now automatically removed as they cause build issues.
- Build: building apps with behaviors is faster.
- Build: deadlock when building frames that include each other.
- Build: the build format has been slightly optimized (slightly better performance with loops and smaller apps).
- Build: fixed a couple of possible issues when files are larger than 4 Gb.
- All runtimes: the "Number of Objects" expression is replaced by 0 at build time if the object is not in the frame.
- Windows runtime: when selecting a mouse movement at runtime, the mouse cursor position was incorrect.
- Windows runtime: DX9 scaling rounding error in some cases. This was fixed by using a potentially slower DX function, but it doesn't seem to cause any performance issue.
- Windows runtime: DX11 pressing Alt+Enter could generate a black screen in some cases.
- Windows runtime: incorrect rounding for Click In Zone condition when used in conjunction with the "Resize display to fit window size" option.
- Windows runtime: if you set a mouse movement at runtime in some cases the mouse cursor didn't disappear.
- Windows runtime: incorrect mouse coordinates for stretched sprite sub-apps that don't ignore parent resize options.
- Windows runtime / Cursor object: now supports images with alpha channel and images with non-black transparent color.
- Windows runtime: in rare cases with non-Unicode extensions string comparison was incorrect.
- All runtimes: error in Pick Closest Object condition when objects are far away.
- All runtimes: error in "Number of selected objects" expressions of some extension objects in events with filtered OR conditions.
- All runtimes: better frame rate handling in physics movements.
- HTML5 runtime: Advanced Path Movement, bug in FindJourney.
- iOS/Mac runtimes: bug when ForEach loops are not at the first position of an event.
- iOS/Android runtimes: GDPR Object, now global, uses the latest ADMOB/UMP SDK 2+ for Android and 11.15+ for iOS.
- Android runtime: updated to use Gradle version 8.4. You need to use API 34 as build API, target Android 14 and use 5.0 as minimum version.
- Android runtime: crash in some cases in collisions after optimization in build 295.
- Android runtime: effects are now allowed in frames and layers.
- Android runtime: WebView2 Object, new action to set as desktop mode.
- Android runtime: removed use of Play Core libs (already in temporary beta released in the forum).
- Android runtime: Android Plus object, new expressions to get safe areas on top, bottom, left, and right, read the default country, and new condition to check if expansion is available.
- Android runtime: GPG Connect, new feature to check for revoked permission or if login is pending.
- Android runtime: GPG Cloud, new feature allowing it to post a file snapshot.
- Android runtime: Admob object updated with latest SDK version, removed play core dependencies, and initialization is now done in a separate thread as recommended by Google.
- Android runtime: Video Android object, now uses foreground service permission to comply with Android 14 target.
- Android runtime: Active Picture, File, Android Camera objects, now updated to handle target 14+.
- Android runtime: InApp object, now uses SDK version 6.1.0+.
- Android runtime: Android Manifest object, added <queries> to manifest, required for Android 10+, handles different intents, and allows an application to interact with another app.
- Android runtime: Android object, should now detect gamepads correctly.
- Android runtime: Android Splash Screen object, now tries to draw a full screen when possible.
- Android runtime: Location object, added a protection to avoid crashes on Android OS 9.
- Android runtime: new "Enable audio focus" property, allows your app to share sound with others.
- Android runtime: Screen Zoom object should be faster.

We've added a clear cache on the server, could you please retry? Fingers crossed.

Thanks! Simon suggests that you open the MS Edge browser, go to clickteam.com and then press Ctrl + F5 to do a hard cache reload.

Quote

What worked for me was to get Java directly from Please login to see this link..

We got support tickets from people who did that and got more issues with this, so IMHO better not do that (plus there are licensing issues with Oracle Java, iirc).

Hey guys, does it work now? or is it still broken?

Did you install (or reinstall) the Android exporter AFTER the latest Fusion update patch? If so, reinstall the latest update patch so that everything is up-to-date.

Weird... I've tried from an IP in the UK and in South Africa and it worked fine too...

Hmm, this issue was fixed a few days ago, it works fine for me.

Maybe some DNS info (or I don't know what) was not propagated everywhere yet and it will work soon for you...

It's "possible" but the change would affect a single object only, in the base frame, (unless it's a global object with editor synchronization options). This could be confusing from a user point of view.

When you copy events to the clipboard it also copies them as text, does this help? (hmm I think you need the 2.5+ DLC for this)

Hmm, a bit risky if the object you want to modify exists in several frames and is different in these frames, you would need to make sure the base frame is set to the one you want to modify...

I don't think you need to give MS credits as you don't redistribute DirectShow or DirectX, your app just uses the version that comes with Windows.