perksoffline.blogg.se -

#PAINT 3D FOR MAC WINDOWS 10#
#PAINT 3D FOR MAC WINDOWS#

#PAINT 3D FOR MAC WINDOWS#

Windows specific: InnoCielo Meridian injects AMHook.dll into PrusaSlicer, which makes PrusaSlicer to crash.

#PAINT 3D FOR MAC WINDOWS 10#

This also solves the Windows 10 dark mode issue, where we were not able to adjust status bar colors #6860.

Bottom status bar was removed and replaced by notifications showing progress of slicing and the "abort slicing" button.

This has been improved: The fixed / remaining errors are newly shown clearly at the side panel and the "exclamation mark" icon is shown with white color for a completely fixed mesh, while an orange color is used for a not fully fixed mesh.

Mesh repair statistics used to be confusing: It was not quite clear which errors were fixed during import and whether there are any errors remaining after the mesh import and repair.

3MFs, AMFs and OBJs are loaded considerably faster, models imported from them are no longer repaired automatically (see 'Architecture and infrastructure' below for further details).

While the new G-code conforms to standard, it may not be consumed by some non-conforming applications #6996.

The G-Code coordinates are newly exported without emitting the leading and trailing zeros, which makes the G-code a bit smaller.

This results in significant improvement of performance: The total slicing time is now 2x to 4x shorter, higher speed up is achieved on high-end CPUs #2263.

G-Code export was parallelized and optimized.

Improvements with respect to PrusaSlicer 2.4.0-alpha1 To let you enjoy the alpha without worries, the alpha builds save their profiles into PrusaSlicer-alpha directory, so you may use the alpha side by side with the current release without ruining your production configuration. The most important change is significant speed-up of the G-Code generator. This alpha adds several new features and improvements and it fixes bugs found in the first alpha. This is the second alpha release of PrusaSlicer 2.4.0, following 2.4.0-alpha1.

Fixed crash after a new resin was added in Configuration Wizard while an SLA printer was active.

This was a regression due to support refactoring in PrusaSlicer 2.4.0-alpha1.

First layer support expansion was not applied when printing without raft.

Fixed possible crash when an object was deleted with the simplification gizmo active.

SLA resin material config option 'Correction for expansion' was not applied correctly, namely the Z correction was applied to Y axis #7013.

Importing such SL1 archives is newly allowed, however the SLA mode needs to be active and the active Print / SLA material / Printer presets will be used #6915.

SLA specific: Importing SL1 archives into PrusaSlicer did not work for SL1 archives produced by old PrusaSlicer versions, which did not store PrusaSlicer Print / SLA material / Printer presets into the SL1 archive.

Fixed a G-Code Viewer crash when loading G-Codes generated by SuperSlicer #7008.This was a regression with respect to PrusaSlicer 2.4.0-alpha1 #7005. Standalone G-Code Viewer was modifying access times of G-code files loaded.

This was a regression due to G-code parser speed up #7016.

The G-Code reader did not process G28, M132 and M402 correctly, leading to issues such as shifted models in the preview.

Fixed import of AMF files, also broken in 2.4.0-alpha2 due to admesh eradication refactoring #7015.

The "inflated" 3MFs generated by alpha2 are now being shrunk back when loaded and saved again with 2.4.0-alpha3. Repeated loading and saving gradually increased size of 3MF files containing multi-material objects or objects with modifier meshes #7011, slicing some models was broken #7039 and some models were positioned incorrectly in Z #7010.

The triangle mesh simplification dialog newly allows to render the model in wireframe view, which helps to better asses the achieved mesh complexity and decimation rate.īugs fixed, reported for PrusaSlicer 2.4.0-alpha2.

The new 'Slicing finished' notification automatically fades out after 2 seconds #7017.

"New project" and "Load project" actions newly clear the undo/redo stack by default, however one may revert to the old behavior by unchecking "Clear Undo / Redo stack on new project" in preferences #2812.

This means that fine undo/redo is available during painting, but the main stack is not flooded with the individual events after the painting is finished. When the painting tool is closed, all the snapshots taken during painting are compacted into one. Instead, the events are added into the main stack.

Painting tools (supports, seam, multimaterial) no longer use a separate undo/redo stack.

Improvements with respect to PrusaSlicer 2.4.0-alpha2 This alpha mostly fixes bugs found in alpha2. This is the third alpha release of PrusaSlicer 2.4.0, following 2.4.0-alpha1 and 2.4.0-alpha2.