Build 293.1 - Release version

Right, so I believe this affects any extensions that use the same exact file selector File object uses. I've tried with File, Array, Edit Box, Common Dialog object, Rich Edit Object, all these are affected, probably a lot more, but for example, Picture or Active Picture are not affected cause they use a slightly different selector (custom?).
It's fairly straight forward, open the selector, don't even need to select a file, you can just cancel, after that edrt.exe will not close even if you click the X, it hides the window but keep running in the background, making Fusion unable to Run and Steam unable to reopen Fusion if it's closed (usually forced cause it will think Fusion is still running despite having Fusion itself closed), Steam will just say Fusion is still running and refuse to open it just because of edrt.exe running in the background.

Actually, I'm doing some tests here... I'm not even sure if this is a Fusion issue (I'm using Windows 10 Insider), it seems like actually any software after opening that standard file selector dialog once will not finish the process once closed D: (Notepad for example, tried on it and did the same, open a file selector once and it will not end the process after closing it)
I'll report this to Microsoft, I guess there's not much Fusion could do about it, UNLESS the Run button could also kill the runtime process before trying to execute it again, as a fail-safe feature...
But I've seen other users having this problem as well, I guess it must be a change on Windows or something if this do not happen on non-Insider Windows 10 versions...

I think you should take my suggestion and make the run button kill the runtime process (edrt.exe and the others) before launching it so the error never happens again... Since closing the application will reenable the Run button despite the process is still running in the background.
Cause if Microsoft don't fix this, soon they will merge Windows 10 Insider with the stable release, meaning this issue will affect all users...

Killing the runtimes processes when closing Fusion would also be a good idea...

The weakness of CF2.5, is that cannot select the opponent object when the same object collides with it.

I asked about how to get the direction of the opponent when the same object collides with it.

https://community.clickteam.com/threads/108578-Can-get-direction-of-opponent-object-when-collided-with-same-object

I wish will add the ability to select the opponent object when the same object collides with it.

I have a suggestion for mobile
I was thinking here, I think it would be nice if JPEG Image compression could make use of a JPEG alpha channel texture (generated during building) and use that so it wouldn't lose transparency and still have a nice reduction in size...
It could be a separated option, "JPEG with Alpha Channel", got me thinking of this since mobile is very limited in resources and there was this guy on the Discord server that has this massive almost 2gb high res game, I think this option would massively reduce the file size without the drawback of having no transparency...

Ah, noticed there's a small bug on Hi-Score object, "Ask for a player's name" does nothing on HTML5... (At least on Free version, possibly on any version tho)

This example shows physics collisions not working correctly at all for some reason

The physics in general don't work very good after the ( Optimizations in collision detection ) feature in some 2020 Fusion update

Hope this will be fixed in soon :)

MFA:
Attachment 30105

@Linky
Physics movement works like this; A collides with B - stop B = A will stop.
Non physics movement; A collides with B - stop A = A will stop.

Quote:

---

Originally Posted by Manuel

@Linky
Physics movement works like this; A collides with B - stop B = A will stop.
Non physics movement; A collides with B - stop A = A will stop.

---

Ah, yeah you are correct, sorry didn't focus on that too much and thought it's a bug xD

@Linky but better do it like; A collides with B - stop A and stop B, because otherwise it will give problem with duplicates, will only work on the first object and all dublictes will ignore collision for whatever reasen. Also never use backdrop object or physics ground object because the object scoping is not working correct with them, use only actives for everything physics related.