Sphinx.
![]() |
||
Posted: June 16, 2017 1:57 am | ||
GMM
Moderator
Posts: 3491 |
No, this is not a bug.
If you keep in mind that everything in the digital world starts with 0, it will become more intuitive ![]() This is what I wrote in the help file: When a map component is connected to this input, the number of the selected list item is determined separately for different image areas by the HDR brightness level of the image supplied by that component. The item number is calculated as the brightness level rounded to the nearest integer: the brightness level of 0 to 0.5 corresponds to the first item, the level of 0.5 to 1.5 to the second item, and 1.5 to 2.5 to the third item. Out-of-range values are clipped, which corresponds to the last item of the list. (feel free to suggest better wording.) Attached is a filter to illustrate my point. Mapping Explained.ffxml |
|
Posted: June 16, 2017 7:31 am | ||
Sphinx.
![]() |
Okay, yeah I figured that was the logic. I would find truncation more logical in this case though:
0.x => List Item 0 1.x => List Item 1 2.x => List Item 2 (speaking zero based here) But really - any of the approaches acceptable as long as you're consistent (which I wanted to check). Those new changes are most welcome ![]() |
|
Posted: June 16, 2017 7:51 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+19 new in 30 days!
153,534 Posts
+31 new in 30 days!
15,348 Topics
+72 new in year!
23 unregistered users.