YOUR ACCOUNT

Login or Register to post new topics or replies
SpaceRay
SpaceRay

Posts: 12298
Filters: 35
In the description of animated components of FF 11 Studio shown below on the quote, for example the Normalized time is put that you can Connect this Normalized time to any of the 7 kind of inputs shown below and is told that this is without using remapping

So, then if all this is true, then Please, I want to know what I may be doing wrong, as most of the Non Green inputs that I try to use gives a red warnings sign

For example if I want to use the Normalized time connected to the variation input of bomber plus, It gives a warning

Should I put something in between?

How is then true the below text?

Thanks very much for any possible help

Quote
When Use Remapping is turned off (or when the remapper is set to its default settings), the value is passed as follows:

To Slider inputs: GREY INPUT
the Normalized Time range (0 to 100) is proportionally mapped onto the range of the target slider. The resulting value of the target slider is determined by a linear interpolation between its minimum and maximum values, where the interpolation coefficient is defined by the output value of Normalized Time.

To Color inputs:
the Normalized Time range (0 to 100) is mapped onto a black-to-white gradient. The resulting color is determined by a linear interpolation between black and white, where the interpolation coefficient is defined by the output value of Normalized Time.

To Angle inputs:
the Normalized Time range (0 to 100) is proportionally mapped onto the range of 0 to 360 degrees. The resulting angle is determined by a linear interpolation between 0 and 360, where the interpolation coefficient is defined by the output value of Normalized Time.

To IntSlider inputs:
the Normalized Time range (0 to 100) is proportionally mapped onto the range of the target integer slider. The resulting value of the target integer slider is determined by a linear interpolation between its minimum and maximum values, where the interpolation coefficient is defined by the output value of Normalized Time. The result of the interpolation is rounded to an integer number and sent to the target input.

To List inputs: the Normalized Time range (0 to 100) is proportionally mapped onto the range of the target list. The item number in the target list is determined by a linear interpolation between 1 and the item count of the list, where the interpolation coefficient is defined by the output value of Normalized Time. The result of the interpolation is rounded to an integer number and sent to the target input.

To Checkbox inputs: if Value is greater than 50 (half the Slider Control range), the target checkbox becomes 'checked', otherwise it stays 'unchecked'.

To Value inputs: the Normalized Time range (0 to 100) is proportionally mapped onto the range of 0 to 1. The resulting value of the target Value input is determined by a linear interpolation between 0 and 1, where the interpolation coefficient is defined by the output value of Normalized Time.
  Details E-Mail
emme
Posts: 718
Filters: 8
You're not doing anything wrong. Using normalized time on variation should work perfectly fine.

I think the warning is there just because the expected input type for variation is an integer - which normalized time is not. As the quoted text points out, normalized time is automatically mapped to IntSlider inputs using rounded linear interpolation between the default min-max values. So no need to worry about warnings as long as everything works smile;)
  Details E-Mail
SpaceRay
SpaceRay

Posts: 12298
Filters: 35
Thanks very much for your answer

Quote
emme wrote:
You're not doing anything wrong. Using normalized time on variation should work perfectly fine.


Yes, is true that it seems to be working correctly and would not be a problem if you can be sure that it will not give any possible error, and another thing is that even when it may be working correctly, you can not submit a filter with a red warning as it not allowed.

Quote
emme wrote:
I think the warning is there just because the expected input type for variation is an integer - which normalized time is not, As the quoted text points out, normalized time is automatically mapped to IntSlider inputs using rounded linear interpolation between the default min-max values.


Yes, you are right, and this is the same that I have thought, BUT if the quoted text is right, then WHY you get the warnings IF the animation component is already mapped accordingly to the input that is connected?

I mean that if it is already allowed to connect an animation component to all the shown input as in the quoted text and the animation component is then adapted to the connected input, why you get a warning?

So this may be a bug that is wrong and should be fixed or modified?

Quote
emme wrote:
So no need to worry about warnings as long as everything works


Yes, I agree with you and you are right that is not needed to worry if it works, unless you may want to submit a filter to the library.
  Details E-Mail
SpaceRay
SpaceRay

Posts: 12298
Filters: 35
I have made a test of all the possible warnings that you may get with all the possible components that could be used to animate something and this is the result

I thought that it was all the grey components, but I was wrong as some of the grey input does not give an error.

From my point of view, I think that this should be changed to avoid confusion and also as it is a bad thing if you want to submit a filter to the library and I am sorry that I do not understand why are these warnings IF the animation component as for example the Normalized time is already adapted and to the corresponding input.

  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,711 Registered Users
+18 new in 30 days!

153,533 Posts
+31 new in 30 days!

15,348 Topics
+73 new in year!

Create an Account

Online Users Last minute:

25 unregistered users.