RW
Raymond West
Mon, Dec 2, 2024 7:16 PM
I've been experimenting with these simple bevel modules.
module myshape(){
cylinder(d=18,h=25);
cube(25);
}
//bevelall()myshape();
below()myshape();
beveltop()myshape();
module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top
of bevel
translate([0,0,ht])
for (j=[0:0.1:bh-0.1]){
translate([0,0,j])
linear_extrude(0.1)
offset(delta=-1*j)
projection(cut=false)
translate([0,0,-ht])
children();
}
}
module below(bh=1,ht=25){
intersection(){translate([0,0,-10000+ht])
cube([10000,10000,20000],true);
children();}
}
There are problems with manifold rendering in particular, but also with
some others. The only way to resolve the issue, afaik, is to close down
openscad, and restart. In f5 render it bevels the top of myshape, as
expected, in f6, it messes up. Once it is messed up, flushing
cache/whatever has no effect. Translating the modules, or changing $fn,
or sizes still gives the same distortions, (but in different location or
resolution). Anyway, I've come across similar problems before with
rendering, so I expect I'll have to live with it, unless recent builds
have specifically addressed this type of issue - my version is
2024.02.19, so maybe time to update again. Images attached below, good
and bad
Perhaps someone can play with the code, load and run manifold, see if
you get the first image. If you get something like the second, then what
do you do to get the first, other than restarting?
I've been experimenting with these simple bevel modules.
module myshape(){
cylinder(d=18,h=25);
cube(25);
}
//bevelall()myshape();
below()myshape();
beveltop()myshape();
module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top
of bevel
translate([0,0,ht])
for (j=[0:0.1:bh-0.1]){
translate([0,0,j])
linear_extrude(0.1)
offset(delta=-1*j)
projection(cut=false)
translate([0,0,-ht])
children();
}
}
module below(bh=1,ht=25){
intersection(){translate([0,0,-10000+ht])
cube([10000,10000,20000],true);
children();}
}
There are problems with manifold rendering in particular, but also with
some others. The only way to resolve the issue, afaik, is to close down
openscad, and restart. In f5 render it bevels the top of myshape, as
expected, in f6, it messes up. Once it is messed up, flushing
cache/whatever has no effect. Translating the modules, or changing $fn,
or sizes still gives the same distortions, (but in different location or
resolution). Anyway, I've come across similar problems before with
rendering, so I expect I'll have to live with it, unless recent builds
have specifically addressed this type of issue - my version is
2024.02.19, so maybe time to update again. Images attached below, good
and bad
Perhaps someone can play with the code, load and run manifold, see if
you get the first image. If you get something like the second, then what
do you do to get the first, other than restarting?
NH
nop head
Mon, Dec 2, 2024 9:18 PM
I got the broken one with manifold enabled. To fix it I disabled manifold
and restarted OpenSCAD and then got a correct render with CGAL.
Version 2024.01.26 (git 358af340c)
On Mon, 2 Dec 2024 at 19:16, Raymond West via Discuss <
discuss@lists.openscad.org> wrote:
I've been experimenting with these simple bevel modules.
module myshape(){
cylinder(d=18,h=25);
cube(25);
}
//bevelall()myshape();
below()myshape();
beveltop()myshape();
module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
bevel
translate([0,0,ht])
for (j=[0:0.1:bh-0.1]){
translate([0,0,j])
linear_extrude(0.1)
offset(delta=-1*j)
projection(cut=false)
translate([0,0,-ht])
children();
}
}
module below(bh=1,ht=25){
intersection(){translate([0,0,-10000+ht])
cube([10000,10000,20000],true);
children();}
}
There are problems with manifold rendering in particular, but also with
some others. The only way to resolve the issue, afaik, is to close down
openscad, and restart. In f5 render it bevels the top of myshape, as
expected, in f6, it messes up. Once it is messed up, flushing
cache/whatever has no effect. Translating the modules, or changing $fn, or
sizes still gives the same distortions, (but in different location or
resolution). Anyway, I've come across similar problems before with
rendering, so I expect I'll have to live with it, unless recent builds have
specifically addressed this type of issue - my version is 2024.02.19, so
maybe time to update again. Images attached below, good and bad
Perhaps someone can play with the code, load and run manifold, see if you
get the first image. If you get something like the second, then what do you
do to get the first, other than restarting?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
I got the broken one with manifold enabled. To fix it I disabled manifold
and restarted OpenSCAD and then got a correct render with CGAL.
Version 2024.01.26 (git 358af340c)
On Mon, 2 Dec 2024 at 19:16, Raymond West via Discuss <
discuss@lists.openscad.org> wrote:
> I've been experimenting with these simple bevel modules.
>
> module myshape(){
> cylinder(d=18,h=25);
> cube(25);
> }
>
> //bevelall()myshape();
>
> below()myshape();
> beveltop()myshape();
>
> module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
> bevel
> translate([0,0,ht])
> for (j=[0:0.1:bh-0.1]){
> translate([0,0,j])
> linear_extrude(0.1)
> offset(delta=-1*j)
> projection(cut=false)
> translate([0,0,-ht])
> children();
> }
> }
>
> module below(bh=1,ht=25){
> intersection(){translate([0,0,-10000+ht])
> cube([10000,10000,20000],true);
> children();}
> }
>
> There are problems with manifold rendering in particular, but also with
> some others. The only way to resolve the issue, afaik, is to close down
> openscad, and restart. In f5 render it bevels the top of myshape, as
> expected, in f6, it messes up. Once it is messed up, flushing
> cache/whatever has no effect. Translating the modules, or changing $fn, or
> sizes still gives the same distortions, (but in different location or
> resolution). Anyway, I've come across similar problems before with
> rendering, so I expect I'll have to live with it, unless recent builds have
> specifically addressed this type of issue - my version is 2024.02.19, so
> maybe time to update again. Images attached below, good and bad
>
> Perhaps someone can play with the code, load and run manifold, see if you
> get the first image. If you get something like the second, then what do you
> do to get the first, other than restarting?
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
M
mikeonenine@web.de
Mon, Dec 2, 2024 9:34 PM
I got the broken one with manifold enabled. To fix it I disabled manifold
and restarted OpenSCAD and then got a correct render with CGAL.
Version 2024.01.26 (git 358af340c)
On Mon, 2 Dec 2024 at 19:16, Raymond West via Discuss <
discuss@lists.openscad.org> wrote:
I've been experimenting with these simple bevel modules.
module myshape(){
cylinder(d=18,h=25);
cube(25);
}
//bevelall()myshape();
below()myshape();
beveltop()myshape();
module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
bevel
translate([0,0,ht])
for (j=[0:0.1:bh-0.1]){
translate([0,0,j])
linear_extrude(0.1)
offset(delta=-1*j)
projection(cut=false)
translate([0,0,-ht])
children();
}
}
module below(bh=1,ht=25){
intersection(){translate([0,0,-10000+ht])
cube([10000,10000,20000],true);
children();}
}
There are problems with manifold rendering in particular, but also with
some others. The only way to resolve the issue, afaik, is to close down
openscad, and restart. In f5 render it bevels the top of myshape, as
expected, in f6, it messes up. Once it is messed up, flushing
cache/whatever has no effect. Translating the modules, or changing $fn, or
sizes still gives the same distortions, (but in different location or
resolution). Anyway, I've come across similar problems before with
rendering, so I expect I'll have to live with it, unless recent builds have
specifically addressed this type of issue - my version is 2024.02.19, so
maybe time to update again. Images attached below, good and bad
Perhaps someone can play with the code, load and run manifold, see if you
get the first image. If you get something like the second, then what do you
do to get the first, other than restarting?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Sorry to spoil the fun!
ch=1; // chamfer
cylinder(d=18, h=25-ch);
cube([25, 25, 25-ch]);
translate([0, 0, 25-ch])
cylinder(ch, 9, 9-ch);
translate([25/2, 25/2, 25-ch])
linear_extrude(1, scale=[0.9, 0.9])
square(25, center=true);
No grainy patterns. Can be turned in any direction without parts disappearing. No messing up.
nop head wrote:
> I got the broken one with manifold enabled. To fix it I disabled manifold
> and restarted OpenSCAD and then got a correct render with CGAL.
>
> Version 2024.01.26 (git 358af340c)
>
> On Mon, 2 Dec 2024 at 19:16, Raymond West via Discuss <
> discuss@lists.openscad.org> wrote:
>
> > I've been experimenting with these simple bevel modules.
> >
> > module myshape(){
> > cylinder(d=18,h=25);
> > cube(25);
> > }
> >
> > //bevelall()myshape();
> >
> > below()myshape();
> > beveltop()myshape();
> >
> > module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
> > bevel
> > translate(\[0,0,ht\])
> > for (j=\[0:0.1:bh-0.1\]){
> > translate(\[0,0,j\])
> > linear_extrude(0.1)
> > offset(delta=-1\*j)
> > projection(cut=false)
> > translate(\[0,0,-ht\])
> > children();
> > }
> > }
> >
> > module below(bh=1,ht=25){
> > intersection(){translate(\[0,0,-10000+ht\])
> > cube(\[10000,10000,20000\],true);
> > children();}
> > }
> >
> > There are problems with manifold rendering in particular, but also with
> > some others. The only way to resolve the issue, afaik, is to close down
> > openscad, and restart. In f5 render it bevels the top of myshape, as
> > expected, in f6, it messes up. Once it is messed up, flushing
> > cache/whatever has no effect. Translating the modules, or changing $fn, or
> > sizes still gives the same distortions, (but in different location or
> > resolution). Anyway, I've come across similar problems before with
> > rendering, so I expect I'll have to live with it, unless recent builds have
> > specifically addressed this type of issue - my version is 2024.02.19, so
> > maybe time to update again. Images attached below, good and bad
> >
> > Perhaps someone can play with the code, load and run manifold, see if you
> > get the first image. If you get something like the second, then what do you
> > do to get the first, other than restarting?
> >
> > ---
> >
> > OpenSCAD mailing list
> > To unsubscribe send an email to discuss-leave@lists.openscad.org
Sorry to spoil the fun!
`ch=1; // chamfer`
`cylinder(d=18, h=25-ch);`
`cube([25, 25, 25-ch]);`
`translate([0, 0, 25-ch])`
`cylinder(ch, 9, 9-ch);`
`translate([25/2, 25/2, 25-ch])`
`linear_extrude(1, scale=[0.9, 0.9])`
`square(25, center=true);`
No grainy patterns. Can be turned in any direction without parts disappearing. No messing up.
SP
Sanjeev Prabhakar
Tue, Dec 3, 2024 1:00 AM
Hi Ray,
As i understand from your code, you are stacking slices of 0.1mm thickness
one over the other.
Would it not be better to just have 2 offsets and hull them to get bevel.
But that would work only for convex shapes.
Drawing from the primitives has serious limitations. It's better to draw
shapes with points list.
A lot of limitations related to rendering can be avoided that way afaik.
Regards
On Tue, 3 Dec, 2024, 12:47 am Raymond West via Discuss, <
discuss@lists.openscad.org> wrote:
I've been experimenting with these simple bevel modules.
module myshape(){
cylinder(d=18,h=25);
cube(25);
}
//bevelall()myshape();
below()myshape();
beveltop()myshape();
module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
bevel
translate([0,0,ht])
for (j=[0:0.1:bh-0.1]){
translate([0,0,j])
linear_extrude(0.1)
offset(delta=-1*j)
projection(cut=false)
translate([0,0,-ht])
children();
}
}
module below(bh=1,ht=25){
intersection(){translate([0,0,-10000+ht])
cube([10000,10000,20000],true);
children();}
}
There are problems with manifold rendering in particular, but also with
some others. The only way to resolve the issue, afaik, is to close down
openscad, and restart. In f5 render it bevels the top of myshape, as
expected, in f6, it messes up. Once it is messed up, flushing
cache/whatever has no effect. Translating the modules, or changing $fn, or
sizes still gives the same distortions, (but in different location or
resolution). Anyway, I've come across similar problems before with
rendering, so I expect I'll have to live with it, unless recent builds have
specifically addressed this type of issue - my version is 2024.02.19, so
maybe time to update again. Images attached below, good and bad
Perhaps someone can play with the code, load and run manifold, see if you
get the first image. If you get something like the second, then what do you
do to get the first, other than restarting?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Hi Ray,
As i understand from your code, you are stacking slices of 0.1mm thickness
one over the other.
Would it not be better to just have 2 offsets and hull them to get bevel.
But that would work only for convex shapes.
Drawing from the primitives has serious limitations. It's better to draw
shapes with points list.
A lot of limitations related to rendering can be avoided that way afaik.
Regards
On Tue, 3 Dec, 2024, 12:47 am Raymond West via Discuss, <
discuss@lists.openscad.org> wrote:
> I've been experimenting with these simple bevel modules.
>
> module myshape(){
> cylinder(d=18,h=25);
> cube(25);
> }
>
> //bevelall()myshape();
>
> below()myshape();
> beveltop()myshape();
>
> module beveltop(bh=1,ht=25){ // bh = bevel height, ht = height to top of
> bevel
> translate([0,0,ht])
> for (j=[0:0.1:bh-0.1]){
> translate([0,0,j])
> linear_extrude(0.1)
> offset(delta=-1*j)
> projection(cut=false)
> translate([0,0,-ht])
> children();
> }
> }
>
> module below(bh=1,ht=25){
> intersection(){translate([0,0,-10000+ht])
> cube([10000,10000,20000],true);
> children();}
> }
>
> There are problems with manifold rendering in particular, but also with
> some others. The only way to resolve the issue, afaik, is to close down
> openscad, and restart. In f5 render it bevels the top of myshape, as
> expected, in f6, it messes up. Once it is messed up, flushing
> cache/whatever has no effect. Translating the modules, or changing $fn, or
> sizes still gives the same distortions, (but in different location or
> resolution). Anyway, I've come across similar problems before with
> rendering, so I expect I'll have to live with it, unless recent builds have
> specifically addressed this type of issue - my version is 2024.02.19, so
> maybe time to update again. Images attached below, good and bad
>
> Perhaps someone can play with the code, load and run manifold, see if you
> get the first image. If you get something like the second, then what do you
> do to get the first, other than restarting?
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
M
mikeonenine@web.de
Tue, Dec 3, 2024 1:24 AM
Would it not be better to just have 2 offsets and hull them to get bevel.
But that would work only for convex shapes.
Hull fills in the gap between the widest parts of hte offsets producing an extra edge around the larger offset.
This works nicely for all rectangles, though I am not quite sure why:
ch=1; // chamfer height = width
sqx=5; // side x
sqy=10; // side y
linear_extrude(ch, scale=[(1-2/sqx), (1+2/sqy)])
square([sqx, sqy], center=true);
The long sides are chamfered one way, the short sides the other way.
Sanjeev Prabhakar wrote:
> Would it not be better to just have 2 offsets and hull them to get bevel.
>
> But that would work only for convex shapes.
Hull fills in the gap between the widest parts of hte offsets producing an extra edge around the larger offset.
This works nicely for all rectangles, though I am not quite sure why:
`ch=1; // chamfer height = width`
`sqx=5; // side x`
`sqy=10; // side y`
`linear_extrude(ch, scale=[(1-2/sqx), (1+2/sqy)])`
`square([sqx, sqy], center=true);`
The long sides are chamfered one way, the short sides the other way.
M
mikeonenine@web.de
Tue, Dec 3, 2024 1:45 AM
Hey!
With offset() you even get nicely chamfered rounded corners!
$fn=100;
ch=1; // chamfer height = width
sqx=5; // side x
sqy=10; // side y
linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])
offset(2)
square([sqx, sqy], center=true);
BTW is this exercise just about experimenting with simple bevel modules or does it have a deeper purpose?
Hey!
With offset() you even get nicely chamfered rounded corners!
`$fn=100;`
`ch=1; // chamfer height = width`
`sqx=5; // side x`
`sqy=10; // side y`
`linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])`
`offset(2)`
`square([sqx, sqy], center=true);`
BTW is this exercise just about experimenting with simple bevel modules or does it have a deeper purpose?
NH
nop head
Tue, Dec 3, 2024 7:31 AM
Regardless of the code, why does Manifold get the wrong result?
On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss discuss@lists.openscad.org
wrote:
Hey!
With offset() you even get nicely chamfered rounded corners!
$fn=100;
ch=1; // chamfer height = width
sqx=5; // side x
sqy=10; // side y
linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])
offset(2)
square([sqx, sqy], center=true);
BTW is this exercise just about experimenting with simple bevel modules or
does it have a deeper purpose?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Regardless of the code, why does Manifold get the wrong result?
On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss <discuss@lists.openscad.org>
wrote:
> Hey!
>
> With offset() you even get nicely chamfered rounded corners!
>
> $fn=100;
>
> ch=1; // chamfer height = width
>
> sqx=5; // side x
>
> sqy=10; // side y
>
> linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])
>
> offset(2)
>
> square([sqx, sqy], center=true);
>
> BTW is this exercise just about experimenting with simple bevel modules or
> does it have a deeper purpose?
>
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
CK
Chun Kit LAM
Tue, Dec 3, 2024 7:41 AM
Which version are you using? I don't get any issue with the latest
master. Manifold was using single precision floating point and can cause
issue for this kind of models, but it was changed a few months ago.
On 12/3/24 15:31, nop head via Discuss wrote:
Regardless of the code, why does Manifold get the wrong result?
On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss
discuss@lists.openscad.org wrote:
Hey!
With offset() you even get nicely chamfered rounded corners!
|$fn=100;|
|ch=1; // chamfer height = width|
|sqx=5; // side x|
|sqy=10; // side y|
|linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])|
|offset(2)|
|square([sqx, sqy], center=true);|
BTW is this exercise just about experimenting with simple bevel
modules or does it have a deeper purpose?
_______________________________________________
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
Which version are you using? I don't get any issue with the latest
master. Manifold was using single precision floating point and can cause
issue for this kind of models, but it was changed a few months ago.
On 12/3/24 15:31, nop head via Discuss wrote:
> Regardless of the code, why does Manifold get the wrong result?
>
> On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss
> <discuss@lists.openscad.org> wrote:
>
> Hey!
>
> With offset() you even get nicely chamfered rounded corners!
>
> |$fn=100;|
>
> |ch=1; // chamfer height = width|
>
> |sqx=5; // side x|
>
> |sqy=10; // side y|
>
> |linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])|
>
> |offset(2)|
>
> |square([sqx, sqy], center=true);|
>
> BTW is this exercise just about experimenting with simple bevel
> modules or does it have a deeper purpose?
>
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email todiscuss-leave@lists.openscad.org
NH
nop head
Tue, Dec 3, 2024 7:51 AM
I am using a version from January so, yes it is due to the massive cube in
the below module. Removing a zero fixes it.
module below(bh=1,ht=25){
intersection(){translate([0,0,-1000+ht])
cube([1000,1000,2000],true);
children();}
}
On Tue, 3 Dec 2024 at 07:42, Chun Kit LAM via Discuss <
discuss@lists.openscad.org> wrote:
Which version are you using? I don't get any issue with the latest master.
Manifold was using single precision floating point and can cause issue for
this kind of models, but it was changed a few months ago.
On 12/3/24 15:31, nop head via Discuss wrote:
Regardless of the code, why does Manifold get the wrong result?
On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss <
discuss@lists.openscad.org> wrote:
Hey!
With offset() you even get nicely chamfered rounded corners!
$fn=100;
ch=1; // chamfer height = width
sqx=5; // side x
sqy=10; // side y
linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])
offset(2)
square([sqx, sqy], center=true);
BTW is this exercise just about experimenting with simple bevel modules
or does it have a deeper purpose?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
I am using a version from January so, yes it is due to the massive cube in
the below module. Removing a zero fixes it.
module below(bh=1,ht=25){
intersection(){translate([0,0,-1000+ht])
cube([1000,1000,2000],true);
children();}
}
On Tue, 3 Dec 2024 at 07:42, Chun Kit LAM via Discuss <
discuss@lists.openscad.org> wrote:
> Which version are you using? I don't get any issue with the latest master.
> Manifold was using single precision floating point and can cause issue for
> this kind of models, but it was changed a few months ago.
> On 12/3/24 15:31, nop head via Discuss wrote:
>
> Regardless of the code, why does Manifold get the wrong result?
>
> On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss <
> discuss@lists.openscad.org> wrote:
>
>> Hey!
>>
>> With offset() you even get nicely chamfered rounded corners!
>>
>> $fn=100;
>>
>> ch=1; // chamfer height = width
>>
>> sqx=5; // side x
>>
>> sqy=10; // side y
>>
>> linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])
>>
>> offset(2)
>>
>> square([sqx, sqy], center=true);
>>
>> BTW is this exercise just about experimenting with simple bevel modules
>> or does it have a deeper purpose?
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
CK
Chun Kit LAM
Tue, Dec 3, 2024 8:54 AM
Why not update? It is already about a year old, and manifold changed a lot.
On 12/3/24 15:51, nop head via Discuss wrote:
I am using a version from January so, yes it is due to the massive
cube in the below module. Removing a zero fixes it.
module below(bh=1,ht=25){
intersection(){translate([0,0,-1000+ht])
cube([1000,1000,2000],true);
children();}
}
On Tue, 3 Dec 2024 at 07:42, Chun Kit LAM via Discuss
discuss@lists.openscad.org wrote:
Which version are you using? I don't get any issue with the latest
master. Manifold was using single precision floating point and can
cause issue for this kind of models, but it was changed a few
months ago.
On 12/3/24 15:31, nop head via Discuss wrote:
Regardless of the code, why does Manifold get the wrong result?
On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss
<discuss@lists.openscad.org> wrote:
Hey!
With offset() you even get nicely chamfered rounded corners!
|$fn=100;|
|ch=1; // chamfer height = width|
|sqx=5; // side x|
|sqy=10; // side y|
|linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])|
|offset(2)|
|square([sqx, sqy], center=true);|
BTW is this exercise just about experimenting with simple
bevel modules or does it have a deeper purpose?
_______________________________________________
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
_______________________________________________
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
_______________________________________________
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
Why not update? It is already about a year old, and manifold changed a lot.
On 12/3/24 15:51, nop head via Discuss wrote:
> I am using a version from January so, yes it is due to the massive
> cube in the below module. Removing a zero fixes it.
>
> module below(bh=1,ht=25){
> intersection(){translate([0,0,-1000+ht])
> cube([1000,1000,2000],true);
> children();}
> }
>
> On Tue, 3 Dec 2024 at 07:42, Chun Kit LAM via Discuss
> <discuss@lists.openscad.org> wrote:
>
> Which version are you using? I don't get any issue with the latest
> master. Manifold was using single precision floating point and can
> cause issue for this kind of models, but it was changed a few
> months ago.
>
> On 12/3/24 15:31, nop head via Discuss wrote:
>> Regardless of the code, why does Manifold get the wrong result?
>>
>> On Tue, 3 Dec 2024 at 01:45, Caddiy via Discuss
>> <discuss@lists.openscad.org> wrote:
>>
>> Hey!
>>
>> With offset() you even get nicely chamfered rounded corners!
>>
>> |$fn=100;|
>>
>> |ch=1; // chamfer height = width|
>>
>> |sqx=5; // side x|
>>
>> |sqy=10; // side y|
>>
>> |linear_extrude(+ch, scale=[(1-2/sqx), (1-2/sqy)])|
>>
>> |offset(2)|
>>
>> |square([sqx, sqy], center=true);|
>>
>> BTW is this exercise just about experimenting with simple
>> bevel modules or does it have a deeper purpose?
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email todiscuss-leave@lists.openscad.org
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email todiscuss-leave@lists.openscad.org