Broken Mosaic Tiles by Crapadilla

Oh! Beautiful!

Quote
Kochubey wrote: Oh! Beautiful!

Thanks!

Looks like Dilla has smashed Mike's floor with his staff

This is really great filter! Thanks, Dilla!

ooh I like this!

noice The original looks better in my opinon

I can already smell various tile designs being cooked up after this fashion...

Quote
Koh wrote: Ow now you dont have to be THAT evil

Well, one has a reputation to uphold!

Dilla wrote:



Well, my admiration I'll express by this:



!But only till the end of the next week!

Maybe it's time to recall also this one?

Pfah.. going groovy dilla?

that last one nice

wow them circle pattern tiles are way way super cool Dilla!!

So, did anyone else look at the alternate version of this filter? Any opinions?

Quote
Crapadilla wrote: So, did anyone else look at the alternate version of this filter? Any opinions?

If you mean them images of the circle and part circle patterns, I really like them ones , high chance of a HU with that I think.

Quote
Beliria wrote: If you mean them images of the circle and part circle patterns, I really like them ones Big grin, high chance of a HU with that I think.

So this is your take on subliminal message implants, eh?

Quote
Kraellin wrote: why all those inverts right after the cells component and why the duplicate cells component?

The Inverts just serve as sample cache components to cache the 5 different sets of coordinates acquired from the Cells component (the original coordinates and those generated by the 4 Offsets that constitute the edge-detection for the grout). I guess it might not have affected speed that much if I removed them, but I also like how they organize the flow of data.

[Generally, I found that using Inverts to organize the flow of data does not affect render speed in a positive or negative way, but it can lead to faster filters under certain circumstances (due to sample caching). If you want the details, I suggest you re-absorb the 'DOs and DONTs' thread or ask Sphinx or Vlad.]

Quote
Vladimir Golovin wrote elsewhere: The sample cache is located at the output, not at the inputs of the component. Every component stores the coordinates and the value of the last calculated sample, and if the next sample has the same coordinates the component returns the cached value instead of evaluating the sample.

Quote
Kraellin wrote: why the duplicate cells component?

The two Cells components are on different branches of the filter tree, consequently I used duplicates. Remember that the height map branch gets sampled three times more often than the other branches. Also, the two Cells are each going into different "sets" of offsets/noise distortions (one for the grout, the other for the tiles surfacing), so sample coordinates are different on the two branches. Using the same Cells component for both would likely lead to this component being (re-)sampled much more often (since coordinates change so often), and thus likely to a slower filter.

Excellent!!!

This is much better than the "abominations" that I had created for it......much faster, more efficient, half the components, etc.....and did I mention that yours looks better??? ..... .....