You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a separate GitHub reports for each of these issues is extremely time-consuming, so it will be better to list them, track and update in a single tracking issue.
So, here's my list of incomplete/buggy features that have been added in 2.3.2 (and also related issues):
The setting is displayed for all filament profiles in advanced mode, but only works with BambuLab filaments (profiles with pre-configured filament_adaptive_volumetric_speed model). Moreover, currently OrcaSlicer doesn't have a single filament profile with non-zero model, so displaying this setting doesn't make sense. I think it should be only visible in the developer mode (ideally, with a disclaimer in tooltip, not only in the wiki).
3. Prime tower improvements don't work [attempt to fix: #12782]
Description
Flushing and notch at the starting point — added flushing actions for the interface layer: the nozzle wipes before flushing (rather than after), then prints the prime tower directly (release notes)
The notch (skip points option) doesn't work with regular profiles, only with BambuLab ones:
Extra pre-extrusion before the interface layer — before printing the prime tower, the interface layer now performs a short pre-extrusion (release notes)
Changing Pre-extrusion distance/length do nothing even with Bambu printers (check the attached gcodes using a diff finder):
Bambu Wiki says that this feature requires Skip points to be enabled, so that may be an additional reason why it doesn't work for regular printers. But as you can see above, it doesn't work even with BambuLab A1 with skip points applied.
Also you can see in previous demo that I changed ironing area as well, but the only difference in the code is in the settings section.
I didn't check other features added in #12266, but I'm afraid all of them are broken.
The Internal ribs option also doesn't affect regular printers: OrcaSlicer applies a different tower algorithm for non-bambu printers, that shrinks the tower when the interface volume is lower.
Demo:
Bambu printers
Regular printers
Enabled
Disabled
The tower width remains the same, ribs can be generated
The width is automatically reduced, no ribs in both scenarios
After adding H2D support to OrcaSlicer, the Filament Gcode legend became misaligned and unnecessarily wide. I suspect the new filament grouping section.
The plate grouping button is invisibly active and available for all other printers after switching to them:
Demo2026.March.08.21.55.mp4
10. Filament grouping is applied and forced to Auto for unsupported printers
Description
Regular dual-nozzle printer profiles with configured extruder_printable_area rely on the model placement safety check. The problem here is that OrcaSlicer always assumes that the Bambu filament grouping mode is used in the printer and is set to "auto", but the grouping feature is not available for non-bambu printers. Thus, model placement is never verified (until I (ab)use another bug to change the Bambu grouping to manually set the extruder for slicing):
2026.March.21.03.51.2.mp4
Solution: filament grouping dialog (both the popup and plate button) and the entire grouping logic should be disabled for all printer profiles without MMUs (including H2D) and only enabled for multi-nozzle printers with connected MMUs. The initial popup dialog also shouldn't be displayed for these profiles unless painted material count exceeds the number of nozzles.
3MF: Filament grouping + dual nozzle.zip
Ⅱ. Regressions/bugs in updated/new features
1. Lagging tool position/speed profile windows [Fixed in #12707]
Description
The speed profile menu and the main window don't update their size when moving layer slider using arrows and requires mouse movement for that
3. Temperature mixing notifications [Fixed in #12700]
Description
The notifications reappear after clicking to the selected plate or attempting to move a single plate (should appear only after switching between different plates)
2026.March.08.17.45.mp4
4. Incomplete support infill pattern warnings [Fixed in: #12710]
Description
We have the new notification for the regular supports (The Lightning base pattern is not supported by this support type; Rectilinear will be used instead.), but the Hollow pattern (shouldn't it be called "None"?) is also incompatible with regular supports and is silently replaced to Rectilinear without a notification:
New manifestation of #6970 – the same Flow rate string is used now to describe both the Flow rateratio calibration and the volumetric speed metrics of a line in Gcode preview:
Flow ratio
Flow rate (volumetric speed)
This leads to inability to translate it correctly into languages where the Flow part in Flow rate and Flow ratio should be replaced with different translations according to the following rate/ratio context. I think the root problem here is a term misuse, and the proper fix for that is to rename the calibration section from Flow rate to Flow ratio.
The tooltip of the zoom button has a broken width calculation
Language
Screenshot
English
Russian
Deutsch
I don't know how it decides to break the lines, but Deutsch suffers the most
7. is_extruder_used placeholder can't be used in Gcode header
Description
The mentioned placeholder (and probably some others) is not available for use in the new Gcode header section for no apparent reason. This limits usability of this new feature for some IDEX/dual-nozzle printers that rely on header information from their proprietary software (for example, FlashForge Creator series).
One of the Machine Gcode sections is randomly halved in height
Description
In 2.3.2, after some actions, height of one of the printer G-code sections become 2 times smaller, which makes it very difficult to work with the code. The weird thing is that the bug randomly affects only one of the sections at a time, and the bug "selects" a new section to change after some additional actions (like changing a tab or creating a new project). This bug was introduced in 2f2f0df.
2.3.1
2.3.2
How to reproduce:
1. Open a new OrcaSlicer instance
2. Create a new empty project
3. Open printer profile settings
4. Go to Machine G-code
5. See that the 1st field height is only 4 strings
6. Go to Notes and see the same
7. Return back to the G-code tab and see that the height of the field has changed
8. Scroll a bit and find another randomly shrinked field
Demonstration:
2026.March.22.20.03.mp4
I couldn't reproduce the issue in 2.3.1 and a previous commit (cca8dc9).
Prepare/preview frame shifts upwards/downwards during the mouse/keyboard activity
Description
The window is constantly shifted during the work process. Also happens when pressing Alt and some other buttons. This annoying problem hasn't been presented in 2.3.1.
For some reason, OBS can't record this window movement, so here's the recording from camera:
Creating a separate GitHub reports for each of these issues is extremely time-consuming, so it will be better to list them, track and update in a single tracking issue.
So, here's my list of incomplete/buggy features that have been added in 2.3.2 (and also related issues):
Ⅰ. New ports from Bambu Studio
1.[Fixed in #12696]BambuStudio warningheaderDescription
The warning is used for the following messages:
"\"%s\" part's mesh contains errors. Please repair it first.OrcaSlicer/src/slic3r/GUI/GUI_ObjectList.cpp
Line 5950 in d6761fe
"\"%s\" will exceed 1 million faces after this subdivision, which may increase slicing time. Do you want to continue?OrcaSlicer/src/slic3r/GUI/GUI_ObjectList.cpp
Line 5961 in d6761fe
2. Adaptive flowrate[Fixed in #12688]Description
The setting is displayed for all filament profiles in advanced mode, but only works with BambuLab filaments (profiles with pre-configured
filament_adaptive_volumetric_speedmodel). Moreover, currently OrcaSlicer doesn't have a single filament profile with non-zero model, so displaying this setting doesn't make sense. I think it should be only visible in the developer mode (ideally, with a disclaimer in tooltip, not only in the wiki).OrcaSlicer/src/libslic3r/PrintConfig.cpp
Line 2464 in d6761fe
3. Prime tower improvements don't work [attempt to fix: #12782]
Description
The notch (
skip pointsoption) doesn't work with regular profiles, only with BambuLab ones:Demo
Changing Pre-extrusion distance/length do nothing even with Bambu printers (check the attached gcodes using a diff finder):
Demo and gcodes
Pre-extrusion and length do nothing.zip
The spiral tower ironing moves aren't applied to printers other than H2D:
Demo
Bambu Wiki says that this feature requires
Skip pointsto be enabled, so that may be an additional reason why it doesn't work for regular printers. But as you can see above, it doesn't work even with BambuLab A1 with skip points applied.Also you can see in previous demo that I changed ironing area as well, but the only difference in the code is in the settings section.
I didn't check other features added in #12266, but I'm afraid all of them are broken.
4. Internal ribs [attempt to fix: #12742]
Description
The
Internal ribsoption also doesn't affect regular printers: OrcaSlicer applies a different tower algorithm for non-bambu printers, that shrinks the tower when the interface volume is lower.Demo:
5. Issues with Wiki links in the ported GUI elements [2/4 fixed]
Description
Filament grouping wiki (3 places) refers to a local Bambu Studio .html, which doesn't exist in OrcaSlicer[Fixed in #12880]Demo
OrcaSlicer/src/slic3r/GUI/FilamentGroupPopup.cpp
Line 150 in d6761fe
OrcaSlicer/src/slic3r/GUI/GCodeViewer.cpp
Line 2768 in d6761fe
Links to local Wiki pages are broken with non'latin paths (and also it opens https instead of the local path)
Wiki link in the OBJ color import opens bambustudio Wiki[Fixed in Some QoL tweaks #12700]OrcaSlicer/src/slic3r/GUI/ObjColorDialog.cpp
Lines 53 to 56 in d6761fe
Wiki link in the PLA/PETG warning refers to Bambu Studio Wiki (intentional?)
OrcaSlicer/src/slic3r/GUI/GLCanvas3D.cpp
Line 9698 in d6761fe
Demo
2026.March.08.17.56.mp4
6. Broken encoding in the OBJ import[Fixed in #12698]Description
See the demo above at 0:30. The bug is probably there:
OrcaSlicer/src/slic3r/GUI/ObjColorDialog.cpp
Line 927 in d6761fe
7. Filament view mode with H2D
Description
After adding H2D support to OrcaSlicer, the
FilamentGcode legend became misaligned and unnecessarily wide. I suspect the new filament grouping section.Demo:
8. Flushing volumes window[Fixed in #12694]Description
The new window cannot be closed using Esc (which may be pretty annoying).
You can scroll the window content using touchpad in a weird way:
Demo
Scrollable.flushing.window.mp4
9. H2D filament grouping[Fixed in #12693]Description
The grouping window can not be closed using
EscThe plate grouping button is invisibly active and available for all other printers after switching to them:
Demo
2026.March.08.21.55.mp4
10. Filament grouping is applied and forced to
Autofor unsupported printersDescription
Regular dual-nozzle printer profiles with configured
extruder_printable_arearely on the model placement safety check. The problem here is that OrcaSlicer always assumes that the Bambu filament grouping mode is used in the printer and is set to "auto", but the grouping feature is not available for non-bambu printers. Thus, model placement is never verified (until I (ab)use another bug to change the Bambu grouping to manually set the extruder for slicing):2026.March.21.03.51.2.mp4
Solution: filament grouping dialog (both the popup and plate button) and the entire grouping logic should be disabled for all printer profiles without MMUs (including H2D) and only enabled for multi-nozzle printers with connected MMUs. The initial popup dialog also shouldn't be displayed for these profiles unless painted material count exceeds the number of nozzles.
3MF: Filament grouping + dual nozzle.zip
Ⅱ. Regressions/bugs in updated/new features
1. Lagging tool position/speed profile windows[Fixed in #12707]Description
The speed profile menu and the main window don't update their size when moving layer slider using arrows and requires mouse movement for that
2026.March.09.14.35.mp4
[Internal ribs] Bambu prime tower.zip (you can test this at the last layer of the tower, or just slice a sphere with
arc fittingenabled)2. Unable to close some notifications[Fixed in #12689]Description
Unable to close some notifications in preview mode without additional actions
Notifications.mp4
This notification is also affected:
(probably a common issue for all stacked notifications)
You can test these notifications using this 3MF: [Internal ribs] Regular prime tower.zip
3. Temperature mixing notifications[Fixed in #12700]Description
The notifications reappear after clicking to the selected plate or attempting to move a single plate (should appear only after switching between different plates)
2026.March.08.17.45.mp4
4. Incomplete support infill pattern warnings[Fixed in: #12710]Description
We have the new notification for the regular supports (
The Lightning base pattern is not supported by this support type; Rectilinear will be used instead.), but theHollowpattern (shouldn't it be called "None"?) is also incompatible with regular supports and is silently replaced to Rectilinear without a notification:5. New localization issues[Fixed in : #12773]Description
New manifestation of #6970 – the same
Flow ratestring is used now to describe both the Flowrateratio calibration and the volumetric speed metrics of a line in Gcode preview:This leads to inability to translate it correctly into languages where the
Flowpart inFlow rateandFlow ratioshould be replaced with different translations according to the followingrate/ratiocontext. I think the root problem here is a term misuse, and the proper fix for that is to rename the calibration section fromFlow ratetoFlow ratio.6. Zoom button tooltip[Fixed in #12692]Description
The tooltip of the zoom button has a broken width calculation
7.
is_extruder_usedplaceholder can't be used in Gcode headerDescription
The mentioned placeholder (and probably some others) is not available for use in the new Gcode header section for no apparent reason. This limits usability of this new feature for some IDEX/dual-nozzle printers that rely on header information from their proprietary software (for example, FlashForge Creator series).
Example:
Ⅲ. Regressions compared to 2.3.1
2.3.2 changelog frame width calculates incorrectly #12370(fixed in: #12265)Regression in 2.3.2-dev: Anycubic Kobra 3 can't start printing, the gcode stuck in
parsingstate #12444 (fix: #12455)Customize Filament Sequence plate setting ignored after first layer #12449(fixed in: #12767)2.3.2 Release crashes when switching to device screen. #12451
Seam no longer showing in preview. #12556(fixed in: #12364)Flushing volume window too small, cuts off buttons at bottom #11702
[ACCESS_VIOLATION] in 2.3.2-dev when trying to slice using profile for 2.3.1 #12704 (fix: #12856)
[2.3.2-dev] Selection in sidebar removed when mouse moves out of sidebar #12823 (fix: #12834)
Spiral z-hop and 5mm retract are forcefully applied when changing material (ignoring the settings)
Description
Project file: #12731.zip
Zero flushing volume warning is displayed for single-material parts
Description
Project file: lamp v2.2.zip
One of the Machine Gcode sections is randomly halved in height
Description
In 2.3.2, after some actions, height of one of the printer G-code sections become 2 times smaller, which makes it very difficult to work with the code. The weird thing is that the bug randomly affects only one of the sections at a time, and the bug "selects" a new section to change after some additional actions (like changing a tab or creating a new project). This bug was introduced in 2f2f0df.
How to reproduce:
1. Open a new OrcaSlicer instance
2. Create a new empty project
3. Open printer profile settings
4. Go to Machine G-code
5. See that the 1st field height is only 4 strings
6. Go to Notes and see the same
7. Return back to the G-code tab and see that the height of the field has changed
8. Scroll a bit and find another randomly shrinked field
Demonstration:
2026.March.22.20.03.mp4
I couldn't reproduce the issue in 2.3.1 and a previous commit (cca8dc9).
Prepare/preview frame shifts upwards/downwards during the mouse/keyboard activity
Description
The window is constantly shifted during the work process. Also happens when pressing Alt and some other buttons. This annoying problem hasn't been presented in 2.3.1.
For some reason, OBS can't record this window movement, so here's the recording from camera:
VID_20260404_202608-compressed.mp4