Fade in/out of frames and objects not working in Android APK build

On this matter,
I was thinking that a cool feature,
maybe after installing an exporter,
could be having some sort of warning on every action/condition prevented on that exporter,
like "crossed" small runtime symbols, or even just letters

let's say in the "Scale / angles" actions submenu:

Scale / angles >
set scale
set X scale
set Y scale
set angle (Ⱥ)

would mean that "set angle" action won't work in Android Exporter
(just a random example, I hope angles work well in Android! XD)

Could be really handy and prevent a lot of trial and error,
or looking everywere to find whatever is supported and what is not and keep this knowledge up-to-date.

I won't argue with you on it. I understand your frustration, I don't think your mannerism is rude.

From a technical point of view, MMF2/Fusion 2.5 was/is the base product. Always has been, was/is a PC publishing software thus transitions were programmed for the frames and objects. This was looooong before "exporters". Back in 2006, the word exporter was almost non-existent. Java/Flash were the first, then Smartphones became popular, so follow Android/iOS along with XNA for Xbox 360.

Whilst majority of features from MMF2/F2.5 were able to be compiled into the runtimes, unfortunately, some things like Frame Transitions had to take the back-bench. Needless to say, around 99% of the products core features are compatible with the exporters, only Frame Transitions and Shaders that aren't. Shaders aren't because D3D9 utilises DirectX shaders HLSL but all the other platforms are OpenGL based which means the shader system is not compatible as they want GLSL.

I know this won't ease your pain but I'm just trying to assure you, we all take pride in the product and bringing the best we can to the table on every occasion, but some things are just not possible, whatsoever.

I do hope you enjoy your poker trip and I hope you perform well Please take the time to reconsider, I'm sure you've found out up to now what a great product Fusion 2.5 is and I reiterate, don't let one thing knock your confidence. I've seen your videos and for a first project, it looks pretty sweet.

Use your own transition Robotica ! Be sure that Fusion choice is the best you made !
For me, i make games in weeks ! Unity is more complicated ! And ask more skill that you think !

So the gameplay of your game is not your transition ! I don't understand your position by making a pause in your work just because of this poor problem !
Use alpha blending properties to make fade in or out for objet. It is very simple and it work on every platform.

why not include d3d11 and opengl

Come on guys... Why is it that when somebody mentions a flaw in Fusion 2.5 they always get bashed?

People paid good money for this software and if there is a problem it should be looked at instead of being ridiculed.

Danny... You're a great friend of mine and a good guy, but an answer like that is unacceptable to me. Remember ClickTeam is a company you're part of and these are your customers. It's important to listen to their feedback and make changes where possible.

I've had too many good friends of mine leave this community due to not being heard/bashed by their issues with the software. I seriously don't want this to continue and thus why I wrote my blog post here: Please login to see this link.

It's time for ClickTeam to start listening to these people's feedback and do something about it or I'm gone. I have 3 projects that can't be finished by various issues I'm having and after the almost 2 years of development.. about 7 months worth of coding and the rest was waiting for bug fixes. THIS is a big issue.... Nothing to release means I'm not making back the money that I put towards the product and I'm losing money everyday on this.

I'm disappointed in this situation...

Honestly I can see why you're mad, but you have to realize that there is a very easy and simple fix if you just make your own fading transition that will take at most 5-6 lines of code. I understand that the transitions should work, but for now while Clickteam can try to fix it you can easily move ahead with your game on all platforms. I created an example of a custom fade transition for frames that will work on all platforms. Just copy the Black active and resize it to fit your screen, then copy the group code. You can change the speed of the transition with the +2/-2 in the semi-transparency code. If you want you can move the black active off screen and then position it at the start of frame so it doesn't conflict with you setting up your frame. Or you could put it on a separate layer above everything else and make the layer invisible while working.

If you want to fade other actives you could always add them to a qualifier and test it that way. Super simple. Just add this to your game and test it to make sure it works. Fix the conditions so it goes to next frame during your game.

Sumo has the right mind set, but also there should be a thread with a list of things that currently doesn't work in Fusion. With every issue there should be a work around until ClickTeam can fix the problems and when it's fixed the work around can be removed from it.

Could you maybe post a youtube vid, or better yet, an example file that illustrates your current different roadblocks. The people on this forum are really helpfull. And finding workarounds for such roadblocks could benefit us all, like the frame transition posted above.

Robotica I updated my .mfa file. Please take a look and see if it helps now. I added a qualifier group that will automatically add the fade transition to all objects in that group. It's super easy to add objects to that qualifier group. Select an object and look under the properties window. The second to last tab (window tab) there's a line that says qualifier. Click the edit button and add the "Dissolving" qualifier. If you ever want to have an object fade, just set the qualifier flag 0 ON.

In the example if you click on any of the colored diamonds, they will separately fade until they're invisible.

Qualifiers allows you to apply code to a bunch of objects, in this case the custom fade.

Quote from JHale

Danny... You're a great friend of mine and a good guy, but an answer like that is unacceptable to me. Remember ClickTeam is a company you're part of and these are your customers. It's important to listen to their feedback and make changes where possible.

JHale, I haven't bashed anybody and I certainly always listen to every bit of feedback that is thrown at us.

