Hello everyone.
I tried the beta 35, since I got an error message about expiration of version
34, since january 1st.
Unfortunately, I discovered a quite serius bug in beta 35.
Any cone will have both ends with the sign of every coordinate changed!
This doesn't happen with version 34.
For example, try:

cylinder{0,10*x,0.02 pigment{color x}}
cylinder{0,10*y,0.02 pigment{color y}}
cylinder{0,10*z,0.02 pigment{color z}}

camera
{
   location 3
   right x*16/9
   direction x*2
   sky z
   up y
   look_at 0
}

cone{<0,0,0>,0,<1,0,0>,0.3 pigment{color rgb 1}}
light_source{10 color rgb 1}


I hope this will be fixed as soon as possible.
In the meanwhile, I will try to uninstall beta 35 and install back version 34.

Thank you.
Best regards.
                   Rosso5

Post a reply to this message

Le 04/01/2010 19:02, Rosso5 nous fit lire :
> Hello everyone.

> I hope this will be fixed as soon as possible.
> In the meanwhile, I will try to uninstall beta 35 and install back version 34.
> 

It's all my fault. Sincerely. Sorry.

I forget to add a

VScaleEq(axis, -1.0);

inside


  if (apex_radius < base_radius)
  {
    /* Want the bigger end at the top */

    Assign_Vector(tmpv,base);
    Assign_Vector(base,apex);
    Assign_Vector(apex,tmpv);

    tmpf = base_radius;
    base_radius = apex_radius;
    apex_radius = tmpf;
    VScaleEq(axis, -1.0);  // Missing: opposite axis
  }

in cones.cpp::Cone::Compute_Cone_Data() (circa line 866)

Previously, axis was computed after that inversion.
It is now computed before, because I needed the length of the cone a bit
before.



> Thank you.
> Best regards.
>                    Rosso5

Post a reply to this message

Thank you for your ready answer.
So, if I have well understood, it will be fixed in the new release, right?
Do you know when? Sorry, I don't know if there is any established rule about
date publication for every release.
Thank you so much.
                     Rosso5

Post a reply to this message

I'll do a new release to fix this issue in the next day or two.

-- Chris

Post a reply to this message

Thank you very much, Chris.

I asked also because the version 34 doesn't allow anymore to make any render.
I get the message "Please obtain an update version of this application" even if
I have just done the "Extend" after the application launch.
The only way is to modify the date/time in computer clock. Or otherwise, to use
version 3.6.2, but it is quite slower than 3.7 one.
I have to generate a lot of frames with the Death Star...

Best regards.
                     Rosso5

Post a reply to this message

On Tue,  5 Jan 2010 15:29:37 EST
"Rosso5" <rem### [at] hotmailcom> wrote:

> I asked also because the version 34 doesn't allow anymore to make any
> render.

See the source download page for a small mod to be made to just one file.
This re-enables beta34.

John

Post a reply to this message

John Coppens <joh### [at] johncoppenscom> wrote:
> On Tue,  5 Jan 2010 15:29:37 EST
> "Rosso5" <rem### [at] hotmailcom> wrote:
>
> > I asked also because the version 34 doesn't allow anymore to make any
> > render.
>
> See the source download page for a small mod to be made to just one file.
> This re-enables beta34.
>
> John
Thank you John, but I think you are referring to the note in Unix/Linux section:
Note: to get the Linux beta 34 source to work after 31 December 2009...

In my case, I'm using PoV on Windows, ver. 3.7 beta 34 & 35.
Maybe I should have specified this first, sorry.

Best regards.
                  Rosso5

Post a reply to this message