 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Stop during mosaic: crash
> http://news.povray.org/Xns9126925CDC108seed7@povray.org
Further to this bug, I've noticed that it only seems to happen with PNG
output, (when I use TGA or BMP it doesn't crash).
-tgq
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
What about that
"[Bug] Output of too many evaluations cause strange behaviour" and the
Sidenote to it I reported 8 oct?
The symptoms changed a bit in beta 6, but the blank message window remained,
the status bar reports still wrong rendertimes and another render afterwards
is not possible (the render window disappears no longer, though until you
start another render).
And without the camera "Too many nested objects" are still reported.
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bc73596@news.povray.org> , "Rune" <run### [at] mobilixnet dk>
wrote:
> Stop during mosaic: crash
> http://news.povray.org/Xns9126925CDC108seed7@povray.org
> Crash when stopping in the first line
> http://news.povray.org/1103_1002737295@iq
> (Also reported as: Radiosity crash when user stops render during pretrace.)
> http://news.povray.org/3bb4605d$1@news.povray.org
AFAIK these three are the same.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
You didn't add the one I suggested:
Using antialiasing method 1 and +ua at the same time makes rendering
abnormally slow (with method 2 the rendering time is perfectly normal).
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
> AFAIK these three are the same.
Got it, thanks.
Rune
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" wrote:
> You didn't add the one I suggested:
Sorry, I forgot.
Rune
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When using radiosity and selected area rendering I found that the radiosity
will keep being done even after a change to the file and save. Only returns
to normal when the entire render window is used again. I won't conjecture
if it has to do with the radiosity mosaic crash.
beta.6, WinME, PIII
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rune wrote:
>
> Rendering animation (MS Windows)
> (Message that indicates the frame to be render is displayed AFTER the
> rendering.)
> http://news.povray.org/3BAC1D0C.74A4A503@free.fr
This appears to be a problem in 3.1g as well.
Regards,
John
--
ICQ: 46085459
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just came across this bug, which is still present in beta 6:
Resising the rendering window
http://news.povray.org/3BA3BE6A.FE29C513@free.fr
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Anders K." <and### [at] f2scom> wrote in message news:3bcca991$1@news.povray.org...
> Just came across this bug, which is still present in beta 6:
>
> Resising the rendering window
> http://news.povray.org/3BA3BE6A.FE29C513@free.fr
This is now fixed.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
