Build 295.10 - Release Version

Quote from Fernando

There is a problem with iOS simulators when running some OpenGL commands; for you to know, using simulator version 17.2 for iPhone 15 pro seems ok, but 17.4 or 17.5 fails. here are more details of what is happening to you

Please login to see this link.

Thanks for the information!
By changing the simulator version to 17.2, the problem is no longer present.

When you add a new condition, you have three ways to view the objects.

What is the use of the third view compared to the second?
The icon and text are the same size.

In the third view, there is a lot of space on the right.
So I thought: could the icon and text be made larger in that view?

Please login to see this attachment.

Would it be possible to add the "do not include at build time" option to layers? This would be handy for storing various guide objects that help you design a level in edit-time. Or for storing debugging/godmode objects that you can easily turn on and off depending on whether you are testing a level or building it for the public.

Also, it would be helpful if a layer's Blend Coefficient could be displayed in the Frame Editor (If "Use Direct3D in editor for Direct3D applications" is checked in preferences, of course). This would allow a sort of 'Light Table' functionality where a guide layer can be overlaid over the other layers to help with positioning and lining things up.

Currently, the Blending Coefficient seems to be utilised in the Frame Editor for individual active objects, but not for layers.

Quote from fnkycoldmadeanr

Feature Request:
When double clicking an object icon on a condition in the list editor you can replace the object with another of object of the same class.

Please login to see this attachment.

I was wondering if this function would be easily added to actions in the list editor?

Would this be difficult to add Yves?

Quote from Yves

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.

Display More

Hi Yves,

Are you guys ready with this version of CF? Because we are stuck on updating our apps on Google Play due to old version of Gradle 7.4.2:

Can we do something from our side in upgrading the Gradle from inside the Fusion?

The error is:

This Android Gradle plugin (7.4.2) was tested up to compileSdk = 33

Thank you in advance!

Best,
Mentor.

Feature Suggestion:

DPIScale should return a DPI value regardless of if `DPI aware` is enabled.

I have an object with some values,strings and/or flags.And I made a copy of that object and changing at least one of the values,strings and/or flags with an event.

Then i made another event that triggers when some of the alterable items matching with the conditions for the object (first or copied).

When the one of the first or copied object matches the conditions the event is triggering for that object (first or copied).

Because of i also used "one action when event loops" condition, that event is working on one of that objects(first or copied).

But it's not working on the other copies even their alterable items are matching with the conditions.

According to my theory,one of the copies of that object's alterable items are already matching with the conditions and because of i used "one action when event loops" condition,the event is not triggers for the other copies of the object.

So I making a request to make that event work for each copy of the object when their alterable items are matches with the conditions even the event has "one action when event loops" condition

The example event i'm talking about:

*alterable value A(active) = 1

*alterable string A(active) = "something"

*Only one action when event loops

-switch flag 1 to on

Bug.

Select a comment, press the end key twice, and use the menu or hotkey to create a new action:

Please login to see this picture.

Ensure that this action relates to an object in the frame:

Please login to see this picture.

Of course, the action will never get created, since you can't create actions in comments. However, it still hangs around in the file in some way. If you try to delete this object now, you'll get a warning message:

Please login to see this picture.

These phantom 'actions' are evidently saved in the MFA, because if you save and reload the file, then try to delete the object again, you'll get the warning again. If you delete the comment, you'll no longer get the warning message.

I don't know how harmful these phantom actions are, but I accidentally created one in my project, and it gave me the heebie jeebies

I don't see any difference between of creating a regular event.

Can you tell or show me how are you even doing it?

And why is it harmful?

Quote from OyunKaosu

I don't see any difference between of creating a regular event.

Can you tell or show me how are you even doing it?

And why is it harmful?

Select a comment first. It will try to create the event inside the comment. It won't create any visible event at all, but the event will still be in there somewhere, invisibly. It will prevent you from deleting related objects. And possibly there might be other unintended consequences.

Quote from Volnaiskra

Select a comment first. It will try to create the event inside the comment. It won't create any visible event at all, but the event will still be in there somewhere, invisibly. It will prevent you from deleting related objects. And possibly there might be other unintended consequences.

I did it, and if the event appears, I don't have shortcuts, I did it from the menu.

Quote from TonyThunder

I did it, and if the event appears, I don't have shortcuts, I did it from the menu.

Sorry, maybe a typo there. I'm not sure what you mean. Do you mean that an event appeared?

oh sorry

I wanted to say that... the event appears

Oh, I see the problem.....

Select the comment, then press the end key twice, and then create an action (not a "line of event" like I wrongly showed in my first screenshot). The bug will reproduce this time.

Please login to see this picture.

I've mapped button #4 on my mouse to add an action, and I forgot that the macro I use for that automatically presses end twice before triggering the 'create action' shortcut. This is because Fusion's shortcut for creating an action only works if the Actions 'column' is highlighted (you can press home & end to move between the event/condition/action 'columns'). So automatically pressing end twice means that I can create an action with a single button press without needing to bother about selecting the right 'column' each time.

So I guess this is a bug that most users are unlikely to encounter (though more users should Please login to see this link. like this, because it's the bomb). I've fixed my original post with the correct instructions.

Feature Suggestion:

Set object visibility through the expression editor. If returned value is equal to 0, make object invisible, otherwise, make object visible.

Would it be possible to add an option for the Workspace Toolbar to prevent frames from unfolding (ie. the little "+" button becoming a "-" button) any time a new object is added in the Frame Editor? As soon as a frame unfolds it basically takes up the entire toolbar and hides all the other frames in the project. I find that whenever I want to navigate to a different frame using the Workspace Toolbar I routinely have to close all the little "-" boxes that have accrued since last time I used it.

Not sure where to post this:

Email notifications from the new forums are erratic. Sometimes I get a notification, sometimes I don't. For example, I've not received any notice in a few days, and when I accessed the forums now, there were 2 replies that should've triggered email notifications.

U get email notifications from a thread you have subscribed.You can subscribe a thread with the subscribe button,or while sending a post on a thread if the "subscribe thread" is open.

When you replace a sound, it isn't updated in the behaviors of an object.

Quote from droxon

When you replace a sound, it isn't updated in the behaviors of an object.

Close the behavior before replacing sound.