 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ron Parker" <ron### [at] povray org> schrieb im Newsbeitrag
news:slr### [at] fwicom...
> It's always been impossible to have more than 256 entries in a blend map;
> I'm not sure where the 128 you mention comes from.
It may come from my example because I put in 2 blend map entries per loop.
That's why POV-Ray gives a parse error after 128 loops in this scene.
So long,
Bonsai
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bonsai" <bon### [at] b0n541net> wrote in message
news:3bab4cf8@news.povray.org...
> "Ron Parker" <ron### [at] povrayorg> schrieb im Newsbeitrag
> news:slr### [at] fwicom...
> > It's always been impossible to have more than 256 entries in a blend
map;
> > I'm not sure where the 128 you mention comes from.
>
> It may come from my example because I put in 2 blend map entries per loop.
> That's why POV-Ray gives a parse error after 128 loops in this scene.
Oh yeah, okay, I see that now. I just through the number 0.0079 into the
calculator thinking 1/0.0079 (or 0.0078) would be around 128. I ignored the
double entry. It is of course still only just greater that 128 and 126
respectively. So somethings wrong there when it crashes at >128.
Sorry Ron, I was sure you were the author of the cells pattern and I had no
idea you were not. Just so everyone knows besides me know who did, that
would be John VanSickle.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Sep 2001 11:27:34 -0500, Bob H. wrote:
>Sorry Ron, I was sure you were the author of the cells pattern and I had no
>idea you were not. Just so everyone knows besides me know who did, that
>would be John VanSickle.
I'm sure you got that notion because I am responsible for crackle solid and
all of the other changes to crackle in 3.5. I'm not really upset, just
don't want anyone who is in a position to fix the problem to shy away because
they think I'll look at it.
That's not to say I *won't* look at it, just to say that if someone else
gets to it first I don't want to discourage them from fixing it instead.
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ron Parker" <ron### [at] povrayorg> wrote in message
news:slr### [at] fwicom...
> On Fri, 21 Sep 2001 11:27:34 -0500, Bob H. wrote:
> >Sorry Ron, I was sure you were the author of the cells pattern and I had
no
> >idea you were not. Just so everyone knows besides me know who did, that
> >would be John VanSickle.
>
> I'm sure you got that notion because I am responsible for crackle solid
and
> all of the other changes to crackle in 3.5. I'm not really upset, just
> don't want anyone who is in a position to fix the problem to shy away
because
> they think I'll look at it.
Yep, crackle I was certain of and you had mentioned cells enough for me to
associate you with it.
I checked and found that the last post around here by John was on the 7th of
this month to say he was leaving for a trip and wouldn't even be getting the
Beta of POV 3.5 to take along with him. Been two weeks now so wonder if
he'll soon see about this? (talking to myself)
> That's not to say I *won't* look at it, just to say that if someone else
> gets to it first I don't want to discourage them from fixing it instead.
Ideally of course every feature's author would be the fix-it person. Or
better yet, someone with extra know-how because I suppose troubleshooting
often goes beyond the part added into the source. Goes without saying. I
can only admire from afar.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob H. wrote:
>I checked and found that the last post around here by John was on the 7th of
>this month to say he was leaving for a trip and wouldn't even be getting the
>Beta of POV 3.5 to take along with him. Been two weeks now so wonder if
>he'll soon see about this? (talking to myself)
>
IIRC, John VanSickle is working for the Pentagon, so he may have some
other concerns right now.
And no, he's not in the (partial) missing person lists.
G.
--
**********************
http://www.oyonale.com
**********************
Graphic experiments
Pov-ray gallery
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Gilles Tran" <tra### [at] inapginrafr> wrote in message
news:3BA### [at] inapginrafr...
> >
> IIRC, John VanSickle is working for the Pentagon, so he may have some
> other concerns right now.
> And no, he's not in the (partial) missing person lists.
I forgot that, thinking I remember something to that effect too.
Real glad you also said the last part too, thanks.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gilles Tran wrote:
> IIRC, John VanSickle is working for the Pentagon, so he may have some
> other concerns right now.
John was working at the Pentagon but was transfered or relocated to
Germany several months ago. I think he is simply taking a vacation
right now.
--
Ken Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bonsai" wrote:
> Now there are no parsing errors but POV-Ray crashed
> immediately after the render window appeared. After
> reloading POV-Ray and restarting the rendering without
> any change on the scene file it renders fine. No problems.
> Very strange! :-(
I can confirm this bug.
Furthermore:
The bug also manifests itself if the texture is only declared but never
invoked. However, the crash happens after the render window appears, as
Bonsai pointed out.
The bug also manifests itself using a pigment_map, but not with a color_map.
After having rendered with i = i+0.0078 you can increase 0.0078 with any
number, and the bug still happens. For example you can change it to 0.1.
This code is enough to reproduce the bug:
#declare M =
pigment {
wood
pigment_map {
#declare i = 0;
#while (i<1)
[i, color rgb i]
#declare i = i + 0.0078;
[i, color rgb i]
#end
}
}
I'm using POV-Ray 3.5 beta 4
on a P150, 16MB RAM
Windows 95 4.00.450 B IE 5 5.00.2919.6307
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Bonsai who wrote:
>Hi,
>
>my machine is a PIII 450 MHz, 128 MB RAM and WinNT 4.0 Service Pack 5,
>POV-Ray 3.5 Beta 2
>
>The following code gives a parse error: Blend_Map too long
>
>// Start of code //
>#version 3.5;
>camera {location <10, 10, -10> look_at <0.5, 0.5, 0.5>}
>light_source {<10, 10,-10> color rgb 1}
>
>plane {<0, 1, 0>, 0
> texture {cells
> texture_map
> {
> #declare i = 0;
> #while (i <= 1)
> #declare my_color = color rgb i
> [i pigment{my_color}]
> #declare i = i + 0.0078;
> [i pigment{my_color}]
> #end
> }
> }
> }
>// End of code //
>
>O.k. there are too many texture_map items.
>Then I changed the #declare of "i" in the #while loop to:
>
>#declare i = i + 0.0079;
> ^^^^^^
>Now there are no parsing errors but POV-Ray crashed immediately after the
>render window appeared. After reloading POV-Ray and restarting the rendering
>without any change on the scene file it renders fine. No problems. Very
>strange! :-(
I've just been doing a bit of checking through the known bugs list, and
can't seem reproduce this in beta 7. It was confirmed in beta 2 and
beta 4.
I reckon that it's now fixed and intend to remove it from the known bugs
list.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mike Williams" <mik### [at] nospamplease> schrieb im Newsbeitrag
news:qscdECA5WnA8Ew$A@econym.demon.co.uk...
> I've just been doing a bit of checking through the known bugs list, and
> can't seem reproduce this in beta 7. It was confirmed in beta 2 and
> beta 4.
> I reckon that it's now fixed and intend to remove it from the known bugs
> list.
I can't reproduce the crash either.
So long,
Bonsai
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
