Bot releases are hidden (Show)
Published by lukasmatena about 2 years ago
This is final release of PrusaSlicer 2.5.0, introducing Arachne perimeter generator, Lightning infill, Pressure equalizer, STEP file import and various smaller features and bugfixes. The final release fixes a single bug found in PrusaSlicer 2.5.0-rc2. See the release logs of 2.5.0-alpha2, 2.5.0-alpha3, 2.5.0-beta1, 2.5.0-rc1 and 2.5.0-rc2 for the complete list of changes with respect to 2.4.2.
Published by lukasmatena about 2 years ago
This is second release candidate of PrusaSlicer 2.5.0, fixing bugs found in PrusaSlicer 2.5.0-rc1. See the release logs of 2.5.0-alpha2, 2.5.0-alpha3, 2.5.0-beta1 and 2.5.0-rc1 for the complete list of changes with respect to 2.4.2.
$SHELL
environment variable was undefined #8766
Published by lukasmatena about 2 years ago
This is a release candidate of PrusaSlicer 2.5.0, fixing several bugs found in beta1. See the release logs of 2.5.0-alpha2, 2.5.0-alpha3 and 2.5.0-beta1 for the complete list of changes with respect to 2.4.2.
The release candidate saves its profiles into regular PrusaSlicer configuration directory. When you first run it, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.
--datadir
if used).Published by lukasmatena about 2 years ago
This is the first beta release of PrusaSlicer 2.5.0, adding STEP file format import and fixing bugs found in the previous alpha. See the release logs of 2.5.0-alpha2 and 2.5.0-alpha3 for the complete list of changes with respect to 2.4.2.
To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. When you first run the beta, it will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one.
Starting with this release, PrusaSlicer is able to import STEP files, which is a format widely used for 3D modelling data exchange. Note that the model is tessellated on import and the slicing algorithms operate on the resulting triangle mesh, i.e., the model is not sliced analytically.
We use Open CASCADE Technology (OCCT) development platform to read the STEP files. It is a CAD kernel also used e.g. by FreeCAD or KiCad. Thanks @Open-Cascade-SAS for keeping it open-source. The import implementation itself was ported from BambuStudio, thanks @bambulab.
Parameters wall_add_middle_threshold
and wall_split_middle_threshold
were removed and are set automatically based on extrusion width. This results in better results in cases where the extrusion width of individual features differs (infill vs perimeters, etc).
Parameters min_feature_size
and wall_transition_length
can now be set in percents, in which case they are calculated based on nozzle diameter. Old profiles containing default values are converted into this percentage-based format, values that differ from the defaults are left untouched as the absolute values.
G1 Fx
lines which would not affect any actual extrusionswall_transition_filter_deviation
config option, which was evaluated incorrectly when set a percentagePublished by lukasmatena over 2 years ago
This is the third alpha release of PrusaSlicer 2.5.0, fixing bugs found in the previous alpha. See the release log of 2.5.0-alpha2 for the complete list of changes with respect to 2.4.2.
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.
G1
lines which were sometimes generated by the wipe tower (this is very old bug)Published by lukasmatena over 2 years ago
This is the first public alpha release of PrusaSlicer 2.5.0 (alpha1 was not public), introducing new perimeter generator Arachne, improved seam placement based on visibility, pressure equalizer, lightning infill and several more improvements and bugfixes.
The new perimeter generator Arachne and the new lightning infill were ported from Cura. The Arachne perimeter generator was implemented based on the paper [Kuipers et al., 2020], while the lightning infill was implemented based on [Tricard et al., 2019]. Big thanks to Ultimaker for keeping Cura open source and big kudos to Cura development team led by @nallath, to @BagelOrb for his research and majority of the Arachne implementation and to @BagelOrb and @rburema for the lightning infill implementation.
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 'classic' strategy for calculating perimeter extrusion paths is to offset contours of an object slice inwards by a constant extrusion width, one offset per perimeter. This was also the default algorithm in previous PrusaSlicer versions. However this simple algorithm does not handle thin regions well, as reported in these issues. Namely, thin regions cannot be filled with an integer number of fixed width extrusion lines. The classic way of handling narrow regions is to either not generate the innermost perimeter that does not quite fit, but to fill the remaining region with a gap fill algorithm, or to over-extrude the innermost perimeter. None of the two approaches are ideal: The gap fill may produce short segments of widely differing extrusion rates, while over-extruding may produce bulges on thin walls.
The developers of Cura recently implemented a new strategy named Arachne based on paper [Kuipers et al., 2020]. The Arachne generator produces perimeter loops and gap fills with varying extrusion width in such a way, that the slice area is filled without underflows and overflows with possibly continuous paths while respecting minimum / maximum extrusion width limits. The Arachne perimeter / gap fill generator really shines on objects with thin walls as thin boxes or labels.
In this PrusaSlicer version, we have ported the Arachne engine from Cura while keeping the old perimeter generator as an option. We made the Arachne perimeter generator default in our printer profiles. Thanks again to Ultimaker for developing Cura under open license.
The following picture demonstrates Arachne benefits on thin text: The classic perimeter generator fills text contours with many thin gap fill lines, while the Arachne perimeter generator widens the perimeter lines instead, producing cleaner prints quicker and with better surface quality.
However the Arachne perimeter generator has a tendency to round concave corners, as shown in the picture below. While the perimeter curves with circular segments at concave corners produced by Arachne are geometrically correct (they satisfy the constant offset distance requirement), they may not be optimal for FDM due to the tendency of extruded plastic to shrink into concave corners, thus the classic perimeter generator producing mitered offset curves with sharp corners may print more accurate concave corners. For most prints the Arachne perimeter generator is superior, but for some functional prints where the accuracy of concave corners is important the classic perimeter generator may be better.
Another case where the classic perimeter generator may be preferable are sharp corners. The classic perimeter generator with "detect thin walls" disabled trims the tips of sharp corners, but the print surface will likely be smooth due to constant extrusion width.
With "detect thin walls" enabled, the chopped off tip is filled with gap fill, which may not quite stick to the print.
Arachne generator produces connected lines with varying extrusion rate, where the extrusion rate variation will likely cause some visible artifacts on the outer surface of the print.
Infill serves dual purpose: To provide structural rigidity and to support top surfaces. In case the structural rigidity is not needed, a lot of material and printing time is saved with the new lightning infill, that is optimized to supports the top surfaces only. The lighting infill is based on paper [Tricard et al., 2019]. A branching structure is generated that gets progressively denser towards the top surfaces to support them reliably. Like the Arachne perimeter generator, we have ported the Lightning infill from Cura, thanks again for keeping Cura open source.
The following table compares the print time and filament consumption when printing the famous tree frog at 100% and 400% scale. The values for a 400% scale are enclosed in braces.
Infill type | Print time [min] | Filament total [g] | Filament Infill [g] | Filament saved on Infill |
---|---|---|---|---|
Gyroid 15% | 54 (1104) | 6.8 (204) | 1.5 (114) | 0% |
Support Cubic 15% | 51 (792) | 6.3 (152) | 1 (62) | 33% (46%) |
Lightning 15% | 55 (840) | 6.0 (111) | 0.6 (20) | 60% (82%) |
FDM printer consists of a motion system and an extrusion system. While the motion system loves to accelerate and decelerate smoothly to reduce vibrations, the extruder loves to extrude at a constant rate for best extrusion consistency. Unfortunately the optimal conditions of the motion system and extruder are contradictory. Bowden style extruders are especially sensitive to pressure fluctuations, due to the slack in bowden tube they are not able to reproduce rapid changes in extrusion rate reliably.
With bowden style extruders, moving from internal perimeter printed at high speed to external perimeter printed at slower speed the extruder often produces a bulge at the start of the external perimeter due to an excess extruder pressure. Similarly when moving from external perimeter to infill the extruder produces gap at the start of infill because of the extruder pressure deficit. To lessen these artifacts caused by rapid extruder pressure fluctuations, we have implemented an experimental "Pressure equalizer" feature.
Before moving from faster internal perimeter to slower external perimeter, the pressure equalizer slows down gradually the end of the internal perimeter to reach the extrusion rate of the external perimeter. Similarly when moving from the external perimeter to infill, the start of the infill is slowed down to external perimeter speed and accelerated gradually. The volumetric rate fluctuations are configured at Print Settings->Speed->Pressure equalizer
, they are limited by the new Max volumetric slope negative and Max volumetric slope positive configuration values. Slowing down infill after perimeter may increase print times excessively, thus it could be suppressed by setting Max volumetric slope positive to zero.
The following two images show gradual slowdown when external perimeter is about to be printed and comparison of the result with and without the feature activated.
The right picture shows bulges on external perimeters due to excess extruder pressure on a bowden style printer, while the bulges are mitigated in left picture thanks to the pressure equalizer.
Starting with this version, seam placement algorithm prefers regions which are not visible from the outside of the model at all or which are occluded from most directions. The new visibility algorithm is applied for seams set to Nearest or Aligned.
In addition, when paint-on seams are used and 'Aligned' is set, the resulting seam line attempts to find a sharp corner in the painted area and snap to it, leading to smoother lines along the sharp edge. Previous versions did not detect the sharp edge in this scenario #5857 #6086 #7180 #8014.
Also the new algorithm strives to produce possibly long and smooth seams on smooth surfaces, while the old algorithm often produced disconnected random bits on such surfaces #4416 #7180 #7759.
For multi-material or multi-part objects where a slice is split into multiple regions with each region having its own perimeter, the seams are newly hidden inside the object between the regions #5144 #6751.
---default---
profile.[Kuipers et al., 2020] Tim Kuipers, Eugeni L. Doubrovski, Jun Wu, Charlie C.L. Wang. "A Framework for Adaptive Width Control of Dense Contour-Parallel Toolpaths in Fused Deposition Modeling." Computer-Aided Design, vol. 128, p. 102907. 2020.
[Tricard et al., 2019] Thibault Tricard, Frédéric Claux, Sylvain Lefebvre. "Ribbed support vaults for 3D printing of hollowed objects." Computer Graphics Forum. 2019.
Published by lukasmatena over 2 years ago
This is final release of PrusaSlicer 2.4.2, which mostly fixes bugs found in 2.4.1 release. This release is functionally the same as 2.4.2-rc2. See the release logs of 2.4.2-rc1 and 2.4.2-rc2 for the complete list of bugfixes with respect to 2.4.1.
Published by lukasmatena over 2 years ago
This is second release candidate of a patch release fixing several bugs found in 2.4.1 release. See the previous release logs for the complete list of bugfixes and improvements in the 2.4 series.
Published by lukasmatena over 2 years ago
This is release candidate of a patch release fixing several bugs found in 2.4.1 release. See the previous release logs for the complete list of bugfixes and improvements in the 2.4 series.
Published by lukasmatena over 2 years ago
This is final release of PrusaSlicer 2.4.1, introducing G-Code Substitutions and fixing bugs found in 2.4.0 release. See the release logs of 2.4.1 betas and rcs for the complete list of bugfixes and improvements.
Published by lukasmatena over 2 years ago
This is a release candidate of PrusaSlicer 2.4.1, following 2.4.1-beta1 and 2.4.1-beta3. This release only fixes several bugs found in beta3. For list of new features in the 2.4 series, please read the release logs of all 2.4.0/2.4.1 releases.
The release candidate builds save their profiles to the same directory as the last release. If you already tested any of the PrusaSlicer 2.4.1 beta builds, you will be offered to import the recent beta profiles.
Published by lukasmatena over 2 years ago
This is another beta version of PrusaSlicer 2.4.1, a third patch release of PrusaSlicer 2.4.0 (beta2 was not released publicly). This patch release adds several little improvements and fixes some bugs found in the 2.4.1-beta1.
This release saves its configuration into a dedicated beta configuration folder to avoid breaking production profiles. PrusaSlicer 2.4.1-beta3 will offer to copy configuration from any older release into the beta configuration folder on the first invocation.
G92 E0
is present in layer change G-Code when relative extruder addressing is used. This is needed to prevent error accumulation in firmware. From this version, the check is only applied for Marlin firmware, because as far as we know, other firmware flavors do not suffer from this issue. #7846G92 E0
was missing and the error accumulation became visible, it would also be visible in the G-Code preview. Because only Marlin firmware suffers from this issue in reality and there is an explicit check for the G92 E0
when Marlin is selected, we have now modified the G-Code Preview so the loss of precision problem is not visualized. #4881, #5073, #6336Published by lukasmatena over 2 years ago
This is a beta version of PrusaSlicer 2.4.1, a first patch release of PrusaSlicer 2.4.0. This patch release adds several small improvements and 3rd party profiles, fixes some bugs found in the 2.4.0 final and typos found in translations.
This release saves its configuration into dedicated beta configuration folder to avoid breaking production profiles. PrusaSlicer 2.4.1-beta1 will offer to copy configuration from PrusaSlicer 2.4.0 or any older release into the beta configuration folder on first invocation.
PrusaSlicer supports processing of the generated G-code with an external post-processor for a long time. Launching an external post-processor is versatile, however it is complex to setup, the post-processing scripts must be distributed with the project and the interpreter running the post-processing script (for example Python) has to be available. We collected many real world use-cases for the post-processing scripts and concluded that many of them could be covered by a simple "Find and Replace" tool with regular expression matching and substitutions.
To make life easier for everyone who only needs basic post-processing, we now integrated such a tool directly into PrusaSlicer. It is accessible from Print Settings -> Output options and allows to add a number of find and replace pairs, with optional regex matching, case sensitivity and whole word matching, similar to what common text editors offer. The G-Code is processed before it is previewed, so your changes will be visible in the G-Code preview.
We hope this tool will make common post-processing tasks simpler, such as adding custom annotations, adjustments of output format such as in #6996), ringing cancellation, adjustments of per feature extrusion rate and similar.
Regular expression syntax of Perl is supported as described in boost Perl regular expression syntax, where a "single line" modifier mimics the Perl's s/
modifier. With regular expressions active, the "Replace with" pattern supports the "extended" syntax as described in boost extended format syntax. Lookahead and lookbehind are supported by the regular expression engine, but only for fixed length patterns. With regular expression disabled, \n
, \r
, \t
, \0
and \\
placeholders are supported in both "Find" and "Replace with" patterns similarly to Notepad++'s "extended" syntax.
The G-code find/replace post-processor processes G-code in blocks, where a single G-code block is generated for each layer starting with the Z up to move to the next layer. Multiple find/replace patterns are applied one by one to one G-code block before processing the next G-code block. Matching multi-line patterns is possible, however only inside one G-code block, most likely inside a single layer. Regular expressions are powerful but tricky, thus we recommend the regular expressions 101 online playground to get familiar with regular expressions and to test and fine tune the regular expressions modifying G-code before entering them into PrusaSlicer. Don't forget to switch the regex flavor to ECMAScript in the regular expressions 101 online playground.
An example of a quite powerful G-code modification by a reasonably complex regular expression: Increase the extrusion rate of top solid infill from the default 95 percent to 98 percent.
Find: (;TYPE:Top solid infill\n)(.*?)(;TYPE:|$)(?!Top solid infill)
Replace with: ${1}M221 S98\n${2}M221 S95\n${3}
Modifiers: regexp
, single line
initial_filament_type
and printing_filament_types
(useful for multi-material prints) #5300, #7684, #7673initial_tool
and initial_extruder
- zero based index of first extrudernum_printing_extruders
- number of printing extruders.G1
command which appeared before bridging perimeters were printed #7714G1 X 10
would not be correctly displayed in Preview. This was a bug introduced in PrusaSlicer 2.4.0 due to G-code export speed-up #7773.Published by bubnikv almost 3 years ago
This is a final release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3, 2.4.0-beta4, 2.4.0-rc and 2.4.0-rc2. The final release fixes bugs found in the second release candidate. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.
If you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.
Published by bubnikv almost 3 years ago
This is a second release candidate of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3, 2.4.0-beta4 and 2.4.0-rc. This release candidate fixes bugs found in the first release candidate. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.
The release candidate builds save their profiles to the same directory as the last release, however if you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.
Published by bubnikv almost 3 years ago
This is a release candidate of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3 and 2.4.0-beta4. This beta mostly fixes bugs found in beta4. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.
The release candidate builds save their profiles to the same directory as the last release, however if you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.
Ender2-Pro profiles were provided by @spuder.
Dutch localization was contributed by Simon Tillema.
Published by lukasmatena almost 3 years ago
This is the fourth beta release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2 and 2.4.0-beta3. This beta mostly fixes bugs found in beta3.
To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration.
--datadir
command line argument.Published by lukasmatena almost 3 years ago
This is the third beta release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1 and 2.4.0-beta2. This beta mostly fixes bugs found in beta2. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.
To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration.
Dictionaries for CZ, DE, ES, FR, IT and PL were updated by Prusa Research. Contributors are welcome, please check the localization guide.
Published by lukasmatena almost 3 years ago
This is the second beta release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3 and 2.4.0-beta1. This beta mostly fixes bugs found in beta1.
To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration.
As mentioned in beta1 change log, we continued in Windows dark mode implementation. This was a tedious work given the lack of support provided by Windows API, but we managed to skin most widgets and got reasonably nice look on both Windows 10 and 11 in the end. Main improvements with respect to 2.4.0-beta1 are included in https://github.com/prusa3d/wxWidgets/commit/4b7588eb0fec2d3e9b48e8b1d27e347ba91011a8:
We also improved dark mode version of "Change volume type" dialog and PrintHost dialogs.
When copying system info from About->System Info dialog into clipboard, OpenGL extensions are newly enclosed in <details>
tag so they are wrapped when inserted into a github issue #6830
Conversion from inches/meters to mm can now be done for all loaded objects at once, so the user does not have to confirm each object separately.
New functions in custom G-Code macro language: round(value)
(rounds to integer), digits(value, num_digits, num_decimals)
(rounds to num_digits and num_decimals, left filled with spaces), zdigits(value, num_digits, num_decimals)
(same as digits(...), only left filled with zeros) #3472
New placeholder parser values for output file name template: {num_objects}
(number of printable objects on the plater), {num_instances}
(number of all printable instances on the plater) #2735 #3339 #4607
When selecting SLA support points by the selection rectangle, even points that are slightly obscured by the object are selected. Until now, the center of the visualized sphere had to be visible, and it sometimes hid behind even very tiny bumps on the object.
When running 32-bit build of PrusaSlicer on 64-bit operating system, the user is instructed to download the correct version. While such application will run, it will be slower and will easily exhaust memory.
Fixed a crash when uploading G-Code to a print host for the second time #7170
When PrusaSlicer detects there is a more recent configuration folder than the one it is about to use (such as an alpha/beta specific folder), the user is asked if he/she wants to copy that configuration into the current folder. A configuration snapshot is taken in case there is something that would be overwritten.
Added a "Start printing after upload" checkbox for Repetier server (#5351, thanks @scott0122)
Sliders presented in the in-scene dialogs always allowed to type in the required value after Ctrl+mouse click. Because this useful feature was too hidden, we now show a small button to the right of each slider to switch it into this mode:
SLA material color can now be specified in Material Settings. The color is used for visualization in the scene and is also shown in the right panel combo box. Until now, the last FDM filament color was used.
Windows specific: When PrusaSlicer was downloaded from the Drivers bundle and installed using the installer, the created desktop shortcut launched external updater application instead of PrusaSlicer. The updater checked updates online, notified the user when a newer version was found and then started PrusaSlicer. The drawback was that command-line arguments were not correctly passed. This was now improved by switching the order: PrusaSlicer now runs the updater after it starts. This only happens when 'Check for application updates' is checked in Preferences and the built-in notification about the same thing is supressed in that case.
In-scene dialog widgets now accept Numpad Enter (until now, only Enter was accepted)
Shape Gallery dialog can now be closed by pressing Esc
Linux specific: Extruder colors in the right panel can be changed by clicking the cog wheel to the right of the respective filament preset #6759
When uploading G-Code to print host, the confirmation dialog now has an "Upload and Print" button (instead of a checkbox)
Changing purge volumes in multi material project did not mark project as unsaved #7265
Minimum diameter of the brush in the multi-material painting gizmo was reduced to 0.1 mm #7108
Configuration Wizard: when adding a printer profile with no default filament/material profile, the dialog is shown informing the user that one should be selected manually
When custom extrusion visibility is supressed in Preview, they are not taken into account when 'Volumetric Flow' view is shown. The scaling of the color palette is therefore more appropriate #7066
Context menu in the right panel now shows even when right clicking the name of the respective part, not just the 'Editing' column #7270
SLA material expansion correction can now be set independently for all three axes
Increased translation speed maximum in 3D connexion dialog to 30 (#3385)
'Scale to print volume' now works with circular beds
When color changes are added using the vertical slider in Preview, the colors are newly chosen randomly. Until now, a fixed predefined sequence of colors was used, leading to issues when the color changes were not added in order).
Out-of-bed detection was refactored and is now faster
Support generator now merges bottom contacts, top contacts and interface layers where possible (always possible with soluble supports, with non-soluble supports it is only possible when they are extruded without bridging and have the same layer height). This removes thin loops of interfaces that were sometimes generated with complex geometries and should generally result it nicer support interfaces.
Added experimental filtering of propagated support columns to two extrusions, overlapping by maximum 20%. This filtering step will remove spurious columns that do not support anything, but it may also remove supports supporting tiny islands (which would likely not be printable anyway without user intervention, such as extending the supported area by painting).
int()
function in the macro language: it did not accept an expression unless it was enclosed in double parentheses. Constants and variables were processed correctly #3472G1
commands were sometimes present in the G-Code due to the cooling slow down logic. This is an old bug present in 2.1.0 already #3058 #5176Published by lukasmatena almost 3 years ago
This is the first beta release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2 and 2.4.0-alpha3. This beta mostly fixes bugs found in alpha3. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas.
To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. If upgrading from any of the PrusaSlicer 2.4.0 alpha release, you may consider to rename your PrusaSlicer-alpha directory to PrusaSlicer-beta.
In order to focus our future effort, we decided to optionally collect some general information about the systems PrusaSlicer is commonly executed on. Such system information will help us to deprecate support of obsolete platforms in order to concentrate on up to date hardware and operating systems to reduce maintenance cost, improve PrusaSlicer performance and to bring up new features. Please help us by submitting your system configuration to us, otherwise it may happen that we will deprecate support of some old or not so common systems too early.
The system configuration data collected is strictly anonymous and the full content of the data collected is available to the user for review from the new "Send system info" dialog. A unique system identifier is generated for the machine submitting the system configuration to identify duplicate records submitted multiple times by the same machine. The unique system identifier is anonymized by hashing with MD5 and salted with a "salt", which is unique to the "system info" service. We believe our method is sufficiently anonymous, however we are certainly open to suggestions by the security experts.
When connected to internet, a dedicated dialog will open on application start up (or second application startup, if Configuration Wizard is opened on first start-up), showing exactly what information PrusaSlicer collects. When confirmed, the data is sent to our server using a secure channel (SSL) and the dialog no more shows up at the following application start-ups. No other data than those presented by the "Send system info" dialog are submitted, and it is not possible to trace one's identity based on the data submitted. One can of course decline to submit the system information data.
FDM supports were improved significantly in PrusaSlicer 2.4.0 alphas. In beta1, the FDM supports were improved further.
A conventional FDM support generator generates support towers based on the differences between successive object layers and PrusaSlicer's support generator is not different. Such a local algorithm often either produces excessive supports, or it does not support long thin features at all. While we are working on a smarter algorithm that takes global geometry of an object into account, it will take us some time to make it ship shape. In the meantime, we made some adjustments to the current local algorithm. Namely, the FDM support generator algorithm was designed before introduction of the support blockers / enforcers and paint-on supports, thus it tried to be smart about not introducing too much supports while not missing supports below thin features, however such algorithm behaved unintuitively. Thus in this release, we switched off some of the unintuitive filtering steps and we rather rely on the user giving hints to the support generator using the support blockers / enforcers and paint-on supports.
We are still fine tuning our print profiles for the new "snug" supports. The "snug" supports behave differently than the old "grid" supports. You may want to experiment with different gaps between object and support interfaces, also the "snug" supports may require more interface layers than the "grid" supports to produce wide enough regions to be printable FDM technology.
When possible, PrusaSlicer newly places seams on internal perimeters close to external seams, reducing travel moves and retractions. For leaky extruders, bowden setups and leaky materials (PET, PVA) reducing travel between perimeters reduces gaps at their starts. The seams between the nested perimeters are not aligned exactly, but they are staggered by a short distance to reduce bulge of the outer most seam #6790, #6400, #6741, #6494, #6186, #5149.
<details>
tag, thus helping to make the github issues easier to read #6830.default_acceleration
parameter is zero. The user interface already suggested this condition by graying out the per feature acceleration parameter fields with default_acceleration
zeroed, but the G-code generator did not respect that #3409, #6743 thanks @jschuh.