POV-Ray : Newsgroups : povray.unofficial.patches : i_dat3d & *.df3 Server Time
2 Sep 2024 02:13:21 EDT (-0400)
  i_dat3d & *.df3 (Message 1 to 10 of 11)  
Goto Latest 10 Messages Next 1 Messages >>>
From: ingo
Subject: i_dat3d & *.df3
Date: 28 Jul 2000 15:52:34
Message: <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.

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

From: Ron Parker
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 15:56:00
Message: <slrn8o3q2n.o8l.ron.parker@fwi.com>
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

From: ingo
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 16:11:40
Message: <8F7FE26EBseed7@204.213.191.228>
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

From: Ron Parker
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 16:40:25
Message: <slrn8o3sm0.oba.ron.parker@fwi.com>
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

From: ingo
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 17:02:34
Message: <8F7FE8B08seed7@204.213.191.228>
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

From: Chris Huff
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 17:58:29
Message: <chrishuff-320CA7.16591628072000@news.povray.org>
In article <8F7FE26EBseed7@204.213.191.228>, ing### [at] homenl (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] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: ingo
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 18:16:43
Message: <8F80366Dseed7@204.213.191.228>
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

From: david sharp
Subject: Bug: Re: i_dat3d & *.df3
Date: 28 Jul 2000 18:56:57
Message: <39820fb9$1@news.povray.org>
ingo <ing### [at] homenl> 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

From: Chris Huff
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 19:16:00
Message: <chrishuff-83377C.18164628072000@news.povray.org>
In article <8F80366Dseed7@204.213.191.228>, ing### [at] homenl (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] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/


Post a reply to this message

From: david sharp
Subject: Re: i_dat3d & *.df3
Date: 28 Jul 2000 19:27:29
Message: <398216e1$1@news.povray.org>
Ron Parker <ron### [at] povrayorg> 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

Goto Latest 10 Messages Next 1 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.