Secret undocumented animation features

I cannot seem to reproduce it here... Do you have an .mfa of the issue by any chance?

Quote from FlipSwitchX

I figured it out. The point was that undocumented auto-features actually trip people up. Wish there was a repository for this stuff.

Sounds a lot like you made a mistake, figured it out, and won't admit it had nothing to do with an "undocumented feature." If this is a real issue, post an .mfa reproducing it so it can be addressed. You want there to be a repository for "this stuff" but you won't even actually share the undocumented feature you supposedly discovered.

Quote from CuddlyGoose

Sounds a lot like you made a mistake, figured it out, and won't admit it had nothing to do with an "undocumented feature." If this is a real issue, post an .mfa reproducing it so it can be addressed. You want there to be a repository for "this stuff" but you won't even actually share the undocumented feature you supposedly discovered.

[MENTION=20803]CuddlyGoose[/MENTION], I am not sure either if [MENTION=12312]FlipSwitchX[/MENTION] 's phrases are aggressive, which I doubt, or if you are.

Correct me if I am wrong but what he is refering to as undocumentedauto-feature is probably the standard behavior of Fusion which is not expected.

I myself has serious problems with properly coding animations and though I don't remember exactly why, I think it had something to do with the stop animation looping. It got me crazy. Then I found another post about it and figured it out (or maybe I got some help from here too). This was undocumented, unexpected and standard behaviour (i think thats what he means by saying auto-feature).

Also there is a possibility he doesnt even know what he did to fix it. Never the less, it would be nice to share the solution.

Quote from AftPeakTank

[MENTION=20803]CuddlyGoose[/MENTION], I am not sure either if [MENTION=12312]FlipSwitchX[/MENTION] 's phrases are aggressive, which I doubt, or if you are.

Correct me if I am wrong but what he is refering to as undocumentedauto-feature is probably the standard behavior of Fusion which is not expected.

I myself has serious problems with properly coding animations and though I don't remember exactly why, I think it had something to do with the stop animation looping. It got me crazy. Then I found another post about it and figured it out (or maybe I got some help from here too). This was undocumented, unexpected and standard behaviour (i think thats what he means by saying auto-feature).

Also there is a possibility he doesnt even know what he did to fix it. Never the less, it would be nice to share the solution.

It is unreasonable and unhelpful to complain about a problem without providing any evidence of the problem. Then when asked for the evidence, it is brushed off, and the complaint is repeated. This does not help anyone. This happens all too regularly in these forums. If the problem is real, then proof needs to be provided so it can be addressed. Otherwise, posts like these are counterproductive and quite unfair to the developers.

I'm not arguing that there aren't undocumented features or weird quirks with Fusion, but this posts reads like a user made a mistake and is refusing to acknowledge that while still placing the blame on Clickteam.

[MENTION=20803]CuddlyGoose[/MENTION] , I guess only [MENTION=12312]FlipSwitchX[/MENTION] can tell us what actually happened here. I am also curious to know what actually happened.

Quote from CuddlyGoose

It is unreasonable and unhelpful to complain about a problem without providing any evidence of the problem. Then when asked for the evidence, it is brushed off, and the complaint is repeated. This does not help anyone. This happens all too regularly in these forums. If the problem is real, then proof needs to be provided so it can be addressed. Otherwise, posts like these are counterproductive and quite unfair to the developers.

I'm not arguing that there aren't undocumented features or weird quirks with Fusion, but this posts reads like a user made a mistake and is refusing to acknowledge that while still placing the blame on Clickteam.

Ah the old "I didn't see it so it couldn't have happened" argument. People like you never fail to impress.

Stay on topic anyway. He addressed your first concern and expressed his point clearly - and its very understandable. Hidden features in fusion that seem to be undocumented. Fusion isn't exactly the most well-documented software and finding needed information isn't always easy. Not everyone has a deep understanding of Fusion and those that do still don't know everything. You can't expect a beginner or even intermediate user to have knowledge on something they have never encountered - especially if they didn't start with an older version of fusion/tgf/cnc/knp etc. where likelyhood of exposure to weird/unexplainable "quirks" or even bugs were a bit more likely.

C'mon guys, don't argue - it's Christmas X)

I think it'd be really great to have a repository of these secret undocumented animation features. It's a funny thing, the Clickteam animation system. It does a lot of stuff without you asking, and some of the time that's really helpful, and some of the time it's really unhelpful. But it is what it is, and it's definitely not going to change before F3 - even if Yves fully understands how it works, he's not going to change core code and risk breaking decades worth of MFAs.

So it'd be great to have a reference for how this stuff works somewhere. Maybe we can try here. I'll start, with what I know:

Appear: play when an object is first created
Disappear: plays when the object is destroyed. The object will only cease to be after the animation finishes
Stopped: plays when object is explicitly stopped with a "stop" action, but also if speed is 0 (this is the case with bouncing ball movement - not sure about other movements)
Walking: seems to play automatically when speed is at 1-74 (again, I've only tested with bouncing ball movement)
Running: seems to play automatically when speed is 75+ (again, I've only tested with bouncing ball movement)

Quote

even if Yves fully understands how it works

I wish I would understand it. I don't know very well this part.

Quote from FlipSwitchX

I figured it out. The point was that undocumented auto-features actually trip people up. Wish there was a repository for this stuff.

Sure but was this an "auto-feature" or a bug?

The way you describe it, I cannot fathom why this would be intended design. In my mind it sounds either like a limitation or some glitch rather than a feature. That is why I think an .mfa example would be very valuable to have. It also goes in spirit with what you are suggesting; adding such findings to a repository of information related to these oddities. Which I agree very much with, it's a good idea. However I seem to have a hard time following the directions in the original post so I cannot put your discovery to any good use yet.

Quote

Appear: play when an object is first created
Disappear: plays when the object is destroyed. The object will only cease to be after the animation finishes
Stopped: plays when object is explicitly stopped with a "stop" action, but also if speed is 0 (this is the case with bouncing ball movement - not sure about other movements)
Walking: seems to play automatically when speed is at 1-74 (again, I've only tested with bouncing ball movement)
Running: seems to play automatically when speed is 75+ (again, I've only tested with bouncing ball movement)

As far as I know you can change the speeds at which Walking / Running activate by changing the speed under direction options.

But you can't disable the built in animations and they will trigger ahead of any custom animations - this to me is a major flaw - because you sometimes need the movement for reasons the developers didn't foresee - like in casual games and not platform / action games and then you don't want stop / walk animations at all.

The only way I could override it was to destroy object A that had a stop / run animation at the point the animation had to change and create a new object B that had the different stop / run animations in it - else I could visibly watch Fusion change to its built-in animations and then change to my custom animations - no matter what I did to prevent it.
(Of course the solution would've been not to use Fusion's movement module at all and move the object some other way - but at the time that didn't occur to me.)

The auto animations have been around since the Klik & Play days surely it says something in the help file.
It’s probably best practice to only use the built-in animations with the built in movements so you have full control over your animations.

You can't not use the built-in-animations if you use the built-in movements - there isn't an off button or an option you can tick to say - override this built-in-feature.

The documentation is very sketchy in all aspects - it really never explains the sequence of events - why it stops doing things and specifically what all those things are - why it forces its own movements / animations etc or how to overcome that. It's why some of us share the frustration of the thread author - it makes Fusion hard to use and even harder to understand.