Let me be blunt because a lot of the time, Clickteam are too helpful and like to explain things technically that some people like to easily dismiss. I always ask the developers; is this possible? Is that possible? Of course, the core product is our main priority, it always has been before I got here and still is the number one priority. Do you think the programmers just say "That's not possible" because they cannot be bothered to do it?

Frame transitions are not possible in Android/iOS, Object transitions are possible in iOS, we will speak with Fernando upon his return and see if we can reflect this in Android to make the product better (thus listening to feedback). Put bluntly, Frame Transitions are not possible to integrate and won't be (For F2.5).

I am a little disappointed you think the likes of Me, Jeff and Simon and the programmers don't take feedback seriously. We love the product and continue to try and improve it at every angle.

With regards to your gripe with bugfixes you have reported, feel free to email me and I'll go through the list personally, just for you to see what we can resolve.

Quote from Danny

JHale, I haven't bashed anybody and I certainly always listen to every bit of feedback that is thrown at us.

Let me be blunt because a lot of the time, Clickteam are too helpful and like to explain things technically that some people like to easily dismiss. I always ask the developers; is this possible? Is that possible? Of course, the core product is our main priority, it always has been before I got here and still is the number one priority. Do you think the programmers just say "That's not possible" because they cannot be bothered to do it?

Frame transitions are not possible in Android/iOS, Object transitions are possible in iOS, we will speak with Fernando upon his return and see if we can reflect this in Android to make the product better (thus listening to feedback). Put bluntly, Frame Transitions are not possible to integrate and won't be (For F2.5).

I am a little disappointed you think the likes of Me, Jeff and Simon and the programmers don't take feedback seriously. We love the product and continue to try and improve it at every angle.

Danny.. You're not getting the point of what I'm saying.. I know you guys work hard to do bug fixes to get things going. I understand the situation of what you guys are going through, but you need to really understand the customer of the pain their going through. These people are spending countless hours with your software thinking that what they see on the Window runtime should be working on all exporters. There are extensions in the extension manager and even extensions your company claims that work for these exporters, but they are not working like they should. Same goes with some features. There are ways to solve this all if there was a thread that states what's not working with the work arounds to get it all going. Don't you DARE think that I'm bashing you or the software, because if I was I wouldn't have bought ALL your products! I support your company and even supported some extensions that some of your customers make. I'm just explaining what I'm going through including some other users in this community that has the same problems as I do. There are ways to fix these problems instead of ticking off people that bought it.

Here's a great example of what I'm talking about..

"Midway through Robotica's development he wanted to release his game for android and so he bought the android exporter. Little did he know that transitions was not working for Android and when he found out he posted this thread of his disappointment. With the countless of hours and days of him coding his game he has to go in and redo lots of code he worked hard on. Which leads to time wasted and money going down the drain."

How does this get solved?

Is transitions possible with the Android exporter? No right?

So let's figure out why he didn't know that transitions didn't work... Oh that's right! There isn't a sticky thread in this forum that states the problems and workarounds that are not possible or needs fixing! So instead before anyone uses anything in Fusion they have to hunt and search the forums to make sure every extension and feature is working properly! (Which could take hours to do)

We need a sticky thread here or something, because we are diving into this software not knowing what is going to happen midway through development. It's like a guessing game... We hope something will work or while new members are in the dark on it they purchase the product without knowing any of this. This isn't a good thing at all and is frustrating to say the least.

Then you have some community members that have left due to Clickteam thinking they're being bashed, but in reality they are not and are just frustrated over the same situation I mentioned above. This is an on going loop with ClickTeam and it's community.... People get banned, other people that see the frustration call them trolls, and so forth. THIS NEED TO BE STOPPED!

Quote

We need a sticky thread here or something, because we are diving into this software not knowing what is going to happen midway through development. It's like a guessing game...

I'm really new to exporters,
just bought a couple some weeks ago on summer sale, and I confirm I feel this to be a problem.

I suggested an idea a couple of posts ago, don't know if this (or whatever) could be considered useful and/or doable.
(putting some sort of warning icon on prevented commands, so that one would know for sure what not-to-do while developing)
This anyway would serve only for people who already bought the exporter.

Before (or after?) buying I recall finding a PDF depicting general limitations for HTML5 and Android exporter on the clickteam website,
maybe this paper could be stressed more and be constantly updated (maybe it already is)?
A single solid source for this material would be really useful both for owners and for people interested in buying.
Digging the forum for all answers to questions he still don't know he would better ask, is a daunting task XD

Anyway, I appreciate exporters being there, even if still not perfect.
Maybe some little effort to join needs of both sides could make everyone happy

Quote from Robotica

I'm just gonna quote myself again... because this is pretty much the point...

"I used to do video editing back in the day... can you imagine how bad it would be if the video editing software didn't show transitions in your rendered video as you had them in your project? How crazy would that be? Right???"

I can feel your pain.
I hope you will find acceptable solutions to this situation.

But on this specific point, I think that would have been LOT worse for a video editing tool not supporting transitions (a key-feature every video editor uses)
than for a different scoped software like Clickteam products are (transitions being a side-feature, many user don't use it at all :()