|
|
I can't verify this yet but I found a scene file of mine won't render and
just stalls out at the start of a render as the timer continues.
When I comment out some lights it renders as it should, so I attempted to
recreate the problem in a very simplified way by putting a light within a
two nested unions, like the problem scene file has. That renders okay, so
I'm not able to explain this possible problem any further. I thought it
might be a good idea to post here about it anyhow if someone else encounters
this kind of stalling or freezing of the render process.
Another side effect of this is that the toolbar buttons grey out after
interrupting the render and don't return until closing then restarting.
beta 12a on XP
Post a reply to this message
|
|
|
|
"StephenS" <sshonfield(at)ottawa(dot)net> wrote in message
news:442de37f$1@news.povray.org...
> ...
> I have a scene that shows this behavior.
> Do you use radiosity? Removing this from my scene helped it along. I only
> waited 2 hours and the scene used to take 20 minutes with v3.6.
Radiosity and photons are within #if's and commented out all of it afterward
to check that they weren't being read anyway somehow. You have me thinking
about any temporary files and now I've deleted the pov-state file and
retried... same thing happens.
I gave a misleading description of the toolbar before, sorry. Only the Ini,
Sel-Run, Stop, Pause buttons (and command-line) go grey and are unclickable
after first pressing Stop in an attempt to abort the stalled render. Of
course, Pause would do that anyhow. Yet all other functions seem okay since
editing and saving a file is still possible.
I haven't let the render sit there stalled for very long because it would
normally appear in the display window within seconds, although tried to let
it go a few minutes to be sure something was indeed wrong.
Thought I had tracked it down to a pair of nested differences but, again, I
can't duplicate the problem even when using almost the same SDL script in a
test file. So far a complete mystery to me.
Post a reply to this message
|
|