YOUR ACCOUNT

Login or Register to post new topics or replies
ssamm
Posts: 364
Filters: 21
I was wanting to make an FF filter that reproduced an effect I made using PaintShopPro and FF, but realized it is impossible because it required me to add effects after using FF's surface filter's lighting.
So my wish is that I could use the "surface filter" as a component (that has an output to further modify).


I did a search and maybe this (or a very similar) idea was mentioned earlier and I think the problem was that it would mess up 3D normal maps (I think(?) BTW, I don't know much about 3D art yet and only work in 2D). But if you don't create the normals map until the last result, I don't this as a big problem -- other than sometimes a filter using a "surface filter" as a component might look strange if used for a 3D texture. (But I don't think this would be *necessarily* always true -- as already with other components you are adjusting the light/dark parameters for certain effects.)
I think this could be pseudo-resolved by just having a note in the filter description that says, "This filter uses a 'lighting/surface filter' component" -- so 3D artists could realize some of the highlights will be already burned into the effect... (Again, I'm just guessing here that this was the concern...)


Anyway, that's my idea for now. And I suppose, it's not that big of a deal, since I can always further manipulate a "surface filter" using PSP. (It's just that I can't create an all-in-one filter and upload it to the library...)

  Details E-Mail
Crapadilla
lvl 52 Filter Weaver and Official "Filter Forge Seer"

Posts: 4365
Filters: 65
We discussed something like that in this thread.
--- Crapadilla says: "Damn you, stupid redundant feature requests!" ;)
  Details E-Mail
ssamm
Posts: 364
Filters: 21
Actually I was thinking of posting my comment in that thread, but some of it went over my head, so I thought it might be safer to just add a new thread to express my specific wish.
I'm sure I don't understand the problems involved, and I doubt I'm the typical FF user anyway. (So I hope this is just taken as an un-censored brainstorming idea -- with no expectations attached.)
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
ssamm,

i've often wished i could have the 'refective', 'reflective blur' and 'metallic' parts of the surface stuff as components or parts of components, so yer not alone here.

and at this point in what i'm doing, i dont much care about 3d either, except maybe for the anaglyphs being done here. so, normal maps, specular, diffuse and all that are 'forgeign subjects' to me and i never worry about them when making filters. let the 3d guys figure those out smile:)

but, FF was designed in large to do textures for 3d use, so, guys like you and me are sort of sub-sets to the group... just sort of curiosities that wandered in off the street (ok, just kidding there... dont send me any emails smile;) )

i'm also a bit surprised whenever i go from normal to surface that the components unplug from the results component and you have to set all your control sequences again and re-do presets. i dont know why cant just toggle these on and off, even in the GUI, or have the whole surface thing as a component that plugged into the results component... but then, i'm not a programmer either smile:)

still, something along these lines would be nice.
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
Quote
Kraellin wrote:
or have the whole surface thing as a component that plugged into the results component...


That was the original idea. I scrapped it because I wanted to make this 'surface thing' easier to find. Currently it always sits at the top of the filter, and if it were a separate component it would be buried in the component list.
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
Quote
Kraellin wrote:
hat the components unplug from the results component and you have to set all your control sequences again


Yes, this is annoying. I hope we'll fix this in future releases.
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
Quote
and if it were a separate component it would be buried in the component list.
hmmm, what if you had it as a separate component, but had it plugged into the results component as a default? that might be a bit annoying to some, but at least it would be prominent.

the thing is, the way it is you cant plug it into just one part of your image and effects. i could easily see using this on just one leg of your component tree but not another, like use it on the foreground but not the background.

and, you can map things into it, but you cant use it to map into other things. i do see your conundrum though. it's such a huge effect module that to place it in the normal components list tends to invalidate its importance. maybe it could just be placed next to or above or below the results component in the editor but not plugged into it? this would give it a fair amount of significance.
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
Quote
Kraellin wrote:
hmmm, what if you had it as a separate component, but had it plugged into the results component as a default?


Not exactly -- we didn't have it as a separate component (there was a number of other problems).
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
ah, ok.
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
m0jo
m0jo
Posts: 10
Filters: 4
Damn, I just had the same idea, searched, came here.. shot down. smile:(

I'm running into problems where I want the surface effect to affect certain parts of the result, but not all. With a Surface componant that would be easy (because it then only affects a certain tree).
For my new Snow filter I want 3D lighting on the snow deposits on the image.. but obviously not over the snowflakes.

Vladimir:
I'm guessing the problems are in coupling the component with the lighting settings?
(if not you can ignore this)
Then what if the result component stays as-is, but you add a surface component with a simplified set of lighting settings in it, which is not affected by the result's lighting?

That would still make a very powerfull add-on to the current features.
Plus I think it would make a lot of (now) very complicated tasks much easyer..
  Details E-Mail

Join Our Community!

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
+27 new in 30 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

30 unregistered users.