Ryfujk

Do I have an "anti-research" personality?

How much cash can I safely carry into the USA and avoid civil forfeiture?

What is the smallest unit of eos?

Elements that can bond to themselves?

Can someone publish a story that happened to you?

What happened to Captain America in Endgame?

Mistake in years of experience in resume?

Who was the lone kid in the line of people at the lake at the end of Avengers: Endgame?

Could the terminal length of components like resistors be reduced?

Are there physical dangers to preparing a prepared piano?

What's the polite way to say "I need to urinate"?

Re-entry to Germany after vacation using blue card

How can I print the prosodic symbols in LaTeX?

How can I practically buy stocks?

What term is being referred to with "reflected-sound-of-underground-spirits"?

How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?

Was there a shared-world project before "Thieves World"?

How would 10 generations of living underground change the human body?

What happens to Mjolnir (Thor's hammer) at the end of Endgame?

Read line from file and process something

What does the integral of a function times a function of a random variable represent, conceptually?

What is the philosophical significance of speech acts/implicature?

What are the steps to solving this definite integral?

Two field separators (colon and space) in awk

How to prevent z-fighting in OpenSCAD?

How to remove internal part of a hex gridAre there any “best” or at least “common” practices to handle allowances in OpenSCAD code?OpenSCAD library for empty space/holesHow to specify rotation origin in openscadOpenSCAD editor font is unreadableOpenSCAD 2018 Command lineOpenSCAD “not valid 2-manifold” useful informationWhy is 2 / -2 / 2 equal to -2 in OpenSCAD? (Mathematical Order of Operations)

2

$begingroup$

Z-fighting is a 3D rendering artifact of coplanar surfaces (means, triangles are located in exactly the same plane, and overlap).

It can happen in OpenSCAD's preview mode when doing a difference() or union() operation. In case of difference(), the rendering artifacts can prevent seeing into a hole in the object. The "compile and render" mode in OpenSCAD does not have z-fighting issues, but it can take some time to render an object.

How best to avoid z-fighting?

If the answer involves changes to the code, I would love to see an idiomatic answer / established convention of OpenSCAD coders, if that exists.

openscad

share|improve this question

edited 1 hour ago

tanius

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

add a comment | 

2

$begingroup$

Z-fighting is a 3D rendering artifact of coplanar surfaces (means, triangles are located in exactly the same plane, and overlap).

It can happen in OpenSCAD's preview mode when doing a difference() or union() operation. In case of difference(), the rendering artifacts can prevent seeing into a hole in the object. The "compile and render" mode in OpenSCAD does not have z-fighting issues, but it can take some time to render an object.

How best to avoid z-fighting?

If the answer involves changes to the code, I would love to see an idiomatic answer / established convention of OpenSCAD coders, if that exists.

openscad

share|improve this question

edited 1 hour ago

tanius

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

add a comment | 

$begingroup$

Z-fighting is a 3D rendering artifact of coplanar surfaces (means, triangles are located in exactly the same plane, and overlap).

It can happen in OpenSCAD's preview mode when doing a difference() or union() operation. In case of difference(), the rendering artifacts can prevent seeing into a hole in the object. The "compile and render" mode in OpenSCAD does not have z-fighting issues, but it can take some time to render an object.

How best to avoid z-fighting?

If the answer involves changes to the code, I would love to see an idiomatic answer / established convention of OpenSCAD coders, if that exists.

openscad

share|improve this question

edited 1 hour ago

tanius

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

share|improve this question

edited 1 hour ago

tanius

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 1 hour ago

tanius

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 4 hours ago

taniustanius

1435

1 Answer
1

active

oldest

votes

3

$begingroup$

The general advice in the OpenSCAD community is to "extend your cuts and embed your joins" (source). Not just because of the rendering artifacts but also because z-fighting can cause unexpected errors during STL export.

So you would change the dimensions of your objects very slightly (0.01 mm works fine) so that:

• for a union(), there is overlap volume between the parts


• for a difference(), the intersector has volume both inside and outside of the intersected part

Now you could adjust both the size and position of your parts to keep the mathematically exact dimensions for the resulting part. But I found that for the purposes of 3D printing, such accuracy is not worth it because it complicates the formulas so much.

Instead, I adjust either position or size of a part, depending on what is simpler in each case. A measure in the final design will be off by 0.01 mm, which does not matter.

And I keep the 0.01 mm offset in a variable called nothing (picked that up somewhere and liked it …). This keeps the calculations intuitively understandable.

Example

To create a cylinder and cut a hole to half of its depth, it would do this:

//!OpenSCAD

nothing=0.01;

height=40;



difference(){

    cylinder(h=height, r=20, center=true);



    translate([0, 0, height/4 + nothing]) 

        cylinder(h=height/2, r=15, center=true);

}

Now the hole is nothing=0.01 less deep than half of the cylinder – that's the inaccuracy I accept.

(Note: You can try the above code online by copy & pasting it into OpenJSCAD. Include the magic comment in the first line to switch it to OpenSCAD syntax.)

share|improve this answer

edited 49 mins ago

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  $begingroup$
  Your answer is the one I'd post for this question. You add the parameter "nothing" while I use "addabit = 0.1" for most z actions.
  $endgroup$
  – fred_dot_u
  2 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "640"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

tanius is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f9794%2fhow-to-prevent-z-fighting-in-openscad%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

$begingroup$

The general advice in the OpenSCAD community is to "extend your cuts and embed your joins" (source). Not just because of the rendering artifacts but also because z-fighting can cause unexpected errors during STL export.

So you would change the dimensions of your objects very slightly (0.01 mm works fine) so that:

• for a union(), there is overlap volume between the parts


• for a difference(), the intersector has volume both inside and outside of the intersected part

Now you could adjust both the size and position of your parts to keep the mathematically exact dimensions for the resulting part. But I found that for the purposes of 3D printing, such accuracy is not worth it because it complicates the formulas so much.

Instead, I adjust either position or size of a part, depending on what is simpler in each case. A measure in the final design will be off by 0.01 mm, which does not matter.

And I keep the 0.01 mm offset in a variable called nothing (picked that up somewhere and liked it …). This keeps the calculations intuitively understandable.

Example

To create a cylinder and cut a hole to half of its depth, it would do this:

//!OpenSCAD

nothing=0.01;

height=40;



difference(){

    cylinder(h=height, r=20, center=true);



    translate([0, 0, height/4 + nothing]) 

        cylinder(h=height/2, r=15, center=true);

}

Now the hole is nothing=0.01 less deep than half of the cylinder – that's the inaccuracy I accept.

(Note: You can try the above code online by copy & pasting it into OpenJSCAD. Include the magic comment in the first line to switch it to OpenSCAD syntax.)

share|improve this answer

edited 49 mins ago

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  $begingroup$
  Your answer is the one I'd post for this question. You add the parameter "nothing" while I use "addabit = 0.1" for most z actions.
  $endgroup$
  – fred_dot_u
  2 hours ago
  

  
  
  
  

add a comment | 

3

$begingroup$

The general advice in the OpenSCAD community is to "extend your cuts and embed your joins" (source). Not just because of the rendering artifacts but also because z-fighting can cause unexpected errors during STL export.

So you would change the dimensions of your objects very slightly (0.01 mm works fine) so that:

• for a union(), there is overlap volume between the parts


• for a difference(), the intersector has volume both inside and outside of the intersected part

Now you could adjust both the size and position of your parts to keep the mathematically exact dimensions for the resulting part. But I found that for the purposes of 3D printing, such accuracy is not worth it because it complicates the formulas so much.

Instead, I adjust either position or size of a part, depending on what is simpler in each case. A measure in the final design will be off by 0.01 mm, which does not matter.

And I keep the 0.01 mm offset in a variable called nothing (picked that up somewhere and liked it …). This keeps the calculations intuitively understandable.

Example

To create a cylinder and cut a hole to half of its depth, it would do this:

//!OpenSCAD

nothing=0.01;

height=40;



difference(){

    cylinder(h=height, r=20, center=true);



    translate([0, 0, height/4 + nothing]) 

        cylinder(h=height/2, r=15, center=true);

}

Now the hole is nothing=0.01 less deep than half of the cylinder – that's the inaccuracy I accept.

(Note: You can try the above code online by copy & pasting it into OpenJSCAD. Include the magic comment in the first line to switch it to OpenSCAD syntax.)

share|improve this answer

edited 49 mins ago

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  $begingroup$
  Your answer is the one I'd post for this question. You add the parameter "nothing" while I use "addabit = 0.1" for most z actions.
  $endgroup$
  – fred_dot_u
  2 hours ago
  

  
  
  
  

add a comment | 

$begingroup$

The general advice in the OpenSCAD community is to "extend your cuts and embed your joins" (source). Not just because of the rendering artifacts but also because z-fighting can cause unexpected errors during STL export.

So you would change the dimensions of your objects very slightly (0.01 mm works fine) so that:

• for a union(), there is overlap volume between the parts


• for a difference(), the intersector has volume both inside and outside of the intersected part

Now you could adjust both the size and position of your parts to keep the mathematically exact dimensions for the resulting part. But I found that for the purposes of 3D printing, such accuracy is not worth it because it complicates the formulas so much.

Instead, I adjust either position or size of a part, depending on what is simpler in each case. A measure in the final design will be off by 0.01 mm, which does not matter.

And I keep the 0.01 mm offset in a variable called nothing (picked that up somewhere and liked it …). This keeps the calculations intuitively understandable.

Example

To create a cylinder and cut a hole to half of its depth, it would do this:

//!OpenSCAD

nothing=0.01;

height=40;



difference(){

    cylinder(h=height, r=20, center=true);



    translate([0, 0, height/4 + nothing]) 

        cylinder(h=height/2, r=15, center=true);

}

Now the hole is nothing=0.01 less deep than half of the cylinder – that's the inaccuracy I accept.

(Note: You can try the above code online by copy & pasting it into OpenJSCAD. Include the magic comment in the first line to switch it to OpenSCAD syntax.)

share|improve this answer

edited 49 mins ago

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

$endgroup$

//!OpenSCAD

nothing=0.01;

height=40;



difference(){

    cylinder(h=height, r=20, center=true);



    translate([0, 0, height/4 + nothing]) 

        cylinder(h=height/2, r=15, center=true);

}

share|improve this answer

edited 49 mins ago

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 4 hours ago

taniustanius

1435

New contributor

tanius is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 4 hours ago

taniustanius

1435