Thank you.
We have already reported to the kaspersky side that it was a false positive and we are in the process of getting them to respond.
Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
Login or registerTo get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
Open a TicketThank you.
We have already reported to the kaspersky side that it was a false positive and we are in the process of getting them to respond.
In case this is fixable: With the layer object if you have the condition:
+ Layer object: Global Value A Below Global Value B?[INDENT] Active : Set effect to "MonoChrome Shader Example" //doesn't matter what's here, this is just as an example[/INDENT]
And there is a chance that either Global Value A or B is null - the .exe will crash.
(It's easily fixed by giving them a dummy value so they're never null but it took me a while to figure out why the .exe was crashing all the time...)
Windows Defender appointing Trojan during Clickteam Fusion 292.29 update.
Please login to see this attachment.
Windows Defender appointing Trojan during Clickteam Fusion 292.29 update.
Please login to see this attachment.
Don't worry about this one. This file was part of the old "compress runtime" option that was removed, so actually Windows Defender displays the false positive when the update patch removes the file. Delete it (in the list of actions they show you).
McAfee's real time scanner will not allow the building of a windows exe application. I can turn real time scanner off and it will build. But if McAfee's real time scanner is on, the built exe cannot be run. McAfee will automatically quarantine it. This occurs for any windows exe program made with the build 292.29. I tried just creating a bare bones window and that occurred.
McAfee's real time scanner will not allow the building of a windows exe application. I can turn real time scanner off and it will build. But if McAfee's real time scanner is on, the built exe cannot be run. McAfee will automatically quarantine it. This occurs for any windows exe program made with the build 292.29. I tried just creating a bare bones window and that occurred.
We've sent them runtime files and example apps and asked them to fix it last week. No answer except an automatic confirmation message. I suggest that you submit them built apps as false positive via the interface of your AV and mention they were made with Clickteam Fusion 2.5, perhaps with more samples they can fix it faster.
If this issue continues with the next version of the runtime we'll have to find a more drastic solution and modify the building process.
Unfortunately, there seems to be no way within the antivirus software to submit this. I had to go to their site, and find instructions for submitting a false positive by email. I have received no confirmation email, but it's Sunday, so . . . .
Hi I've discovered a bug in the current version of Fusion. The "Handle background collisions even out of window" checkbox in the Frame Properties menu is actually backward. Checking it actually turns it off and unchecking it turns it on. The process of discovering this was very frustrating.
Hi I've discovered a bug in the current version of Fusion. The "Handle background collisions even out of window" checkbox in the Frame Properties menu is actually backward. Checking it actually turns it off and unchecking it turns it on. The process of discovering this was very frustrating.
Sorry I can't reproduce this issue, can you post an example please?
Here you go, try this. The 2nd and 3rd frames show the bug. Please login to see this link.
Here you go, try this. The 2nd and 3rd frames show the bug. Please login to see this link.
Ah, you misunderstood how this option works.
This option works for the objects that are within the bounds of the frame, your objects are out of the frame. It was made typically for scrolling apps where the frame is larger than the window.
It's not intended to be used as in your example for objects that are out of the frame. I'm not sure why it works in the third frame but this is probably a side effect, I'll need to check it.
Check the MFA attached to this post to see what it was made for.
Also, note that this option is only for the layer #1, the only layer that contains a global collision mask, the global collision mask was made originally when there was a single layer and this option was made to limit the size of the collision mask. It's ignored in the other layers (= on these layers collisions are always checked), so if you really need backdrop collisions to work in your example you can move the objects to layer #2.
Hello!
I'm trying to use a lot Child events, it's a very good features, saddly it could be a real mess sometimes when you have a lot of child events... It could be really awesome to have something like that to see wich parents are the same, and to enlarge/reduce some parts of the code :
Please login to see this attachment.
I don't know if it's possible easily.
Hello!
I'm trying to use a lot Child events, it's a very good features, saddly it could be a real mess sometimes when you have a lot of child events... It could be really awesome to have something like that to see wich parents are the same, and to enlarge/reduce some parts of the code :Please login to see this attachment.
I don't know if it's possible easily.
It's in the wish list, but I'm not sure we'll have time to do it in 2.5, it's not a quick task.
Hello!
Please login to see this attachment.
That's actually a really nice way of displaying it with the pseudo-parenthesis.
Let's cross finger to have it in 2.5
Found a bug, it's not the first time I see it, pretty often since 6 months.
When I'm using each loop, if I use a Fast loop inside and put it at the beginning, and if this fastloop call another fastloop, it will select all Object during the Each Loop, instead of only one.
But if I put the first fastloop at the end, it will be good.
For exemple :
Please login to see this attachment.
This will delete all "Ennemi" object, even if Action="Reflechis" for only one.
Please login to see this attachment.
This will delete only one Ennemi, the one with Action="Reflechis".
Yes "Start Loop" affects the object selection, better not use it with other actions in the same event.
@Child Events: that is a very clever solution. But I would rather it be color coded. I have cases of maybe a dozen child events (some of which have a few child events of their own) which span multiple screens in the ELE. It would be very helpful to know when one ends and another begins. The indent is a nice start, but once you start putting them into groups, the indents become harder to read. Hopefully a solution can be found for 2.5.
You can try something like this, even if it's far from perfect.
Please login to see this attachment.
Would be possible to add the "Parallaxer object" to the UWP exporter?
[MENTION=9539]Crian[/MENTION] Microsoft already discontinued UWP, you can still build it, but there's really no benefit of using it, you can add the tile to exe games/apps without it, and Microsoft Store supports exe these days
I don't know about performance tho, never built anything with it...
Don’t have an account yet? Register yourself now and be a part of our community!
Almightyzentaco (Fusion 2.5 Tutorials)
Captain Quail (Firefly Tutorials)