"Kenneth" <kdw### [at] gmailcom> wrote:
> Using a single image_map, and *without* pre-#declaring the image,
> the parsing took a LOT of time (with constantly increasing memory use as the
> image had to be 're-processed' for each iteration.) By pre#declaring the image,
> the entire parse/render occured in mere seconds, with a much-reduced memory
> load.

Right, because the POV-Ray parser can't know that it's already red that image
file in, and so it re-reads it from disk, reloads it into a new memory slot,
etc...


> Yep, I agree. Sad to say, when I started working on this scene, I used jpg's,
> and have continued that way ever since. The reason being, that my OLD version of
> Photoshop has wonky problems with correct png gamma when saving an edited image.
> So no png's. But otherwise I LOVE my old version of PS; it's just easier to use
> (for me) than GIMP.

I have not found GIMP to be user-friendly.
In windoze I used wingif, winjpg, Irfanview, and paint.net


> > Buy more RAM -
>
> Ha! But that would defeat my purpose of trying to get me scene to run in, uh,
> 256K  :-P

I look forward to the Inigo Quilez Demoscene version in 8k.   :P

> > I ignored the people who said I couldn't put 16 GB of RAM in my
> > laptop after researching the issue. Been running fine for years.
>
> THAT'S interesting. Yeah, AFAIK, my Win 7 box has an 8MB limit(?), so I never
> thought of trying to increase it. So, my computer wouldn't actually explode,
> right??

It will just not be able to access the memory properly.
It's all very architecture dependent.  YMMV
Flip it over and have someone pop in different (but proper _type_) memory and
reboot it.  If it works (system stats report all the GB you installed are
recognized, then I'd buy it.

Post a reply to this message