YOUR ACCOUNT

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

  • Filterforge 4 some Problems
    ... author probably only made one preset. The rest that you see on the homepage were generated by the submission wizard but only appear on the page. The filters you download only come with the presets the authors include. 2.) Are you getting the "Bad Allocation" error? Then you should try with a smaller image or run it from within Photoshop. Also do a search in the forum for more information, there are some threads about this and some tips on settings. Well if you want to continue using it ...

  • Render Time Experiment
    ... percentage would be better for speed, but never tested it myself if it was true or not and I have put it at 85%, but now seeing this test and it seems that the RAM at 60% or 90% would be the same, is better to keep it at 60% and avoid much more the Bad allocation bug.

  • Error when saving a 10,000 x 5,000 render
    ... while to turn on/off), it still produced the results with no errors. " Thanks very much for telling me your experience and know that on your side it works fine and right without any errors, you are very lucky. I have MANY times the "bad allocation" error and until now I have not realized that if using FF inside Photoshop it did not give the same error YES, the same as you, also in my Photoshop some few times can be frozen until it renders it all that takes about 20 minutes to ...

  • FF3 crashes frequently while long renders for big files
    ... SOME FF USERS HERE ALSO HAVE THE ERROR INSIDE PHOTOSHOP ? :?: :?: Reading this threads seems that some have ALSO the same error using FF as a plugin. Please could anyone that is using FF as a plugin tell me if you also have found the "bad allocation" error using FF inside Photoshop ? Thanks

  • FF3: Slow
    ... program, and don´t even bother with taking a little bit of time to read up on things. Plus a certain user who always has to put fuel on the fire or reignite old ones ;-) Plus something I wonder about, there were so many complaints about the bad allocation error. Now that they possibly fixed it, no one gives any feedback or makes some big resolution tests. That would help much more than complaining.

  • Why is the render taking so long
    ... handling issues. Standalone version of FF. Using Midtone Enchancher filer on 14 Mp Photo with Bitmap aliasing option on.. Happened during saving to disk (aka final rendering). Exception reported at thread 00002F48 'RenderingMgr 131A6C70/4': bad allocation

  • Error when saving a 10,000 x 5,000 render
    Author: SpaceRay. Is this true what oniXMaster have said ? The error could come fr om the paging file size ??? :?: "oniXMaster wrote: "bad allocation" means that you ran out of available memory. Please try the following: 1) ensure your paging file size isn't lim ited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    ... PLUGIN OF PHOTOSHOP and a resolution of 10.000 x 10.000 pixels and have been able to use 28 filters WITHOUT this unwanted bug !!!! If you do not have Photoshop, there are other possible software hosts for FF SO if you want to avoid this "bad allocation" bug, please try to use Filter Forge as a plugin instead of the standalone version and will be able to render in high resolution WITHOUT PROBLEMS, well probably, as I got this bug 2 times during the test. I do not know if it is important ...

  • Export any filter from Librarian delete all saved filters in favorite
    ... with FF4.015 and another things we have noticed a while ago as you Transfer too many filters from the TRAY "librarian" to filter forge. then as you re opening filter forge there is a BUG kernel and we had to re install FF4.015 many moment. bad allocation we have more than 100GB space available in the computer running 16gb ram and windows 7 2.20ghz. We will appreciate a great support for that bug to be fixed thank you okkanym

  • List of open issues
    ....com/forum/read.php?FID=8&TID=9572) - Issues with alphas and blending (http://filterforge.com/forum/read.php?FID=8&TID=4397) - Worley bug (http://www.filterforge.com/forum/read.php?FID=8&TID=2167&MID=50248&sphrase_id=1071489#message50248) Windows: - Bad allocation (http://filterforge.com/forum/read.php?FID=8&TID=9955) - Unknown exception (a common problem surprisingly not reported on the forums) - Horizontal lines with multi-pass previews (http://filterforge.com/forum/read.php?FID=8&TID=10011&MID=107258) ...

  • FF3 crashes frequently while long renders for big files
    ... found some interesting information from oniXMaster in reference to rendering big file sizes and giving error, please see it here below COULD THE PAGING FILE SIZE FOR TEMPORARY FILTER FORGE FILES BE THE PROBLEM ? "oniXMaster wrote: "bad allocation" means that you ran out of available memory. Please try the following: 1) ensure your paging file size isn't lim ited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally ...

  • Stable Rendering
    ... fix, solution or news (http://filterforge.com/forum/read.php?FID=8&TID=9955) (as put above this was before when the thread was done and now in this moment is 15 MONTHS instead of 9) --> Please, MORE information class XFW:Kernel:StdException> bad allocation (http://filterforge.com/forum/read.php?FID=8&TID=9394) RENDERING!!! (http://filterforge.com/forum/read.php?FID=8&TID=10882) HUGE Resolutions = FAIL (http://filterforge.com/forum/read.php?FID=8&TID=9365) Error when saving a 10,000 x ...

  • Error when saving a 10,000 x 5,000 render
    ... I rendered a 10000 x 5000 image of this filter (one of my favourites) Kromatism (http://www.filterforge.com/filters/4129.html) http://www.onepixeldeep.btinternet.co.uk/Kromatism.jpg When I went to save it as a .JPG, this error occured : bad allocation After cancelling the error, saving halted, but the save progress dialogue box remained open - after cancelling that, I got this error : Object @0804F6F0 was not released before destruction. FF does save a partial JPG file which can ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    ... but in this case, it kinda goes like this: "I tried to render a 4000x4000 or larger image". It's not any specific filter or image or resolution that makes FF spew this error. It seems like all filters have the potential to crap out with bad allocation, given high resolution jobs. Also, littering the forum with the same bug over lots of posts is not good conduct. There's a bug report forum, and all posts about one bug should live under the same thread. It's ok to bump the thread every ...

  • List of bug fixes and additions in Filter Forge release version 1.007
    ... · Fixed a bug that resulted in incorrect handling of a preset with a missing environment. · Fixed a bug that caused incorrect slider behavior. · Fixed a bug that caused incorrect handling of long filter names. · Fixed a bug that caused 'Bad allocation' errors to appear while opening certain filters. · Fixed a bug that caused 'Last filter action ID doesn't match current filter ID' errors to appear while opening certain filters. · Fixed a bug that caused a filter to be removed from ...

  • Bad allocation error go away!
    ... fix, solution or news (http://filterforge.com/forum/read.php?FID=8&TID=9955) (as put above this was before when the thread was done and now in this moment is 15 MONTHS instead of 9) --> Please, MORE information class XFW:Kernel:StdException> bad allocation (http://filterforge.com/forum/read.php?FID=8&TID=9394) Stable Rendering (http://filterforge.com/forum/read.php?FID=9&TID=10840) RENDERING!!! (http://filterforge.com/forum/read.php?FID=8&TID=10882) HUGE Resolutions = FAIL (http://filterforge....

  • Error when saving a 10,000 x 5,000 render
    ... :) PLEASE MORGANTAO COULD YOU BE SO KIND TO CONFIRM THIS IF POSSIBLE Could you be so kind to test FF as a plugin of Photoshop (or other host)and confirm if you can use Filter Forge as a plugin of Photoshop (or another host) without the "bad allocation" error ? . You only need to have a 3000x3000 photo, or better higher. ALSO this is of course and welcomed if any other one wants to make the same test Thanks very much for your help

  • Can't install
    ... Processor info: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, ~2387 MHz Filter Forge x86 4.001.25805.53330 Release, September 12, 2012 12:45 [9/16/2012 8:52:34 PM AUS Eastern Standard Time] Exception caught at thread 00001EAC 'Application': bad allocation (0) : ()+0 at 0088BBA4 in Filter Forge x86.exe (0) : ()+0 at 0067EA1B in Filter Forge x86.exe (0) : GetProcAddress()+451 at 75C4941E in C:\Windows\system32\kernel32.dll (0) : ()+0 at 00EC5125 in Filter Forge x86.exe (0) : ()+0 at 00F4C0E4 ...

  • Help with an error.
    ... temporary files and is made the either if it using one or the other ? Or the plugin version has a different way to manage memory and FF temporal files? Please also see this information below fr om oniXMAster "oniXMaster wrote: "bad allocation" means that you ran out of available memory. Please try the following: 1) ensure your paging file size isn't lim ited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally ...

  • This is the main thread for discussing the 'bad allocation' exception
    Author: SpaceRay. "Sharandra Usually I can´t render 4096x4096 in the standalone version without getting the bad allocation error" Yes, for me 98% of the times that I try to render above 3500 pixels in standalone mode it gives this error, and it happens in both ways, I mean if you use the reduced size and then go "save image as" or if you set the ...

Search results 101 - 120 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,739 Registered Users
+5 new in 7 days!

153,586 Posts
+8 new in 7 days!

15,356 Topics
+6 new in 30 days!

Create an Account

Online Users Last minute:

10 unregistered users.