Sphinx.
![]() |
I'm trying to figure out how I can offset a checker component exactly one checker square horizontally.
The principle is simple enough, if we have 4x4 checkers (repeat 2), we offset -25 horizontally to get the next checker in the row. I.e. offset value = 100 / (repeat * 2). The problem arise when I want to control the offset from an intslider that controls the number of repeats in the checker - I can't seem to get the mapping right. I know that a solution is possible via the Bias curve somehow, but I can't get it right. Any help appreciated ![]() I've attached a very simple filter that shows the idea. next checker offset.ffxml |
|||
Posted: September 30, 2008 5:37 am | ||||
Kraellin
![]() |
try a step curve.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: September 30, 2008 9:04 am | ||||
Sphinx.
![]() |
How? |
|||
Posted: September 30, 2008 9:13 am | ||||
Kraellin
![]() |
forget the step curve. i just looked at the filter. but, what i dont get is the problem here. just use the offset. why doesnt that work? are you trying to get the checker offset all in one jump, is that it? rather than just sliding tthe horizontal along and taking many steps?
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: September 30, 2008 2:08 pm | ||||
Crapadilla
![]() |
Did you take a look at my Unstable Weave filter? I had a similar problem back then: Controlling a Repeat and an Offset value with the same intslider. I used a switch component that came 'preloaded' with the right offsets. The drawback is, you can on use 12 discrete repeats. The same technique is also inside my good olde Roofing Shingles filter. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||
Posted: September 30, 2008 2:48 pm | ||||
ThreeDee
![]() |
||||
Posted: September 30, 2008 4:31 pm | ||||
Sphinx.
![]() |
Ahh great!.. seems to work as it should, though I have a few problems with high cell divisions (repeats)
Cell Interpolate.ffxml |
|||
Posted: October 1, 2008 4:22 am | ||||
ThreeDee
![]() |
The problem being...?
|
|||
Posted: October 1, 2008 5:56 am | ||||
Sphinx.
![]() |
At a few Cell Division values lines appears (see image), e.g. Cell Division = 40 (disable AA). I'm not sure what is causing it yet...
![]() |
|||
Posted: October 1, 2008 6:25 am | ||||
ThreeDee
![]() |
Okay, I just saw that when opening a file that wasn't 600x600.
I suspect there is an extremely small inaccuracy in the calculation of the curve which causes the offset to be a tiny fraction off and which is somehow exacerbated by the anti-aliasing routine. Seems so, for as you increase the anti-aliasing setting those random lines become less and less visible. Check out this rather weird way of handling it: Instead of offsetting by 100, put 99.9999 in the offsets and it is gone. |
|||
Posted: October 1, 2008 6:49 am | ||||
Sphinx.
![]() |
Ah.. yep.. that did the trick.. thanks again ![]() |
|||
Posted: October 1, 2008 7:09 am | ||||
Crapadilla
![]() |
Ah, an elegant solution, ThreeDee! That will help unclutter some of my old filters...
![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||
Posted: October 1, 2008 3:39 pm |
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,537 Posts
+6 new in 7 days!
15,348 Topics
+72 new in year!
42 unregistered users.