Robot Monster
![]() |
i might be going crazy, but it seems that FF 2.006 changes the output generated by some filters?!
Ammonite is a really obvious example -- the output looks nothing like the preview pictures. (I've been using this filter recently, and it was the one I had open when running FF 2.006 for the first time). Is this change expected, or an introduced bug? Seems like a bug to me. |
|
Posted: June 5, 2010 1:39 pm | ||
Vladimir Golovin
Administrator |
2.006 shouldn't change anything -- all components are versioned. The output of a filter may look different on a thumbnail and final pic due to possible aliasing artifacts in the thumbnail. Could you post a link to the filter in question?
Edit: Ammonite looks OK. Here's what I just rendered on my work machine: ![]() |
|
Posted: June 5, 2010 5:14 pm | ||
Robot Monster
![]() |
Yeah, I thought you versioned the components to prevent this.
Here's what I get from FF2.006 on Ammonite -- oh I should have mentioned this is on the Mac build. ![]() |
|
Posted: June 6, 2010 4:20 am | ||
Totte
![]() |
Got this, mac OS X 10.6.3 Beta 2.006.
I suspect you've got that 2004 (or 3) bug that caused the filters to be corrupted. There is a thread here that describe the problem: http://www.filterforge.com/forum/read...6&TID=7342 ![]() - I never expected the Spanish inquisition |
|
Posted: June 6, 2010 5:20 am | ||
Robot Monster
![]() |
Thanks Totte -- it appears you are correct -- forcing a redownload of that filter has fixed the problem.
Weird that the previous version of FF handled the filter on my harddrive perfectly.. oh well! Now I guess I need to redownload all filters, otherwise I have no way of knowing which filters have become corrupted. Sigh! Thanks again Totte! |
|
Posted: June 6, 2010 5:48 am |
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
+31 new in 30 days!
15,348 Topics
+72 new in year!
11 unregistered users.