Crapadilla
![]() |
No clue why this is so, but this bugs the hell out of me when trying to unify repeat values (i.e. relative sizes) in filters that use all of the below pattern components:
Why does the minimum repeat of 1 on the Pavement component look inconsistent with those of bricks and tiles? I'd expect it to give an output just like the icon on the component bar! ![]() ![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 21, 2008 11:55 am | ||||||
Crapadilla
![]() |
This fact makes hooking these components to a single Repeat slider difficult. The only thing you can do is remap this Repeat value with a step size of 3 for Bricks and Tiles. This unifies the Repeats at a global value of 3, but gives us a rather big visual repeat to start with!
Why not reduce the default Repeat of the Pavement to look like as on the component Bar? This way we'd have Repeats unified at a global value of 1, as it should be! [Below you can see Bricks at Repeat 3, Pavements at Repeat 1, Tiles at Repeat 3] ![]() ![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 21, 2008 12:02 pm | ||||||
Crapadilla
![]() |
IMHO one could easily cut the Pavement components current hardcoded minimum repeat value in half and still keep the bricks that make up the patterns in a unified size relationship.
See the commented filter attached below... ![]() Pavement Mimimum Repeat Revisited.ffxml --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 21, 2008 1:54 pm | ||||||
Crapadilla
![]() |
*** insert sounds of crickets chirping lazily in the midday heat ***
![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 25, 2008 7:17 am | ||||||
Kraellin
![]() |
i'd post a popcorn smilie, but dont have one
![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||||
Posted: November 25, 2008 9:05 am | ||||||
Crapadilla
![]() |
Well, there might be some sort of 'reason' to this that I'm overlooking, so I'm really interested in why the pavements component was designed this way.
--- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 25, 2008 12:05 pm | ||||||
Kraellin
![]() |
well, quite honestly, i've had questions about the differences in those components, also. i see little reason, for instance, in having the hue/light/sat nodes on there, when we already have a hue/sat component. i also dont see why perlin doesnt have more nodes like the others. i've also used all the noise components in a single filter and attach just one set of controls to all of them and then have a selector to swap out the different noises, but the controls dont line up one to the next exactly. most are pretty close, with perlin being the most oddball.
so, i just eat my popcorn and wait for beta2 ![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||||
Posted: November 25, 2008 1:15 pm | ||||||
Vladimir Golovin
Administrator |
We always try to maintain input consistency across components, so there certainly was a reason for this. Most likely, it was because the mininum repeat value / minimal tiling region are different for these kind of patterns. |
|||||
Posted: November 26, 2008 3:10 am | ||||||
Crapadilla
![]() |
I suspected it might have something to do with this, which is why I have taken a closer look at the miminal tiling regions of all the pavement bond types. There is one bond type - the 'boxed basket weave' - that has a very large 'minimum tiling region' (which adversely affected the choice of minimal repeat for all other bonds, I presume). However, as I have demonstrated inside the filter above, the 'boxed basket weave' is actually two similar patterns combined (or rather the same pattern, but with one copy rotated 90 degress and then combined with the original). Hence one could - by taking care of that one pattern - further reduce the minimum tilings for all the pavement component bond types and bring the overall minimum repeat closer to that of the bricks and tiles components. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 26, 2008 5:55 am | ||||||
Vladimir Golovin
Administrator |
They're per brick, not per output.
Perlin and Worley use different algorithms with different parameters. Also, our Perlin already has more controls than its usual implementations. |
|||||
Posted: November 26, 2008 9:56 am | ||||||
Kraellin
![]() |
ok, thanks, vlad.
in all honesty, i was mostly just making remarks to keep dilla company here till someone like you showed up and could answer intelligently. so, i was mostly just making dumb-ass comments rather than serious conversation or suggestions. so, since you're here, i'll shut up now ![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||||
Posted: November 26, 2008 12:48 pm |
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,531 Posts
+36 new in 30 days!
15,347 Topics
+72 new in year!
34 unregistered users.