Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supports placement with multiple objects #3288

Closed
DrJuJu opened this issue Dec 7, 2019 · 1 comment
Closed

Supports placement with multiple objects #3288

DrJuJu opened this issue Dec 7, 2019 · 1 comment

Comments

@DrJuJu
Copy link

DrJuJu commented Dec 7, 2019

PrusaSlicer
Version: 2.1.0+win64
Build: PrusaSlicer-2.1.0+win64-201909160915

Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 18363), 64-bit edition
Total RAM size [MB]: 8,477MB
OpenGL installation
GL version: 4.6.0 - Build 26.20.100.7463
Vendor: Intel
Renderer: Intel(R) HD Graphics 530
GLSL version: 4.60 - Build 26.20.100.7463

Behavior

Created a compact platter to print the Braq Dragon Wings (https://www.thingiverse.com/thing:854575) Using the non support stl files

I've attached the gcode and Prusa Slicer config files.

Before starting the print run, all looked ok but after the print had completed I found that the slicer setting for "only on print bed" had been ignored, for the mid wing sections, which are partially under the larger wing sections, and the support for the larger, overhanging wing had been set onto the lower part.

It appears that the slicing process slices all objects separately, thereby ignoring any possible conflicts with other items on the platter.

I believe the system should have either issued a warning or generated a failure message with steps to correct the issue, i.e. re-arrange the parts.

Dragon_Wings_0.2mm_PLA.gcode.zip
PrusaSlicer_config_bundle.ini.txt

@FidelCapo
Copy link
Collaborator

FidelCapo commented Dec 9, 2019

This is a known issue. Supports are generated per object, so supports of one object can go through other objects.
I think this is duplicate of #316

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants