StevieJ
![]() |
HUGE rendering problems with surface result filters...
1) The "Bad Allocation" error needs to be fixed and rendering stabilized... Renders rarely complete without being stopped by this error at 5000 x 5000 ppi and above resolutions...and if by some chance they do complete, they are mostly either corrupted files or lighting effects are only partially done... Sometimes these high res renders won't even begin to render... Using FF as a Photoshop plugin does not remedy the problem...and neither does using one core to render... 2) The higher resolution you go...the less a rendered result looks like your display image... Try it... Take a high res image of 5000 x 5000 and render it using a surface result filter... Then take the same image at a lower resolution like 1000 x 1000 and render it... The lower resolution render looks pretty close to what you were looking at on your display...while the high res render has lost almost all the lighting effects...and is not even close to what you were seeing on your display... Below is a reduced 5000 x 5000 render that finished...but only partially did the lighting effects... This is what is happening continuously at high resolution...if it even starts to render, stops rendering, or corrupts with the "Bad Allocation" error... ![]() Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
|||||||
Posted: January 30, 2013 6:57 pm | ||||||||
FilterForgePersonOfTheYear
Posts: 4 |
Hi Steve,
I'm glad you are keeping up with this, because this is an important issue! Sort of makes getting the Professional version overkill. In it's current state (for anyone on the fence), I would not recommend the Pro version until they get this resolved. |
|||||||
Posted: January 31, 2013 9:16 am | ||||||||
joBox
![]() |
I was bitching about this well over a year and a half ago, and it's STILL a problem. I thought it would be fixed in 4.0, but so far, no luck.
It's BEYOND frustrating, and I've basically given up using FF unfortunately. joBox |
|||||||
Posted: February 5, 2013 10:40 pm | ||||||||
FilterForgePersonOfTheYear
Posts: 4 |
I've had some success recently- at least with some of the well known filters (chain mail, tiles, scale armor). As suggested by support- I ran it through photoshop and have successfully rendered a 4k image, 8k image, 10k image, and currently rendering a 12k image (started this morning).
Here's some tech details: Platform: Win 8 Pro Software: Adobe Photoshop CS6 64bit (latest version) Plugin: Filter 4 (latest version) a) After creating a new Document in Adobe (sized in pixels), I add a new layer and save the project. b) I select the Filter Forge 4 filter/plugin through the adobe menu (this launches Filter Forge 4) c) I verify the Render settings in filter forge are set to single cpu, and set the memory to 80% available. d) I select whatever filter I want to try out, make sure "seamless texture" is selected, and click "apply". e) As it renders out (which takes most of the day 10+ hours for the 10K), Adobe Photoshop becomes unresponsive. The only indicator is that popup window in Photoshop that shows rendering progress. I haven't had one error since I started doing this. Keeping my fingers crossed the 12k renders out okay. I know not everyone has Photoshop, but just thought I'd post my experience with Filter Forge. As a standalone app, high resolution textures never worked for me. As a plugin to Photoshop- seems to work pretty good.. but I'll know more when I start experimenting with more process heavy filters. If anyone has any filters they'd like me to try out as a test, let me know. Regards~ |
|||||||
Posted: February 6, 2013 7:59 am | ||||||||
SpaceRay
![]() |
YES, YES; I have made the same as you, I have given up making things in FF, as I have too many Bad allocation errors, and I am fed up of loosing time and waiting to see if the render error appears or not, AND I have 16 GB RAM so it is not a problem of not having enough (I know that FF can´t use more than 1,5 GB)
I agree with you, the first news of this Bad Allocation bug error was in the 6th September 2011 and now we are in the 6th February 2013, so it has been already 15 MONTHS with this bug and still there is no news when this could be solved, and it also happens in FF 4.0 Beta 1. 9 MONTHS with this bug and still without a fix, solution or news (as put above this was before when the thread was done and now in this moment is 15 MONTHS instead of 9) I have tried to help the FF team to solve this in the way to put a thread with all the error reports from the FF users, but no one has put any bug report there High resolution rendering test bug report compilation inside here Also see this other threads for more information about this and that there are some information to solve this in some way temporaly meanwhile they fix it: --> Please, MORE information class XFW:Kernel:StdException> bad allocation HUGE Resolutions = FAIL Error when saving a 10,000 x 5,000 render FF3 crashes frequently while long renders for big files Stable Rendering
Bad allocation error go away! Rendering above 5000x ??? |
|||||||
Posted: February 6, 2013 5:28 pm | ||||||||
Vladimir Golovin
Administrator |
Here's a possible fix for the Bad Allocation error:
http://www.filterforge.com/forum/read...&TID=10903 |
|||||||
Posted: February 8, 2013 10:21 am | ||||||||
zailaiboke
Posts: 3 |
the way to put a thread with all the error reports from the FF users, but no one has put any bug report there
______________________________________________ Aion Kinah zailaiboke zailaiboke |
|||||||
Posted: September 3, 2013 3:37 am |
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,533 Posts
+38 new in 30 days!
15,348 Topics
+73 new in year!
16 unregistered users.