Logo by AGUS - Contribute your own Logo!

END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

it was a great time but no longer maintainable by c.Kleinhuis contact him for any data retrieval,
thanks and see you perhaps in 10 years again

this forum will stay online for reference
News: Visit the official fractalforums.com Youtube Channel
 
*
Welcome, Guest. Please login or register. October 15, 2019, 09:56:53 PM


Login with username, password and session length


The All New FractalForums is now in Public Beta Testing! Visit FractalForums.org and check it out!


Pages: [1]   Go Down
  Print  
Share this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on RedditShare this topic on StumbleUponShare this topic on Twitter
Author Topic: Mandelbulber memory problem  (Read 1477 times)
0 Members and 1 Guest are viewing this topic.
Pauldelbrot
Fractal Senior
******
Posts: 2592



pderbyshire2
« on: May 25, 2011, 12:56:35 PM »

Trying to render a Mandelbox at 1280x720 seems to work with fog disabled, but bombs with fog enabled with:

Code:
Log file: log.txt
commandline: keyframe mode
commandline: settings file: C:\Users\Owner\mandelbulber\mag1\magma_1280_2.fract
noGUI mode
Detected 2 CPUs
Memory allocated
g_thread supported
Default data directory: C:\Users\Owner/mandelbulber
Image textures/envmap.jpg loaded
Width = 512, Height = 512
Environment map texture loaded
Image textures/lightmap.jpg loaded
Width = 512, Height = 512
Ambient occlusion light map texture loaded
Image textures/background.jpg loaded
Width = 2048, Height = 2048
Background texture loaded
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

One odd thing here is that the settings file contains:

Code:
textured_background 0;

so it should not be loading the background texture.

On top of that, the machine has 3GB of physical RAM and God alone knows how much virtual mem; the process size while it's successfully rendering with fog disabled is just a touch under 70 megs. Unless turning on fog makes it need forty times as much memory, it seems to me that it should be working.

Mandelbulber version is 1.00. I see there's a 1.02 out but the change log in the zip makes no mention of any memory or fog related changes.
Logged

Pauldelbrot
Fractal Senior
******
Posts: 2592



pderbyshire2
« Reply #1 on: October 31, 2011, 05:21:39 AM »

Actually, this was solved a while back. Somehow a parameter file had gotten corrupted, and it thought the output image dimension I wanted was 12800x720 instead of 1280x720.

Probably there should be some support for rendering images larger than will fit in memory, by rendering rectangular chunks in memory and stitching them together on disk, but for now it's not an issue for me.
Logged

Buddhi
Fractal Iambus
***
Posts: 895



WWW
« Reply #2 on: November 14, 2011, 06:13:39 PM »

Probably there should be some support for rendering images larger than will fit in memory, by rendering rectangular chunks in memory and stitching them together on disk, but for now it's not an issue for me.

It's possible to render larger images on 64-bit systems (almost no limitation). You can also run program in "Low mem" mode (from shell by command mandelbulber -lowmem, or from Start menu - there should be menu item for low mem mode). Saving of rectangular chinks on disk will be not effective because there is needed whole image in memory for post-processing effects.
Logged

Pauldelbrot
Fractal Senior
******
Posts: 2592



pderbyshire2
« Reply #3 on: November 15, 2011, 03:33:41 AM »

Probably there should be some support for rendering images larger than will fit in memory, by rendering rectangular chunks in memory and stitching them together on disk, but for now it's not an issue for me.

It's possible to render larger images on 64-bit systems (almost no limitation). You can also run program in "Low mem" mode (from shell by command mandelbulber -lowmem, or from Start menu - there should be menu item for low mem mode). Saving of rectangular chinks on disk will be not effective because there is needed whole image in memory for post-processing effects.

Do the post effects require global data about the whole image, rather than being able to be applied to each chunk separately?

Plus, it seems that what I suggested can already be done manually by setting the camera FOV and aim appropriately, rendering separate scenes, and stitching them together in Photoshop. This could not be automated?

There's also the option of graceful degradation: some features disable for large images but everything else keeps working.
Logged

taurus
Fractal Supremo
*****
Posts: 1175



profile.php?id=1339106810 @taurus_arts_66
WWW
« Reply #4 on: November 15, 2011, 01:15:06 PM »


Do the post effects require global data about the whole image, rather than being able to be applied to each chunk separately?


obviously. mb3d already has an option on rendering big ones in chunks (due to the lack of a 64bit version). dof is completely disabeled and ao is limited to the distance estimation ao.
Logged

when life offers you a lemon, get yourself some salt and tequila!
Pages: [1]   Go Down
  Print  
 
Jump to:  

Related Topics
Subject Started by Replies Views Last post
New Born Memory 3D Art titia 0 883 Last post March 20, 2009, 11:37:19 AM
by titia
Mandelbulber 0.60 rendering problem Mandelbulber MarkJayBee 2 1366 Last post June 02, 2010, 09:55:53 PM
by MarkJayBee
Blue moon (and out of memory) Images Showcase (Rate My Fractal) ker2x 1 673 Last post April 05, 2011, 09:04:46 PM
by Buddhi
Mandelbulber - problem setting detail and smoothness for a keyframe Help & Support erstwhile 5 207 Last post February 01, 2013, 11:31:24 PM
by erstwhile
out of memory Mandelbulb 3d Renmen 9 781 Last post December 01, 2016, 10:11:16 PM
by Sabine

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.139 seconds with 28 queries. (Pretty URLs adds 0.01s, 2q)