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 resolve issues that until yesterday could halt production.
- OrcaSlicer v2.3.2 — version 2.3.2 — 23 March 2026
- Marlin 2.1.3-b3 — version 2.1.3-b3 — 25 June 2025
OrcaSlicer: enhanced 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 resolves a bug that caused crashes during G-code export in multi-material prints with Wipe Tower. According to the release notes, the issue occurred when mesh data was not initialized correctly, 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. An apparently trivial error, but capable of stalling the software and forcing a restart.
OrcaSlicer v2.3.2 fixes a path traversal vulnerability in .3mf files that could allow the execution of arbitrary code. If you work with 3MF files received from third parties, the update is essential.
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, including the brim in the size estimate. 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 serves to avoid incorrect configurations by less experienced users, given the still experimental nature of the function.
Marlin: new life for modern hardware
Beta 2.1.3-b3 brings native support for new boards and optimizes performance on GD32 architectures, expanding the hardware compatibility of the firmware.
Marlin 2.1.3-b3 introduces significant optimizations for GPIO on GD32 processors, with measurable improvements in speed. The release notes explicitly mention support for the Creality v4.2.7 based on GD32 and the update of the GD32 MFL platform to version 1.0.3.
Native support for FLY boards arrives 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 TMC driver baud rate on these boards.
- Native support for GD32 processors with optimized GPIO
- Compatibility with 7 new boards from the FLY family
- Wireless firmware updates (OTA) on STM32F401RE Creality
- Support for Trinamic TMC2240 drivers via SPI
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 every firmware update, simplifying maintenance on remote or hard-to-access 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 targeted fixes in 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 who receives 3MF files from clients or external collaborators must update immediately. The path traversal vulnerability fixed in OrcaSlicer v2.3.2 could allow arbitrary code execution through specially crafted 3MF files.
| Use scenario | Software | Concrete benefit |
|---|---|---|
| Multi-material prints | OrcaSlicer v2.3.2 | No crash during G-code export |
| 3MF files from third parties | OrcaSlicer v2.3.2 | Protection from code execution |
| GD32/FLY boards | Marlin 2.1.3-b3 | Native support + fast GPIO |
| Remote updates | Marlin 2.1.3-b3 | Creality wireless OTA |
Users with printers based on MCU GD32 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 safety 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 references in the configuration files. The release notes do not specify an automatic migration procedure.
As a beta, Marlin 2.1.3-b3 may present instability on less common hardware configurations. The release notes report that some fixes were applied after the initial release, suggesting an ongoing stabilization process.
If you have manually modified Marlin configuration files, verify compatibility with the new FYSETC environment names before updating. Some old configurations may not work without changes.
OrcaSlicer v2.3.2 hides the “Adaptive Volumetric Speed” function in developer mode. If you used it regularly, you will need to enable developer mode to access it again. The choice reflects the still experimental nature of the function.
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. OrcaSlicer v2.3.2's critical fixes 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
Q&A
- What stability bugs does OrcaSlicer v2.3.2 fix in multi-material prints?
- It eliminates a crash during G-code export caused by incorrectly initialized mesh data. It also fixes an infinite loop that was triggered when the top solid infill density was set to zero, causing the software to stall.
- What security vulnerability was fixed in OrcaSlicer v2.3.2 and why is it important to update?
- A path traversal vulnerability in .3mf files was fixed, which could allow the execution of arbitrary code. The update is essential for those who receive 3MF files from third parties, as it eliminates the risk of executing malicious code.
- What changes for the purge tower in OrcaSlicer v2.3.2 when changing printer presets?
- The purge tower no longer ends up outside the build plate after changing presets. The software automatically recalculates the position including the brim in the size estimate, preventing slicing results from being invalidated.
- What are the main hardware news introduced by Marlin 2.1.3-b3?
- The beta adds native support for GD32 processors with optimized GPIO and compatibility with seven new FLY boards. It also introduces wireless OTA firmware updates on STM32F401RE Creality and support for Trinamic TMC2240 drivers via SPI.
- What precautions are necessary for those updating to Marlin 2.1.3-b3 with custom configurations?
- As it is a beta, it may present instability on less common hardware. Additionally, some FYSETC environments have been renamed, so those using FYSETC S6 or Spider boards must manually update references in the configuration files.
- Why was the 'Adaptive Volumetric Speed' feature moved to developer mode in OrcaSlicer v2.3.2?
- This choice serves to avoid incorrect configurations by less experienced users, given the still experimental nature of the feature. Those who were using it will need to enable developer mode to access it again.
