discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

Re: [OpenSCAD] Normalized tree is growing past ... elements

M
MichaelAtOz
Thu, Aug 20, 2015 4:08 AM

zeycus wrote

Hi, I am new to OpenSCAD, but PovRAY veteran. I am translating a model I
made some time ago from PovRAY to OpenSCAD. The problem is that with very
few solids, I am already getting a message "Normalized Tree is growing
past 200000 elements". I must be doing something wrong, this is just a
single dodecahedron from which some pyramids are substracted.
...

Hi, your post is still flagged "This post has NOT been accepted by the
mailing list yet. " so no one on the mailing list sees it. They will see
this. If you next post is still flagged (after a few minutes) check your
registration
http://forum.openscad.org/mailing_list/MailingListOptions.jtp?forum=1  .


Unless specifically shown otherwise above, my contribution is in the Public Domain; To the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. This work is published globally via the internet. :) Inclusion of works of previous authors is not included in the above.

The TPP is no simple “trade agreement.”  Fight it! http://www.ourfairdeal.org/

View this message in context: http://forum.openscad.org/Normalized-tree-is-growing-past-elements-tp13509p13561.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

zeycus wrote > Hi, I am new to OpenSCAD, but PovRAY veteran. I am translating a model I > made some time ago from PovRAY to OpenSCAD. The problem is that with very > few solids, I am already getting a message "Normalized Tree is growing > past 200000 elements". I must be doing something wrong, this is just a > single dodecahedron from which some pyramids are substracted. > ... Hi, your post is still flagged "This post has NOT been accepted by the mailing list yet. " so no one on the mailing list sees it. They will see this. If you next post is still flagged (after a few minutes) check your registration <http://forum.openscad.org/mailing_list/MailingListOptions.jtp?forum=1> . ----- Unless specifically shown otherwise above, my contribution is in the Public Domain; To the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. This work is published globally via the internet. :) Inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ -- View this message in context: http://forum.openscad.org/Normalized-tree-is-growing-past-elements-tp13509p13561.html Sent from the OpenSCAD mailing list archive at Nabble.com.
TP
Torsten Paul
Thu, Aug 20, 2015 10:23 AM

zeycus wrote

Hi, I am new to OpenSCAD, but PovRAY veteran. I am translating a model I
made some time ago from PovRAY to OpenSCAD. The problem is that with very
few solids, I am already getting a message "Normalized Tree is growing
past 200000 elements". I must be doing something wrong, this is just a
single dodecahedron from which some pyramids are substracted.
...

I guess the main reason for this is the usage of intersection with many
objects. Some details of the effect regarding the preview are explained
in https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/FAQ#Why_is_the_preview_so_slow.3F

A simple workaround (at the expense of a slower initial preview) is to
prefix all the intersection() definitions with render(), e.g.

module dodecahedron()
{
rotate([0,0,-90])
render() intersection(){
rotate(a=0, v=[0,0,1]){
...

This will force the intersection result to be generated as mesh making
the calculation slower but preventing the CSG tree explosion.

ciao,
Torsten.

zeycus wrote > Hi, I am new to OpenSCAD, but PovRAY veteran. I am translating a model I > made some time ago from PovRAY to OpenSCAD. The problem is that with very > few solids, I am already getting a message "Normalized Tree is growing > past 200000 elements". I must be doing something wrong, this is just a > single dodecahedron from which some pyramids are substracted. > ... > I guess the main reason for this is the usage of intersection with many objects. Some details of the effect regarding the preview are explained in https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/FAQ#Why_is_the_preview_so_slow.3F A simple workaround (at the expense of a slower initial preview) is to prefix all the intersection() definitions with render(), e.g. module dodecahedron() { rotate([0,0,-90]) render() intersection(){ rotate(a=0, v=[0,0,1]){ ... This will force the intersection result to be generated as mesh making the calculation slower but preventing the CSG tree explosion. ciao, Torsten.