Related to the Flyspray feature request #305;
remove maximum component limit for blobs (1M)

Start an array [736][350][736]
....fails on 32bit WinXP, run on 64bit WinVista
Initilize array element based on trace to mesh()
Create a blob component only if on surface.
....scan array, check for 6 face elements = fully inside, no component used

Full run, under 15 hours with 2.8Mhz cpu
array elements = 43,585,544
blob components = 2,826,336 <<<<<<<<<
Saved files:
array 1.64G
object 131M
about 3hrs to create array
about 11-12hrs to select points to use
trace 2min


Use results run,
Read object(blob) file and trace
4min

Comments welcome:

Stephen S

Post a reply to this message

Attachments:
Download 'blobinator_g_test.png' (349 KB)

Preview of image 'blobinator_g_test.png'

"StephenS" <nomail@nomail> wrote:
> Related to the Flyspray feature request #305;
> remove maximum component limit for blobs (1M)
....

Forgot to say, used:
Pov-Ray v 3.7.0.20140613.unofficial.msvc10.win64
from winpov help about

This should be Uberpov, but not sure what version.

Will update to latest and continue to play.

Stephen S

Post a reply to this message

Hi(gh)!

On 16.02.2015 14:21, StephenS wrote:
> Start an array [736][350][736]
> ....fails on 32bit WinXP, run on 64bit WinVista

Perhaps you should have tried Linux - I experienced a slightly better 
memory use under Linux when rendering scenes requiring huge amounts of RAM!

See you in Khyberspace!

Yadgar

Now playing: When I was a Man and you were a Woman (John Foxx)

Post a reply to this message

"StephenS" <nomail@nomail> wrote:
> Related to the Flyspray feature request #305;
> remove maximum component limit for blobs (1M)
>
> Start an array [736][350][736]
> ....fails on 32bit WinXP, run on 64bit WinVista
> Initilize array element based on trace to mesh()
> Create a blob component only if on surface.
> ....scan array, check for 6 face elements = fully inside, no component used
>
> Full run, under 15 hours with 2.8Mhz cpu
> array elements = 43,585,544
> blob components = 2,826,336 <<<<<<<<<
> Saved files:
> array 1.64G
> object 131M
> about 3hrs to create array
> about 11-12hrs to select points to use
> trace 2min
>
>
> Use results run,
> Read object(blob) file and trace
> 4min
>
> Comments welcome:
>
> Stephen S

Looks like this could be usefull for muddy and particle based effects the
Blender exporter is already supposed to support blobs, so if it's not broken,
it could provide incredible tools for tree modeling and viscose matter using
blender particles to guide them! Great improvement!

Post a reply to this message

Am 16.02.2015 um 14:38 schrieb StephenS:
> "StephenS" <nomail@nomail> wrote:
>> Related to the Flyspray feature request #305;
>> remove maximum component limit for blobs (1M)
> .....
>
> Forgot to say, used:
> Pov-Ray v 3.7.0.20140613.unofficial.msvc10.win64
> from winpov help about
>
> This should be Uberpov, but not sure what version.

It isn't. v3.7.0.20140613 is just an unofficial binary release I built 
quite a while ago from the official POV-Ray development sources, and a 
precursor to the semi-official POV-Ray for Windows binary releases I'm 
publishing on https://github.com/c-lipka/povray/releases from time to time.

UberPOV binaries can be found on 
https://github.com/UberPOV/UberPOV/releases.

As for FlySpray issue #305, I forgot to close that one. Thanks for 
reminding me.

Post a reply to this message

> Hi(gh)!
>
> On 16.02.2015 14:21, StephenS wrote:
>> Start an array [736][350][736]
>> ....fails on 32bit WinXP, run on 64bit WinVista
>
> Perhaps you should have tried Linux - I experienced a slightly better
> memory use under Linux when rendering scenes requiring huge amounts of RAM!

Linux won't help in this case: POV-Ray isn't optimized for parser memory 
footprint, and will try to allocate some 3.5 GB of RAM for that array, 
exceeding the 3 GB per-process user memory limit for 32 bit applications 
imposed by both Windows and Linux.

This really is a matter of 32 bit vs. 64 bit.

Post a reply to this message

Hey, excellent!

Hopefully this makes it into main. A lot of my macros depend on blobs
(snow, ice coat, icicle, corrosion, etc..), and that limit was vexing.

Now if I can just get Glows in there... :p

Ian

"StephenS" <nomail@nomail> wrote:
> Related to the Flyspray feature request #305; remove maximum component limit for
blobs (1M)
> 
> Start an array [736][350][736] ....fails on 32bit WinXP, run on 64bit
> WinVista Initilize array element based on trace to mesh() Create a blob
> component only if on surface. ....scan array, check for 6 face elements =
> fully inside, no component used
> 
> Full run, under 15 hours with 2.8Mhz cpu array elements = 43,585,544 blob
> components = 2,826,336 <<<<<<<<< Saved files:
> array 1.64G
> object 131M
> about 3hrs to create array
> about 11-12hrs to select points to use
> trace 2min
> 
> Use results run,
> Read object(blob) file and trace
> 4min
> 
> Comments welcome:
> 
> Stephen S

Post a reply to this message

I like, that the surface of your cup looks a but like clay.
Give it a clay-red color, and the illusion is perfect.




"StephenS" <nomail@nomail> wrote:
> Related to the Flyspray feature request #305;
> remove maximum component limit for blobs (1M)
>
> Start an array [736][350][736]
> ....fails on 32bit WinXP, run on 64bit WinVista
> Initilize array element based on trace to mesh()
> Create a blob component only if on surface.
> ....scan array, check for 6 face elements = fully inside, no component used
>
> Full run, under 15 hours with 2.8Mhz cpu
> array elements = 43,585,544
> blob components = 2,826,336 <<<<<<<<<
> Saved files:
> array 1.64G
> object 131M
> about 3hrs to create array
> about 11-12hrs to select points to use
> trace 2min
>
>
> Use results run,
> Read object(blob) file and trace
> 4min
>
> Comments welcome:
>
> Stephen S

Post a reply to this message