prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.77k stars 1.94k forks source link

Time for a new travel engine #10756

Open onolox opened 1 year ago

onolox commented 1 year ago

The engine simple drag the nozzle all over the place, simple go over things printed in the layer . In overrall the travel engine is dumb in prusaslicer. It's not only on organic supports. Common, Cura is open source, get inspiration there. I love PS but in the actual state is a deal breaker.

Video:

https://user-images.githubusercontent.com/11450681/227791993-1f83b7da-3ad5-44c8-872f-ded07505c1fb.mp4

Originally posted by @onolox in https://github.com/prusa3d/PrusaSlicer/issues/10077#issuecomment-1484159271

onolox commented 1 year ago

image

And now an example on how Cura deals with the same part (printing started in the right):

image

igerko commented 1 year ago

I couldn't solve issue with broke suport after 6h of printing (17h total). Tried it 4-times, but support for 3 iterations looked like detached from bed, then I was trying fix it with Support First layer densinity and First layer expansion. On 4th iteration supports didn't detached from bed, but broke in bottom layers.

Thanks for fiding it out.

westranm commented 1 year ago

I just figured this out today when the nozzle kept breaking off organic supports over and over. This really needs to be fixed...it is making organic supports really a crap shoot as to whether they survive enough to properly support the items being printed. I have added z-lift to see if the issue is resolved but hope that my print quality is not impacted.

onolox commented 1 year ago

z-lift is just an poor workaround, and a poorer excuse.

OpaApo commented 1 year ago

I am a total beginner that chose PrusaSlicer because of the organic supports, so hyped on YT. On smaller prints this bug didn't happen. So i kept printing the big statue. On every print the supports fell off after about 4 hours of printing. I started the print 4 times. I wasted so much time and filament trying to figure out what's happening, when finally on the 4th time i saw the nozzle, knocking over the support. Such a simple explanation but I really couldn't believe it, that slicing software, has such enormous bug in it's basic functionality.

onolox commented 1 year ago

Cura has tree supports in the same level as prusa now. Cura is much more complex, lot of settings, but the majority of them are a setting you set once and can hide forever. In the end you have the same amount of the prusa, and cura is so much more advanced and reliable. But Tree supports need some fiddling in cura to be in the same level of the default of prusa.

rodokas commented 2 months ago

I've been waiting for a Prusa solution for this for a long time! I really like Prusa but this bothers me a lot, it's simply improving travel so as not to run over objects that have already been printed. Estou esperando uma solução do prusa para isso a muito tempo! gosto muito do prusa mas isso me pertuba muito, é simplesmente melhorar as viagens para nao passar por cima de objetos ja impressos.

onolox commented 2 months ago

Options to have same trees has prusa:

@OpaApo

rodokas commented 2 months ago

This only solves the problem with tree supports, but if they are not supports, but rather items in the part, the movement must also be controlled.

Em ter., 27 de ago. de 2024, 10:18, Eduardo @.***> escreveu:

Cela ne fonctionne que sur les supports d'arbres, mais s'il ne s'agit pas de supports, mais d'éléments de la pièce, le mouvement doit également être contrôlé.

Em ter., 27 de ago. de 2024, 09:40, Fabio Markmitt < @.***> escreveu:

Options to have same trees has prusa: image.png (view on web) https://github.com/user-attachments/assets/74b31c68-9f27-421c-9883-3cfae64fac9f

— Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/10756#issuecomment-2312454106, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASCOHPIEBN2AULQWD7VL3M3ZTRXUHAVCNFSM6AAAAABNF3FGZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGQ2TIMJQGY . You are receiving this because you commented.Message ID: @.***>