|  |  | 
|  |  |  |  | 
|  |  | 
|  |  | 
|  |  |  |  | 
|  |  | 
|  |  | 
|  |  | POV 3.5 RC2 icl on WinNT Sp 6 PII 233 with 128 MB
I have reported several porblems around splines in RC1in some thread last week
but they were probably a little trivialized becouse of "still being worked on"
status. Now Splines are on "Fixed bugs" list so I can focus some things.
For tests I have used the same source I posted in
http://news.povray.org/m7fq3u41ctia9e6i3tbnlstn6ek739vpke%404ax.com
but I only limited range in Draw() macro from:
      #local c=1;
      #while (c<=(Points-Step))
      :
      sphere{Spline(Points Force()) Radius}
to:
      #local c=2;
      #while (c<=((Points-1)-Step))
      :
      sphere{Spline((Points-1) Force()) Radius}
becouse of smaller number of "real" points for cubic spline.
Experimenting script was designed to render two rows of spline in following
order:
    linear cubic cubic linear forced_cubic 
    cubic linear linear cubic forced_cubic
So problems are now:
- forcing cubic_spline at moment of calculation not work - that's probably
  bug in parser becouse it not accepts cubic_spline where it expects
  cubic_spline - error is:
      ,cubic_spline <----ERROR
      Parse Error: linear_spline, quadratic_spline, natural_spline,
      or cubic_spline expected.
  for further tests I commented content of Force() macro to not force
  cubic_spline then
- first column - pure definition - works fine
- second column - copying spline with changing type and all points
  redefinition - works wrong
- third column - copying spline with changing type - works wrong
- fourth column - copying spline with additional point - works fine
- fifth column - forcing type at calculation time - can't be tested becouse
  described above bug
ABX
Post a reply to this message
 |  | 
|  |  | 
|  |  | 
|  |  | 
| From: Thorsten Froehlich Subject: Re: spline problems still not solved
 Date: 22 Apr 2002 13:37:30
 Message: <3cc44a5a@news.povray.org>
 
 |  |  | 
|  |  | 
|  |  | 
|  |  | 
Skiba <abx### [at] babilon org>  wrote:
> - forcing cubic_spline at moment of calculation not work - that's probably
>   bug in parser becouse it not accepts cubic_spline where it expects
>   cubic_spline - error is:
>       ,cubic_spline <----ERROR
>       Parse Error: linear_spline, quadratic_spline, natural_spline,
>       or cubic_spline expected.
>   for further tests I commented content of Force() macro to not force
>   cubic_spline then
> - fifth column - forcing type at calculation time - can't be tested because
>   described above bug
Use the old keyword "catmull_rom_spline"; it had still been in this place in
the parser.
> - second column - copying spline with changing type and all points
>   redefinition - works wrong
> - third column - copying spline with changing type - works wrong
The same problem as the spline type is simply not changed.
    Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf  de
Visit POV-Ray on the web: http://mac.povray.org Post a reply to this message
 |  | 
|  |  | 
|  |  | 
|  |  |  |  | 
|  |  | 
|  |  | 
|  |  | POV 3.5 RC2 icl on WinNT Sp 6 PII 233 with 128 MB
In RC3 neither old catmull_rom_spline nor new cubic_spline not work in forcing
type in evaluation spline. Sample script:
  #local S=spline{0 x 1 y 2 z 3 1}
  #local V=S(2);
  #local V=S(2,linear_spline);
  #local V=S(2,quadratic_spline);
  #local V=S(2,natural_spline);
  #local V=S(2,cubic_spline);
  #local V=S(2,catmull_rom_spline);
ABX
Post a reply to this message
 |  | 
|  |  | 
|  |  | 
|  |  | 
| From: Thorsten Froehlich Subject: Re: still can't force type of spline
 Date: 30 Apr 2002 08:24:42
 Message: <3cce8d0a@news.povray.org>
 
 |  |  | 
|  |  | 
|  |  | 
|  |  | 
Skiba <abx### [at] babilon org>  wrote:
>   #local V=S(2,cubic_spline);
Use "cubic" for now, I copied the wrong token name...
    Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf  de
Visit POV-Ray on the web: http://mac.povray.org Post a reply to this message
 |  | 
|  |  | 
|  |  | 
|  |  |  |  | 
|  |  |