Notifications
Clear all

2.8.0  

  RSS
kevsurp
(@kevsurp)
Active Member
2.8.0

is it me or has prusaslicer gotten slow lately when slicing. it use to take like a min to slice a med item now like 3 or more. not sure if i like the new look either

Napsal : 27/06/2024 11:55 pm
jcoplin
(@jcoplin)
Member
RE: 2.8.0

I'm experiencing the same. I have prints that on the previous version took maybe 3 minutes to slice but now are taking 20minutes.

 

James

Napsal : 28/06/2024 6:13 pm
PJ
 PJ
(@pj-2)
Member
RE: 2.8.0

I'm experiencing a different problem but I think may be related. 

I'm running on Arch and PrusaSlicer is in the package repository for this distro.  I've been using PrusaSlicer for about 2 years with no issues at all - really excellent software until 2.8.0. 

Recently, I performed a full update of my system which included a PrusaSlicer update from 2.7.4 -> 2.8.0.   I've been developing a model in SolveSpace, making small incremental changes to the model with each revision as I go.  After the PrusaSlicer update to 2.8.0 I noticed my print time on this model increased by over 30 minutes.  Looking closely at the slicing statistics, the extra time is all due to head travel.  Watching the printer as it prints the first layer, the print head jumps all over the place.  It prints a few patterns in one area, then jumps clear across the build plate to another area, prints a few more patterns, then jumps back to the previous location and prints a few more patterns, then jumps again.  This behavior repeats itself over and over throughout the entire print.  It's like something has gone wrong with the algorithm that optimizes (minimizes) head travel before outputting gcode. 

Since I use git for revision control, I have all of the previous revisions of the model.  I used PrusaSlicer 2.8.0 to slice the previous revision I had sliced with 2.7.4 and that gcode behaved in same way as the current revision sliced with 2.8.0.  At that point, I reverted back to 2.7.4 and re-sliced both revisions.  The print time for both revisions took about 30 minutes less after being sliced with 2.7.4 and the head jumping across the build plate stopped.  In other words, reverting back to 2.7.4 put things back to "normal".   So this looks like it's either a bug in 2.8.0 or there's some configuration setting from 2.7.4 that wasn't preserved with the update to 2.8.0.

Again my problem is different than what you're seeing, but I think they are related.

Napsal : 03/08/2024 8:19 pm
kapasaki
(@kapasaki)
Member
RE: 2.8.0

I have noticed a similar annoying problem.

After updating from Prusaslicer 2.7.4 to 2.8.0, I noticed that at times the routing of the printhead movements is considerably more inefficient. Version 2.8.1 did not improve the situation.

This can be observed particularly well when printing a flat piece that has e.g. hexagon mesh.

Then the hexagon hole edges are printed one by one, but in a seemingly random order. That is, one at the left side, then one at the right side, one up, etc.

This results in plenty of unnecessary, long non-print movements from one side to another, increasing the print time significantly.

If I slice the same piece with ver. 2.7.4, or the recent Cura, then the hexagons are printed in order, one next to the other.

Is there some new (or old) setting I am missing here? Why are the new versions of Prusaslicer working like this now?

Napsal : 26/09/2024 12:58 pm
Share: