Thorsten Froehlich wrote:
> 
> In article <36FB1833.6E711D6C@infomagic.com> , Xplo Eristotle
> <xpl### [at] infomagiccom>  wrote:
> 
> > Not really; it's simply unable to locate the files. Evidently it just flat-out
> > refuses to look anywhere else but the directory that contains the saved scene
> > file, but doesn't say so.
> 
> You may also want to check the for leading spaces in volume names, e.g if
> the volume is named " Macintosh HD" instead of "Macintosh HD" this will not
> work (because of some technical reasons in the core, platform independed
> code of POV-Ray).

That's it.

> > The effect is similar to what you get when you blow up an image in Photoshop
> > (using interpolation): the image looks jaggy, but the edges of the jags are
> > blurred together.
> 
> I understand now.
> Theoretically this cannot happen at all, we draw plain rectangles using the
> Macintosh toolbox to draw to the screen, and there is no interpolation
> option...if you can verify that this happens with radiosity off (and in
> 3.1e) I will look into this further, especially because this problem has
> never been reported so far.

*nods*

> >> It seems that by the time you see this the POV-Ray application has been
> >> completely corrupted and the crash is only the result of all the previous
> >> problems.
> 
> > *shrugs* Fresh installs suffer from the same problem, so if it's corrupted,
> > it's corrupted at the source.
> 
> Ups, my mistake: I don't mean that the application _file_ is corrupted, the
> application code in _memory_ is corrupted.

Even if I reboot and try a fresh render immediately after launching POV-Ray,
it'll hang.

> >> However, if you do _not_ touch the application and render preferences dialog
> >> before rendering but POV-Ray still crashes, it would be great if you could
> >> fill out the bug report form in the docs folder and e-mail it to us.
> 
> > I'll look into it.
> 
> Another idea: Do you use the default memory settings? If you are rendering a
> scene with lots of objects, preview, radiosity etc on POV-Ray will need a
> lot of memory. We still have sometimes crashes when memory gets far to low
> for some reason. You may want to try increasing the memory size of POV-Ray
> in the Finder. For the scene that crashes near a mosaic preview level of 2,
> try to just double the maximum memory (and make sure POV-Ray really got that
> much memory) and try it again - does it still crash?

I do use the default settings, but my scenes have so far been exceedingly
simple, since I'm still trying to get the hang of things. I can try doubling
the memory, though...

-Xplo

Post a reply to this message