Critical bugs fixed: OrcaSlicer and Marlin are now more reliable

Critical bugs fixed: OrcaSlicer and Marlin are now more reliable

Sudden crashes during slicing, security vulnerabilities in 3MF files, and hardware incompatibility: the latest releases of OrcaSlicer and Marlin fix issues that until yesterday could block production.

OrcaSlicer: reinforced security and stability

OrcaSlicer version 2.3.2 closes critical flaws and improves reliability in complex slicing, eliminating recurring crashes and security vulnerabilities.

OrcaSlicer v2.3.2 fixes a bug that caused crashes during G-code export in multi-material prints with Wipe Tower. According to the release notes, the problem occurred when mesh data was not properly initialized, blocking the entire slicing process.

The release also fixes an infinite loop that was triggered when the top solid infill density was set to zero. A seemingly trivial error, but capable of freezing the software and forcing a hard restart.

The wipe tower no longer ends up outside the print bed after changing the printer preset. OrcaSlicer v2.3.2 automatically recalculates the tower position when presets are modified, also including the brim in the size estimation. This prevents slicing results from being invalidated immediately after the first processing.

The “Adaptive Volumetric Speed” function has been moved to developer mode. According to the OrcaSlicer v2.3.2 notes, this choice is to avoid incorrect configurations by less experienced users, given the still experimental nature of the function.

Marlin: new breath for modern hardware

Beta 2.1.3-b3 brings native support for new boards and optimizes performance on GD32 architectures, expanding the firmware's hardware compatibility.

Marlin 2.1.3-b3 introduces significant optimizations for GPIO on GD32 processors, with measurable speed improvements. The release notes explicitly mention support for the GD32-based Creality v4.2.7 and the update of the GD32 MFL platform to version 1.0.3.

Native support for FLY boards comes with this beta: FLY_D5, FLY_DP5, FLY_D7, FLY_D8, FLY_D8_PRO, FLY_SUPER8_PRO and FLY_CDY_V3 are now officially compatible. Marlin 2.1.3-b3 also includes specific configurations for the baud rate of TMC drivers on these boards.

Marlin 2.1.3-b3 adds the OTA_FIRMWARE_UPDATE function for wireless updates on STM32F401RE Creality boards. This eliminates the need to physically connect the printer to a PC for each firmware update, simplifying maintenance on remote or hard-to-reach installations.

Support for Trinamic TMC2240 drivers via SPI is now available. According to the Marlin 2.1.3-b3 notes, the implementation required several subsequent fixes to ensure stability, but the driver is now fully functional.

Who benefits (and how)

Multi-material, external 3MF files, and new controllers become more manageable thanks to the targeted fixes of both releases.

If you work with multi-material prints and purge towers, OrcaSlicer v2.3.2 eliminates crashes during G-code export and resolves tower positioning issues. Complex prints become more reliable, without sudden interruptions mid-slicing.

Anyone receiving 3MF files from clients or external collaborators must update immediately. The fixed path traversal vulnerability in OrcaSlicer v2.3.2 could allow arbitrary code execution through specially crafted 3MF files.

Users with printers based on GD32 MCU or FLY boards directly benefit from Marlin 2.1.3-b3. GPIO optimizations improve firmware responsiveness, while native support eliminates complex manual configurations.

Trade-offs and field reality

Some sacrifice in terms of existing configurations and compatibility, but with tangible returns in security and stability.

Marlin 2.1.3-b3 renames some FYSETC environments. If you have custom configurations for FYSETC S6 or Spider boards, you will need to update the references in the configuration files. The release notes do not specify an automatic migration procedure.

Being a beta, Marlin 2.1.3-b3 may present instability on less common hardware configurations. The release notes indicate that some fixes were applied after the initial release, suggesting a stabilization process still ongoing.

OrcaSlicer v2.3.2 hides the “Adaptive Volumetric Speed” feature in developer mode. If you used it regularly, you will need to enable developer mode to access it again. This choice reflects the still experimental nature of the feature.

The OrcaSlicer v2.3.2 release notes do not report significant risks: the release mainly contains bug fixes. For Marlin 2.1.3-b3, the main risk concerns possible incompatibilities with outdated custom configurations.

Conclusion

Updating OrcaSlicer and Marlin today means reducing daily frustrations and opening the door to greater safety and modern hardware support. The critical fixes in OrcaSlicer v2.3.2 eliminate recurring crashes and security vulnerabilities, while Marlin 2.1.3-b3 brings native compatibility for recent hardware and tangible optimizations on GD32 processors.

Check if your configuration can benefit from these updates, especially if you use multi-material or GD32/FLY boards. The improvements in stability and security justify the time investment for the update, even considering the small adjustments needed for custom configurations.

article written with the help of artificial intelligence systems