Kraellin
![]() |
we've had this discussion before, i know. but, having just run into this again, i'd like to bring it up again. the height features in surface filters is really cool, along with all the hdri. but, it's in the wrong place. often, at least in image/effect type filters, you want to fiddle with the height BEFORE the results and separate from the image itself. you only want to tweak the height on an effect that is later going to be blended with an imported image.
with the height controls IN the results component, this is not possible. and often, because you had to blend your effect WITH the import BEFORE the results, you cant tweak the height of JUST the effect portion. thus, your effect AND the import get affected by the height controls. thus, control is limited and we have to make explanations to the end users not to fiddle with the height too much or you'll break the overall. even if i could re-map the height within the results component this would help a bit. and i know i can limit the effects coming into the HEIGHT node to control the height that way, somewhat. but, that also limits how much height one can put on the effect, and is again, not the optimum solution. also, if HEIGHT were a separate component, one could use it more than once in other portions of the filter. i dont have a current need for this, but it seems like it could be desirable. i'm not a coder. i dont know how much this would entail. i'm fairly sure it's possible, but i dont know how easily or if there are any other drawbacks to doing this. for all i know it would require a re-write of major portions of the code. so, i'm just stating a condition i see and asking here what would be involved and is it even possible for the current FF or if it would require a major re-write that we wont see until FF ver 2. so, vladimir and FF crew, this is as much a question as it is a request. If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: August 27, 2007 2:18 pm | ||||
Foxxee
![]() |
Well, I sure could ![]() Another good suggestion I hope gets a little consideration ![]() ~Foxxee~
You are more than welcome to use and learn from my FF filters ;) |
|||
Posted: August 27, 2007 4:52 pm | ||||
Crapadilla
![]() |
I'm confused, Kraellin. Are you talking about the 'Height' map input or the 'Surface Height' parameter on the Lighting tab?
Also, I'm not sure what you mean by "fiddling with the height BEFORE the result component". 'Height' is a map input, and the final destination of any height map. As such, you are always "fiddling with the height BEFORE the result component" by definition. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||
Posted: August 27, 2007 5:06 pm | ||||
Kraellin
![]() |
dilla, specifically, the height node on surface filters. in my 'blood stain' filter is a good example of why this is needed. if i turn the height control way up, because an effect i'm applying to an imported image cant be adjusted heightwise without also adjusting the imported image.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: August 27, 2007 5:09 pm | ||||
Vladimir Golovin
Administrator |
Height is inseparable from Lighting and all its settings. Actually, its Height (along with the Height Map input) what makes the surface filters possible. The question can be reformulated as follows:
Can we have Result (along with Lighting) as a separate component, instead of having a single copy of it at the top of the tree? I remember that we already discussed why Result has been placed at the top of the tree -- try to look for earlier threads on this. |
|||
Posted: August 28, 2007 5:26 am | ||||
Kraellin
![]() |
ok, i ran into this again when working on a filter. so, let me put this a different way and give an example. perhaps we dont need this if someone can tell me how to do this, but so far, i'm not seeing it.
in crapadilla's 'noise lab' thread i learned a bit more about noises and one of the things i learned was how to use one noise on the surface color and one on height in the results component to get a lot more depth in a given filter. that was good. but, now i want to take it an extra step. let's say i have done the noise and noise thing on surface color and height, but i now want to add something additional to that effect, an overlay. i can do this with two separate filters and that's good, but i'd prefer to do it in one filter. so, the question is, if i've already got a surface color and height combination that i like, how do i add an additional element that overlays those two effects and would be the foreground over those, if i've already used the surface color and height nodes on the results component? i dont see how i can do an overlay on the surface color because the height control is going to alter both the original noise and the overlay. and i cant put it on the height node because that's going to affect the height of the surface color and such. so, the point of this thread was to be able to essentially have another results component that wasnt named 'results' but that would do the same things as the results component, so that i put additional elements in there without warping the two noise elements. let's state this another way, just to be sure i've got this right. let's say i had another component that did exactly the same thing as the results component. i could plug one noise into the surface color and one into the height and then have that output to anything else. i could then add in any additional elements and components and routines i wanted to and then plug that all into the final results component. essentially, this would do a pre-render on height to get that final noise blending i wanted and then be able to plug that into my overlay and finally to the result. and, the results component, the real one, could be either surface or simple still because the pre-rendering on the other one would already be a done and just pass a final out its output. i really dont think this is impossible to do and i do keep running into this in filter making. i want to pre-render a height and surface color combination like the current results component does and then pass that on to the rest of the filter. this shld be possible to do. If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: January 18, 2008 1:49 pm | ||||
jffe |
I don't think you can do it as a *foreground* if you are already using the surface/main input. There are 5 inputs for the texture/surface filters though, have you already tried all combinations of plugging things into each of those ? I'd have to imagine that with enough experiments and adjustments, that you could make textures with 5 different elements to them in that way no ? The trick might be inverting some, or adjusting the gamma/blurring some and whatnot, stuff you already know really, just finding some combos that work, and that might be different for each one eh.
jffe Filter Forger |
|||
Posted: January 18, 2008 1:57 pm | ||||
Kraellin
![]() |
jffe, an inversion on some of those nodes might help me. i'll look into that. but i still dont see why one cant just render a bump map type thing like we do in refraction or some of the other 'height' nodes that exist in components. in fact, that gives me an idea. perhaps i can do my pre-height with some of those components that already have a 'height' node. that might work. i'll look at it some more.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: January 18, 2008 2:43 pm | ||||
jffe |
----The only other thing I can think of, is some careful blending. The *blend* component is sorely underused me thinks, there's still a lot you can do with it. I actually just discovered a 'glitch' in it similar to the look of the High Pass trick I used in one of my filters, it throws up random/weird artifacts that look kinda cool in a low-fi nu skool glitchtronica kind of way. ^_^ jffe Filter Forger |
|||
Posted: January 18, 2008 3:08 pm | ||||
Kraellin
![]() |
yeah, i've been pushing the limits with blend modes on this one. and i just tried refraction to as a pre-rendering height blend. it came a little closer, but no prize. i'll keep toying with it. noise elevation didnt work at all.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: January 18, 2008 3:35 pm |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+18 new in 30 days!
153,537 Posts
+6 new in 7 days!
15,348 Topics
+72 new in year!
23 unregistered users.