CompuServe Messages

Imagine Wrap Mem Hog?

    27-Oct-91 12:46:48
Sb: Imagine Wrap Mem Hog?
Fm: John Pendergrass 76246,676
To: Roger Hand 73520,3506
Roger, remember your problem with wrapping a 1 bitplane image in Imagine. You kept getting 'not enough ram' error messages, even though you thought the brush was pretty small (cause it was just 1 bitplane, after all). I thought that maybe Imagine expanded all brush wrap images to 24bits internally? Well, I did a quick test, and results seem to bear out that it expands the 1 bitplane image to 24bits. At least that amount of memory is consumed. Here are the results of my test: I created a 1 bitplane 640×600 image. As a 1 bitplane image it should use up @ 48,000 bytes internally (640×600/8). As a 24 bitplane image it would use up @ 1,152,000 bytes. (640x600x3) I started Imagine and set up a simple sphere for rendering. I used AVAIL every few seconds immediately after I told it to start rendering…. Memory avail Memory avail w/ no image wrap w/ color image wrap. Imagine running, before rendering 8,898,952 8,899,192 @ 2 secs after starting to render 8,729,568 7,720,776 @ 10 secs after starting 8,604,987 7,577,680 when done rendering 8,898,952 8,899,192 As you can see, when rendering without an image wrap, the memory dropped about 80K just after rendering. With the image wrap, it dropped almost *1.2meg*. That's just about the size of the 2 bitplane if expanded to 24bits. So, I'd think the solution to your problem will have to be MORE MEMORY 🙂 It appears that Imagine does expand all images to 24bits, and that really eats memory. Either that, or use smaller brushes for your wraps. Good luck. –jp–seattle–