![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
1. Is there a limit to the size of a df3 file that can be used with
"i_dat3d"? A 100^3 file parses ok. A 150^3 file gives the error:
#declare Func={"data_3d_3",<1> library "i_dat3d",
"pytest.df3",<150,150,150,5> <----- Error
..\box_erode.pov:62 error: out of memory, cannot allocate -4764052 bytes
for Lib.
2. All I get when using a df3 with "i_dat3d" is no object or a white box.
Can somebody show me the function working with spiral.df3 (from the
standard pov).
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 28 Jul 2000 15:52:34 -0400, ingo wrote:
>2. All I get when using a df3 with "i_dat3d" is no object or a white box.
>Can somebody show me the function working with spiral.df3 (from the
>standard pov).
Is i_dat3d supposed to work with df3 files? I thought it used a more
human-readable format.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ron Parker wrote:
>Is i_dat3d supposed to work with df3 files?
Yes, I think David Sharp added that part.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 28 Jul 2000 16:11:40 -0400, ingo wrote:
>Ron Parker wrote:
>
>>Is i_dat3d supposed to work with df3 files?
>
>Yes, I think David Sharp added that part.
Why is it necessary? Can't you just use the pigment function with a
pigment defined by the df3 file?
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ron Parker wrote:
>Why is it necessary? Can't you just use the pigment function with a
>pigment defined by the df3 file?
>
Can't answer the first question. For the second one, just wanted to
compare the speed and output of both methods.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <8F7FE26EBseed7@204.213.191.228>, ing### [at] home nl (ingo)
wrote:
> >Is i_dat3d supposed to work with df3 files?
>
> Yes, I think David Sharp added that part.
I'm not sure, but I think all that was added was the ability to use an
array as i_dat3d input. I think you have to use a pigment function to
get df3 files to be useable in isosurfaces.
--
Christopher James Huff - Personal e-mail: chr### [at] mac com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff wrote:
>I'm not sure, but I think all that was added was the ability to use an
>array as i_dat3d input. I think you have to use a pigment function to
>get df3 files to be useable in isosurfaces.
>
From the doc for WinMegaPov:
The final vector <32,32,16,0> contains the parameters for the i_dat3d
library. : <L0,L1,L2,L3>
<snip>
sample parameters.
from the DF3 file's header and just ignore the sample parameters found in
the llibrary parameter vector <Nx,Ny,Nz,6>
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
ingo <ing### [at] home nl> wrote in message
news:8F7FD9A61seed7@204.213.191.228...
> 1. Is there a limit to the size of a df3 file that can be used with
> "i_dat3d"? A 100^3 file parses ok. A 150^3 file gives the error:
>
> #declare Func={"data_3d_3",<1> library "i_dat3d",
> "pytest.df3",<150,150,150,5> <----- Error
> ..\box_erode.pov:62 error: out of memory, cannot allocate -4764052 bytes
> for Lib.
The cause is a bug in the initialization.
The MegaPOV 0.5 source level fix is to change line 1216 in isosurf.c from
char df3header[6];
to
unsigned char df3header[6];
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <8F80366Dseed7@204.213.191.228>, ing### [at] home nl (ingo)
wrote:
> From the doc for WinMegaPov:
> The final vector <32,32,16,0> contains the parameters for the i_dat3d
> library. : <L0,L1,L2,L3>
...snip...
I stand (well, sit) corrected.
Hmm, does the interpolation of the i_dat3d library differ from the df3
pattern interpolation?
--
Christopher James Huff - Personal e-mail: chr### [at] mac com
TAG(Technical Assistance Group) e-mail: chr### [at] tag povray org
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ron Parker <ron### [at] povray org> wrote
> Why is it necessary? Can't you just use the pigment function with a
> pigment defined by the df3 file?
The df3 reading was added to the dat3d/dat2d functions just because
it seemed logical that as long as there already existed a POV 3d data
format, the dat3d/2d functions should be able to use it.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |