MAC (M1 Prozessor, 8GB RAM) bad operating behavior after slicing

[S3D-Jason]

These factory files you are attaching have 10 or so processes. Which exact ones are you selecting when slicing?

[TheBum]

Stock MacBook Air, 15-inch, M2, 2023, MacOS 14.2.1. Nothing custom in terms of hardware or software.

Here's another with the same behavior:

I tried this last factory file on my M2 MBP w/ 32GB of RAM and I see the same lagging after slicing. I've been seeing it on my more complex models before that. I'm running S3D 5.1.2 and macOS 14.3.

Here's a screen video capture in real time: https://youtu.be/5H5xP4l7NLY

[S3D-Jason]

Which processes did you select? Many of those processes are just printing the same region twice, so you definitely wouldn't want to select all of them since that would just make the preview slower for no reason (imagine drawing the same thing 5x, that just makes it 5x slower).

[waterbornewarrio]

Which processes did you select? Many of those processes are just printing the same region twice, so you definitely wouldn't want to select all of them since that would just make the preview slower for no reason (imagine drawing the same thing 5x, that just makes it 5x slower).

Selecting any single process (with custom zones set to print the full height) replicates the problem... *except* the process "top" which is a one perimeter, zero infill profile. So it does seem "density" or complexity-related...

[TheBum]

Here's an example with a lot of parts in one print. All the infill is only 15%.

[S3D-Jason]

That factory file is MUCH larger than the prior examples. It create well over 1 million lines of output, so that is expected to be slower to render. I think the OP was seeing slower rendering with much smaller files, so that's mostly what I think this thread was investigating.