Bad allocation error go away!

rant/ I´m kinda disappointed that this STILL hasn´t been fixed!

Everytime I want to render out a texture bigger than 2k, I have to do it from inside Photoshop, which means that I can´t do anything else until it´s done. And depending on the filter speed and image resolution that can take a while

I don´t know if it works with Gimp,never tried since I hate it, but you can´t really expect ppl to buy extra software in order to get a fully functional FilterForge.
And maybe you should mention in your advertisement that the standalone can´t render huge resolutions so that ppl don´t feel cheated./rant over

I love FF, but this really needs to be fixed

Quote
We're working on it!

That´s good to hear!

Keep up the good work

This one is absolutely killing me. I almost work exclusively with 4k x 4k textures and this bug is really making it near impossible to use the program without Photoshop. I'd certainly much rather skip using PS because it locks-up my PC for an hour every time I try to get it to render a large FF texture. PLEASE give us some official feedback on this bug FF team.

Yep, and I've found that it gets really bad when any of the blur type nodes are involved just as others have reported. If I put a single blur node anywhere in the chain it has that error 100% of the time (although it still does it without the blur nodes sometimes). This is a serious issue IMO.