Ideas for Filter Forge Beta 2+

Hey angelboiii,

Thank you! I guess I missed that with all the frustration.

Have a GREAT day!

Ron

Great!

Some of the non seamless stuff is very good to build things for the seamless, like bomber particles...

Hey Vladimir,

Good to hear from you!

Quote
Vladimir Golovin wrote: Just wanted to say that we've implemented an additional Override option for the Seamless Tiling checkbox that forces it to "always enabled". It will be available in the upcoming beta

We all, are SOO looking forward to seamless filters again with the NEW features!

THANK YOU!

Have a GREAT day!

Ron

I would like to see ... a way to insert divisions or break or space ... between the parameter controls in the settings tab ... which is used to tweak the filter. Filter makers sould have the ability to add dividers between controls to group similar or related controls. Such as controls for "eyes" ... or "paint" in case there are large no. of controls. The divider should have a heading / title too which will help to identify the set of controls. Filter maker should have the ability to move up/down the divider as presently one can do in manual arrangements.

no, no, no, dont like that. i want to see my filter tree and all the thumbs. i dont mind having a larger preview on the side and grouped components to save space, but in a large filter, especially if you're tracing a problem, you want to be able to see all the thumbs to find where things went wrong.

Quote
Vladimir Golovin wrote: Regarding the larger preview -- I think I've finally found a good way to implement this

Can we see a screen shot of what you have in mind??? .....so we users can start beeeotching or praising it.....

Personally, what I think would work best for "me".....is either one-touch tabs or a preview button (takes up less space than tabs) up top in header bar to toggle between a full-sized preview and the component editor in the editor window.....opening to preview on what component is currently selected in the editor.....with the same right-click view controls.....and even better, with a view control menu bar at the top of the preview window that has another toggle to go from selected component preview to result preview and back. Something like that would be slick and really help my workflow.....

.....

Vladimir: Seamless tiling override!!! YESSSSSSSSSSS!!!!!! Now we are talking

I would like a node that returned it's upstream input with a new variation. Iow, input a node chain and the output is the input with variations incremented for all upstream nodes that have variations.

Quote
Lucato wrote: I didn't see that spinner/dial reply Vlad. Talking about these spinner/dial buttons, where they removed into the 2.007? I didn't get to find them.

Uh, I'm a bit confused. We didn't remove anything. Could you quote the context?

7 ) Scripiting (Apply Changes):
When we "Apply Changes" by pressing the button, it refreshes the script code windows and scrolls it to the top while when pressing the shortcut (Ctrl+Enter) it doesn't happen. It would be cool if the button pressed would act the same way without scrolling to the top. Every time after applying I need to scroll back to the place I was changing the code. When trying/testing it becomes a pain IMHO.

8 ) Scripiting (Debug):
It would be very cool, if we would have some kind of debug window where it would inform the actual values of each variable of the running script.

9 ) Scripiting (Inputs for Map and Curve Scripts):
I'm not sure if this idea would be bad for company secrets, but it would be very very cool if the "map script" and "curve script" components had an input and we would connect any original/default FF components and it would show the scripts and its inputs and we would edit them the way we want to without changing the original ones once the map script will assume the new version and the original version will be as an input only.

10 ) Coming soon...

Quote
Vladimir Golovin wrote: Lucato, regarding where to find spinners/dials: - Any Math component - Any 'Free' component (Free Gradient, Free Rectangle etc.) - Color Picker in HDR mode

Ops, they are still there! :0) Thanks Vlad.

Quote
Vladimir Golovin wrote: That's a bug. We'll fix it. (Apply Changes)

Thanks.

Quote
Vladimir Golovin wrote: Yes, but we will also need breakpoints, and, therefore, a full-blown debugger, which is a bit too much work at this stage. Meanwhile, you can use the error() function to print values to the message log (Igor Lorentz has explained it in a nearby thread.)

I see. Thanks, I'll check the error() function. Thanks for the tip. I'll check also the Igor thread.

Quote
Vladimir Golovin wrote: Basically, you're suggesting a way to expose the source code of stock FF components, right? This is technically impossible because our components aren't written in Lua, they're written in C++, and they use a different API than what we expose to Lua.

Yup, rigth! I see. I tought they were made with Lua too. It would be amazing. Well, who nows you guys some day can post some components in Lua version at the Scripiting Library Thread. :0)

11 ) Scripiting (Line #s):
The scrip text area would have on its left side the number of the lines or an option to show/hide them. It will help to follow log and so on.

12 ) Coming soon...

Quote
Vladimir Golovin wrote: You can follow the log by double-clicking error messages that have line numbers -- this sets the cursor to the line where the error occurred. (But a sidebar with line numbers can be easily implemented.)

Thanks for the tip.

Thanks GMM. Let's wait the new update. ;0)

Continuing...

12 ) Show preset (MI):
On the right side of the "Show Original" checkbox FF would have a new check box "Show preset" with a dropdown list on its right side containing the preset factory numbers/names from 1 to the last preset in the effect/texture in use. So, we would compare the actual settings with some other preset we have created instead of only with the option to compare the original with the actual values. I mean, we would have two options with this feature:
1 - the existing one "Show original" to get to compare the preset in progress with the original image;
2 - this new feature to get to compare the preset in progress with the existing presets from the texture/filter selected/in use.

13 ) Coming soon...