QIDITECH / QIDISlicer

QIDISlicer gets your 3D printing easier and faster.
https://qidi3d.com/
GNU Affero General Public License v3.0
40 stars 10 forks source link

Qidislicer 1.1.0 on Linux #29

Closed Vance1122 closed 4 months ago

Vance1122 commented 5 months ago

When you add several files to the build plate and you use auto arrange then slice, The slicer complains that the models are too close and the tool head might hit other models while printing. It used to not do this in 1.0.8. With this bug, you can only put about half the number of models on the build plate at once because you now have to space them out further. I print all models at once and not one at a time, so no models should be high enough for the tool head to run into.

derbasteller commented 5 months ago

Mein Slicer ist unter Windows 10 pro und kann zu Linux nichts sagen. Morgen werde ich auch mehrere Teile auf die Plattform legen. Mal sehen ob es bei mie auch Probleme gibt?

QIDITECH commented 5 months ago

In 1.1.0, we added Z-axis lift optimizations, turning it off will solve your problem. image

In addition, please provide your model and print parameters if possible so that we can optimize the program.

Vance1122 commented 5 months ago

It is the xmax3 and I am using the 0.6mm nozzle profile set for abs.

On Thu, Jan 25, 2024, 17:23 QIDI TECH @.***> wrote:

In 1.1.0, we added Z-axis lift optimizations, turning it off will solve your problem. image.png (view on web) https://github.com/QIDITECH/QIDISlicer/assets/37525539/6811d0e8-2190-4ceb-a44f-dfc74e3c6f17

In addition, please provide your model and print parameters if possible so that we can optimize the program.

— Reply to this email directly, view it on GitHub https://github.com/QIDITECH/QIDISlicer/issues/29#issuecomment-1911260668, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADAWOCPJ5DX6W64VGDSB6S3YQMARVAVCNFSM6AAAAABCJ3JTPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRGI3DANRWHA . You are receiving this because you authored the thread.Message ID: @.***>

Vance1122 commented 4 months ago

This can be closed as it was fixed in version 1.1.1