 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
yesbird <sya### [at] gmail com> wrote:
> On 15/03/2025 11:00, Paul Bourke wrote:
> > And more importantly, how to fix or get around it?
> >
>
> Successfully rendered this scene (see attached image), but have a lot of
> warnings:
> ------------------------------------------------------------------------
> "C:\temp\pb\scene.pov" line 33: Possible Parse Error: Suspiciously high
> 'ambient' value found. Are you trying to model a glowing material? As of
> POV-Ray v3.7, 'ambient' is disabled when using radiosity, and its use to
> model glowing materials is generally deprecated;
> use 'emission' for this purpose instead. If your intention is to model
> unusually high ambient illumination in a non-radiosity scene, you can
> avoid this warning by explicitly specifying 'emission 0'.
> ------------------------------------------------------------------------
>
> POV-Ray version:
> https://github.com/LeForgeron/povray
>
> System:
> OS Name Microsoft Windows 7
> Version 6.1.7601 Service Pack 1 Build 7601
> Total Physical Memory 24.0 GB
>
> Log in attachment.
> --
> YB
But did you increase theradius to 0.1?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
kurtz le pirate <kur### [at] freefr> wrote:
> On 15/03/2025 11:14, Paul Bourke wrote:
> > "Paul Bourke" <pau### [at] gmailcom> wrote:
> >> Any ideas why this scene
> >> https://paulbourke.net/transient/povray/
> >> crashes once "theradius" gets past a certain value, eg: 0.6. There are no
> >> coincident points, running version 3.7 on MacOS. Tonnes of RAM (192GB) and only
> >> a fraction is used.
> >> And more importantly, how to fix or get around it?
> >
> > Also happens for beta 3.8, but at different values of "the radius".
> >
>
> IMHO, this comes from using the <disk> object.
>
> Have you tried using the <cylinder> object instead ?
I just tried it, didn't make any difference, still crashes, in fact crashes more
reliably now. Here's the new DoPoint macro.
#macro DoPoint(theposition,thecolour)
#local thenormal = vnormalize(VP-theposition);
#local thedistance = vlength(VP-theposition);
#if (thedistance > 0.2) // Filter any points close to the camera
#if (thedistance < 30) // Filter any distant outliers
#local theradius = 0.05;
cylinder {
<0,0,0>, thenormal/100, 0.95
//hollow
texture {
pigment {
onion
colour_map {
[0.00, rgb thecolour transmit 0]
[0.20, rgb thecolour transmit 0.95]
[1.00, rgb thecolour transmit 1]
}
}
finish { emission 0 ambient 1 diffuse 0 specular 0 }
}
scale theradius
translate theposition
}
#end
#end
#end
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Paul Bourke" <pau### [at] gmailcom> wrote:
> > Any ideas why this scene
> > https://paulbourke.net/transient/povray/
> > crashes once "theradius" gets past a certain value, eg: 0.6. There are no
> > coincident points, running version 3.7 on MacOS. Tonnes of RAM (192GB) and only
> > a fraction is used.
> > And more importantly, how to fix or get around it?
>
> I would say that you're pushing up against certain hard-coded values in 3.7.
> Also, people have made a very good (and non-obvious) point about the disc object
> having an inside.
>
> Although you could use cylinders, I used spheres, but I put them all inside a
> blob {} statement to get a speed boost from the special bounding mechanism.
>
> It takes maybe 15 sec to parse that huge inc file, and then FOR-EVER to try and
> render it.
> That's coming from the transmit values in your pigment map.
> Setting all of those to 0 allows the scene to render in 45s on my machine.
>
> The only other things I can think of to perhaps make the scene render faster and
> with less memory usage, are to sort the disc/sphere/blobs by color (perhaps with
> some rounding) so that you can use a single texture statement for each group of
> similarly colored object, thereby saving memory.
> Also, you could sort by distance from the camera, and only give the nearest
> objects a transmit pigment, so you wouldn't have so many layers of transmit to
> deal with, though perhaps setting max_trace_level to a lower value would
> essentially accomplish the same task.
>
> Pretty cool idea - and I hope to see the final animation once it's all working!
>
> - BW
Thanks for the suggestions. I am now rendering in 3.8, only takes about 20s and
that's with an even bigger inc file. But speed isn't an issue for me, at least
with 3.7 since I can distribute it. The 3.8 I downloaded has the gui (MacOS), is
there a pure command line for 3.8? Can't efficiently do a distributed render
with the gui.
See previous message, tried cylinders and spheres (3.7), same problem.
There are also nasty defects in the 3.8 render (discs), see attached example
frame. Strange they are mostly on the right half, it's those narrow dark
slivers. Perhaps they are a cue to what's happening.
Post a reply to this message
Attachments:
Download 'scene120.png' (1797 KB)
Preview of image 'scene120.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just changed the disks to plain spheres (no blob) and set max_trace_level to
2, and it rendered just fine in 20s.
I'm guessing maybe it's something in 3.7.
I'll keep bumping up the MTL and see what happens.
Post a reply to this message
Attachments:
Download 'scene.png' (1115 KB)
Preview of image 'scene.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Paul Bourke" <pau### [at] gmailcom> wrote:
> Thanks for the suggestions. I am now rendering in 3.8, only takes about 20s and
> that's with an even bigger inc file. But speed isn't an issue for me, at least
> with 3.7 since I can distribute it.
Well, I was juggling making the kid dinner + other stuff + Bourke-level POV-Ray
creativity, so I wanted to get a finished render so that I could get a better
overall idea of what was going on.
> The 3.8 I downloaded has the gui (MacOS), is
> there a pure command line for 3.8? Can't efficiently do a distributed render
> with the gui.
Yes Sir.
I just ran [Path] pvengine64 /RENDER scene.pov, and that seemed to work fine
under M$ Win 7
> See previous message, tried cylinders and spheres (3.7), same problem.
>
> There are also nasty defects in the 3.8 render (discs), see attached example
> frame. Strange they are mostly on the right half, it's those narrow dark
> slivers. Perhaps they are a cue to what's happening.
Dunno. If they're disks or something, maybe somehow they got oriented wrong,
and they're dark colors in front of light?
I just tried again with spheres that are scaled by 0.01 in x, so that they
resemble your original disc. Can't tell if the lines are there.
What resolution are you rendering at?
- Bill
Post a reply to this message
Attachments:
Download 'scene.png' (1239 KB)
Preview of image 'scene.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> I just tried again with spheres that are scaled by 0.01 in x, so that they
> resemble your original disc. Can't tell if the lines are there.
> What resolution are you rendering at?
"Just download the render at look at the image size, Bill."
<eyeroll>
Take a look at this and see what you think.
Post a reply to this message
Attachments:
Download 'scene.png' (976 KB)
Preview of image 'scene.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Never mind that last one.
I flattened the spheres and then rotated them so that they were perpendicular to
the camera.
Try this and see if this gets you anywhere better.
#macro Reorient_Trans(Axis1, Axis2)
#local vX1 = vnormalize(Axis1);
#local vX2 = vnormalize(Axis2);
#local Y = vcross(vX1, vX2);
#if(vlength(Y) > 0)
#local vY = vnormalize(Y);
#local vZ1 = vnormalize(vcross(vX1, vY));
#local vZ2 = vnormalize(vcross(vX2, vY));
transform {
matrix < vX1.x, vY.x,vZ1.x, vX1.y,vY.y,vZ1.y, vX1.z,vY.z, vZ1.z, 0,0,0
>
matrix < vX2.x,vX2.y,vX2.z, vY.x,vY.y, vY.z, vZ2.x,vZ2.y,vZ2.z, 0,0,0
>
}
#else
#if (vlength(vX1-vX2)=0)
transform {}
#else
#local vZ = VPerp_To_Vector(vX2);
transform { Axis_Rotate_Trans(vZ,180) }
#end
#end
#end
#macro DoPoint(theposition,thecolour)
#local theradius = 0.2;
sphere{<0,0,0>, 0.2 //, 0.05
//disc{<0,0,0>, VP-theposition, 1
texture {
pigment {
onion
colour_map {
[0.00, rgb thecolour transmit 0]
[0.20, rgb thecolour transmit 0.95]
[1.00, rgb thecolour transmit 1]
}
}
finish { emission 1 diffuse 0 specular 0 }
}
scale <0.01, 1, 1>
Reorient_Trans(x, vnormalize(VP-theposition))
scale theradius
translate theposition
}
#end
Post a reply to this message
Attachments:
Download 'scene.png' (678 KB)
Preview of image 'scene.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Even if I abandon solids and just create a polygon at each position, Povray
crashes as soon as I scale the polygon up past a certain amount. Is there
possibly an issue if too many objects overlap?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Paul Bourke" <pau### [at] gmailcom> wrote:
> Even if I abandon solids and just create a polygon at each position, Povray
> crashes as soon as I scale the polygon up past a certain amount. Is there
> possibly an issue if too many objects overlap?
I personally am not having that issue.
I have #local theradius = 1;
and it's still just chugging along fine.
It's just a cheap HP EliteDesk i5 with 16GB RAM
Of course, I'm using an edited version of the original...
Maybe it's the Apple version?
Post your current scene and I'll run it unedited.
-BW
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16/03/2025 01:37, Paul Bourke wrote:
> .... and you increased theradius to 0.1?
>
This is what I got with theradius = 0.1 and no crash.
--
YB
Post a reply to this message
Attachments:
Download 'scene0000.png' (2021 KB)
Preview of image 'scene0000.png'
|
|
| |
| |
|
|
|
|
| |
|
|
