YOUR ACCOUNT

Home > Forums > 

Search Forums

Search results 81 - 100 of 122
First | Prev. | 3 4 5 6 7 | Next | Last 

  • What are the differences between using FF as standalone and as plugin?
    Author: Morgantao. Yep, I agree, it's much more rare to see a bad allocation error in plugin mode. The image I used was a mere 4000x3000 image, but I think it's a combination of image size, filter complexity, filter settings (which preset is used), and other unknown variables, like having all the filters from ...

  • Autopsy
    ... [ desperately need folders, authors most requested wish :( ]. While the 5th needs work and at moment wouldn't get pass the FF time render police ;) And the last one has a bug in it that occurs when trying to render anything larger than 600x600 .... Bad memory kernal allocation [ something like that ] bug report sent. I probly redesign it a bit to try and avoid the problem, it's a matter of finding the time :)

  • Thank for all the effort getting rid of Bad allocation error
    Author: SpaceRay. Yes, is true that now the bad allocation is much more often missing and almost does not appear, although sometimes it still happens, but as said really much, much more less often, and I also want to give thanks for this and having been able to solve it at least in this way, I mean ...

  • Rendering
    ... me using FF in 64Bit Photoshop 5.1 I don't know if there's a difference with PS 5.5 that would not allow you run FF as plugin. FF can do 5000 X 5000 image for me on 64Bit Photoshop win 7 64 16bg mem On the same system Stand Alone FF hangs and does Bad Allocation error at 3000 X 3000 with one filter I'm using. I suspect that the advertized 6000 x 6000 can be done with some filters.

  • Photoshop: Filter > Filter Forge greyed out
    ... remained greyed-out. I managed to solve my problem by performing the render in standalone mode and *further* increasing my virtual memory to 500GB. It took around 18 hours due to the constant thrashing, but I finally got an output image without a Bad Allocation error. According to my task manager the virtual memory use got as high as ~250GB so I wasn't too far off with my original virtual memory settings.

  • Heavy Snow (over your images)
    ... like one of the biggest things FilterForge needs to fix that's yet to be fixed. " Well, then we share something Macs and Windows versions, we both have a big unfixed bug that is very bad, you have this LUA script error, and we have the "Bad allocation" error and wish and hope that they get fixed soon

  • Updated: Possible fix for the "Bad Allocation" error
    ... more up our sleeve. Now we have to figure out whether they still continue to work at 64000x64000 pixels. I guess Flagstones would be too heavy for this, so we'll need to find a simpler test case (like the Perlin / Blur combo suggested in one of the bad alloc threads).

  • Rendering
    ... images 3600 x 3600 and up. I am testing filters under "creative" such as paint HDRist and watercolor. The rendering is taking hours to complete. I am also getting an error message but I know that this is a bug that FF is working on. ( bad allocation). I am using a duel core processor, windows/vista. I am using FF stand alone. My question is: are there any settings that I can choose to speed things up or is this normal and should I expect it every time with this size file and this type ...

  • Bad allocation error go away!
    Author: SpaceRay. I agree with you Sharandra Bad allocation error go away! I hope and wish that This can be solved before the final version of FF 4.0 and will not keep another year waiting for the fix as it has happened with FF 3.0. I know that this may be a difficult and complex thing to fix ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    ... buying FF specifically for extreme resolutions. For FF inc.'s defense though, you have a free month of FF Pro to test it, see if you like it, if it works for you and if you can achieve what you want with it. If withing this month you had a constant bad allocation error, and ask around and find out there's no way to fix it, simply don't buy it.

  • Rendering
    Author: bobbijake. Thanks for the reply SpaceRay. I have been reading the forums for a couple of days now, so I know that Bad Allocation is a bug. I also see in the forums that with some files and some filters FF runs slow, but what I can't find is why I can't get it to work at all. I have been running a rendering all night and it is still going now, so obviously it ...

  • Error when saving a 10,000 x 5,000 render
    Author: onyXMaster. "bad allocation" means that you ran out of available memory. Please try the following: 1) ensure your paging file size isn't limited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally it ...

  • FF3 crashes frequently while long renders for big files
    Author: SpaceRay. Is curious that many times that I want to make a larger result with many filters and I mean about 2500 x 3500 not a HUGE resolution at all 70% of the times I get the "bad allocation" error using the standalone version, BUT then I use the Photoshop version and ALL is working right 98% of the times, just once got the error in Photoshop. SO surely the standalone for me is not good to use at all. AND I said is "curious" ...

  • This is the main thread for discussing the 'bad allocation' exception
    Author: Kraellin. no, it's not false advertising, at least as i recall things. the bad allocation thing doesnt happen on every machine. some folks can render on the huge sizes. i think Sign Guy is one that can. he makes textures for the sign industry and uses very large file sizes. it just takes a while. so, it seems to be something specific ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    ... without rewriting FF from the ground up in 64bit, or a genius way to get more than 32 bitian ammounts of RAM, we'll have that max memory cap on FF. That being said, if the bug is isolated and fixed, it's going to solve FF's biggest problem, which is the bad allocation error. Then it's only a matter of render time, without crapping up in the middle of a 3 hour render.

  • Bad allocation error go away!
    Author: Sharandra. rant/ I´m kinda disappointed that this STILL hasn´t been fixed! :evil: 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 :P 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...

  • FF3 crash report
    ... kodak). the render would go as far as you see in the attached screenshot and then pop up with the bug report and wouldnt render any further. there would be several of these same bug reports popping up in the same crash, all seemingly the same thing, 'bad allocation'. my ram goes up to about 56% used and go to that point every time i tried this. after the first crash i killed FF3 and started it again and tried the same thing and it did the same crash at the same point and the same ram usage.

  • 9 MONTHS with this bug and still without a fix, solution or news
    Author: SpaceRay. "Morgantao wrote: The Bad allocation error is more like the Toyota's unintended acceleration problem from 2009-2010, which caused the car to randomly accelerate to breakneck speed. Toyota had to recall their cars. Fortunatly, software bugs can be solved with an update" ...

  • <class XFW::Kernel::StdException> bad allocation
    ... Filterforge 4 Erase all the xml in the folder of filter forge. enter / System / folder. erase all .xml and version files (no folders, just Xmls again try to execute your Filter forge (Did on standalone and work fine) So i believe this bad allocation error happens cause the cache of batches and thumbnails is not correct cause you either apply something or it becomes corrupted. I'm talking about my case, however i cant confirm on someone else case, so I hope this helps.

  • FF3: Slow
    ... page 1 in April 2012 In the last 5 posts or so there are the same issues reported for pretty much ever... Memory usage of 1.5GB max, while the system has 6 or 8 or 12 GB. Slowness with relativly small images. FF going belly up with "bad allocation error" all the time.... For crying out loud, FF inc, DO SOMETHING!!!!" I agree with Morgantao, and also want to know if Filter Forge Inc. will do something about this or will be kept all in silence and without any kind of news ...

Search results 81 - 100 of 122
First | Prev. | 3 4 5 6 7 | Next | Last 

Join Our Community!

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!

Create an Account

Online Users Last minute:

24 unregistered users.

Recent Forum Posts:

Join our Forum Join our Forum
Over 30 000 members!
Join us on Facebook Join us on Facebook
Over 42 000 likes!
Follow us on Twitter Follow us on Twitter
Get updates quickly!
Follow us on Instagram Follow us on Instagram
Tag us #filterforge