Some strange behavior I observed in the Mac GUI related to partial image
rendering (I don't know if that's your priority at the moment, I thought I'd
report it anyway):

In a scene file that has its render settings set to "Default" (either
because it doesn't contain settings resources or because you chose "Default"
from the popup in the Render Settings dialog), if you turn on partial
rendering either from the Render Settings dialog or from the image window
widget (but don't change the partial image size that is initially set to
cover the whole image) and then try to render, it fails to parse and render
outputting "Could not find file 'OBJECT.POV'" (sic!) and "Cannot open input
file".

It works normally however after the first time you change the partial image
size (in the image window or in the Render Settings dialog), even if you
change it back to full image as it was.

If the scene is in such a state where it doesn't render, and you then switch
on antialiasing, it suddenly does render, but without antialiasing. It seems
that antialiasing is on from the point of view of the GUI (as seen in the
render settings dialog) but off from the point of view of the renderer (as
seen in the console output and of course the image). The same thing when you
start with antialiasing on with an image rendering normally and then you
switch on partial image rendering without changing the initial size.

Summarized, there seems to be something wrong with the initial partial image
size that gets set when you switch on partial image rendering with no
previous partial image size set.

The whole thing is still a little obscure to me and I don't know if I've
figured it all out. But let's first see what the people in knowledge of the
source have to say.

And one other little thing I found out when investigating the above: If
partial image rendering is on and you go to the Render Settings dialog and
choose "Default" from the popup, the image window doesn't reflect the fact
that partial image rendering is off now.

 -Christian

Post a reply to this message

Hello? No Mac users around here? I'm still waiting for any comments to my
post about "Mac GUI partial image oddities" (2002/01/27,
http://news.povray.org/povray.beta-test/21765/). Or is my formulation just
so intimidatingly complex? :)

Thorsten? I don't expect you to have it all fixed until tomorrow, I'd just
like to know that you took note of my report, and let me know if I can help
in any way.

 -Christian

Post a reply to this message

In article <B87D98C6.2B73%cwa### [at] gmxch> , Christian Walther 
<cwa### [at] gmxch>  wrote:

> Hello? No Mac users around here? I'm still waiting for any comments to my
> post about "Mac GUI partial image oddities" (2002/01/27,
> http://news.povray.org/povray.beta-test/21765/). Or is my formulation just
> so intimidatingly complex? :)

Probably :-)

> Thorsten? I don't expect you to have it all fixed until tomorrow, I'd just
> like to know that you took note of my report, and let me know if I can help
> in any way.

I was waiting for someone to confirm it at all.  I am neither able to
reproduce it nor does the code do anything that could cause this.  It could
just be that your preferences are corrupted.


    Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

> I am neither able to reproduce it...

I am: I just did the following on an iMac (G3 400MHz, 320MB RAM, MacOS 9.2.2
US) that has never seen POV-Ray in its life:

o download and install a fresh copy of POV-Ray

o doubleclick "perspective.pov" from scenes: camera:

o add the "include" folder to the Include Paths in the Preferences dialog

o open the render settings dialog, go to the "Output" tab, check the
"Partial Image" box, and close the dialog


open input file." in the Messages window with a stop sign in front of each.

o open the render settings dialog, go to the "Quality" tab, check the
"Anti-Aliasing" box, and close the dialog


Messages window says in the last "Tracing Options":
"Antialiasing.........Off"

o open the render settings dialog, go to the "Output" tab, click "Set Size",
delete the zero of "120", type it again, click "OK" and close the dialog.



o open the render settings dialog, choose "Default" from the popup, close
the dialog

o click on the partial image widget in the image window that is still
activated to deactivate it, then once again to activate it again

o start a render - Could not find file 'OBJECT.POV'.


> ...nor does the code do anything that could cause this.

I've just found out that "OBJECT.POV" is the default filename the renderer
assumes when it doesn't get any other, so this too seems to be a problem of
arguments not getting passed correctly from the GUI to the renderer. (OK,
you probably knew that, so take it as a loud thought rather than a helpful
hint :) )

> It could just be that your preferences are corrupted.

Not likely, as the above shows. And trashing the prefs didn't help on my
powerbook (G3 266, 192MB RAM, MacOS 9.2.2 US, by the way), where I
originally observed the problem, either.

Good luck in locating that bug, don't feel pressed by me, and let me know if
I can do anything to help you!

 -Christian

Post a reply to this message

I'd just like to note that my "partial image oddities" persist in beta 11. I
have now tried it on my powerbook (G3 266MHz, 192MB RAM) with both MacOS
9.2.2 US and MacOS X 10.1.2, as well as on a Performa 5320 (603e 112MHz,
64MB RAM, MacOS 8.1 german), and behavior is exactly the same everywhere (as
described in <B87F2405.2B8D%cwa### [at] gmxch>, 2002/01/31,
http://news.povray.org/povray.beta-test/21765/).

Post a reply to this message