Built-in Temp Tower temperature transitions misaligned by a single layer when using non-0.2mm layer heights #778

New Issue

MrUnknownDE · 2026-04-05T16:30:27+02:00

MrUnknownDE commented

2026-04-05 16:30:27 +02:00

Originally created by @TimetravelerDD on 2/14/2026

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.1

Operating System (OS)

Windows

OS Version

Windows 11

Additional system information

No response

Printer

Snapmaker U1

How to reproduce

When using the built-in Temperature Tower from the Calibration menu, the automated script that changes the extruder temperature appears to be hardcoded for a 0.20mm layer height. If a user tries to generate and slice the temp tower using a different layer height profile (e.g., 0.16mm), the temperature changes do not align perfectly with the physical geometry of the blocks.

The shift is not drastic enough to ruin the overall overhangs, but it misses the start of the new block by exactly one layer. This causes the surface of that specific boundary layer to print at the incorrect temperature, invalidating close inspections of surface quality for that height.

Steps to Reproduce

Open OrcaSlicer and select a printer profile.
Select a 0.16mm (or any non-0.20mm) print profile in the Process tab.
Navigate to Calibration -> Temperature in the top menu bar.
Generate the standard Temperature Tower.
Click Slice plate.
Go to the Preview tab and change the color scheme view to Temperature.
Observe the color transitions relative to the geometry of the tower.

Actual results

The temperature transitions (indicated by the color change in the preview) shift slightly relative to the structural grooves. The temperature change misses the exact start of the new block by about one layer, meaning the surface of that layer is printed using the temperature of the block below it.

in this example there is no "balcony" for 250°C or 240°C

Expected results

The calibration script should ideally calculate the modifier heights dynamically based on the active layer height profile. The temperature shift should occur exactly at the flat start of the new block segment regardless of the user's selected layer height, ensuring accurate surface testing.

If that's too complicated I would say simply staring the new temperature always one layer later would also be acceptable .

Project file & Debug log uploads

Nozzle temperature test-bug report.zip

Checklist of files to include

Log file
Project file

Anything else?

No response

*Originally created by @TimetravelerDD on 2/14/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.1 ### Operating System (OS) Windows ### OS Version Windows 11 ### Additional system information _No response_ ### Printer Snapmaker U1 ### How to reproduce When using the built-in Temperature Tower from the Calibration menu, the automated script that changes the extruder temperature appears to be hardcoded for a 0.20mm layer height. If a user tries to generate and slice the temp tower using a different layer height profile (e.g., 0.16mm), the temperature changes do not align perfectly with the physical geometry of the blocks. The shift is not drastic enough to ruin the overall overhangs, but it misses the start of the new block by exactly one layer. This causes the surface of that specific boundary layer to print at the incorrect temperature, invalidating close inspections of surface quality for that height. **Steps to Reproduce** 1. Open OrcaSlicer and select a printer profile. 2. Select a 0.16mm (or any non-0.20mm) print profile in the Process tab. 3. Navigate to Calibration -> Temperature in the top menu bar. 4. Generate the standard Temperature Tower. 5. Click Slice plate. 6. Go to the Preview tab and change the color scheme view to Temperature. 7. Observe the color transitions relative to the geometry of the tower. ### Actual results The temperature transitions (indicated by the color change in the preview) shift slightly relative to the structural grooves. The temperature change misses the exact start of the new block by about one layer, meaning the surface of that layer is printed using the temperature of the block below it. <img width="1610" height="1250" alt="Image" src="https://github.com/user-attachments/assets/7d297d5e-aa6b-4ddd-92ca-3cd030465907" /> in this example there is no "balcony" for 250°C or 240°C ### Expected results The calibration script should ideally calculate the modifier heights dynamically based on the active layer height profile. The temperature shift should occur exactly at the flat start of the new block segment regardless of the user's selected layer height, ensuring accurate surface testing. If that's too complicated I would say simply staring the new temperature always one layer later would also be acceptable . ### Project file & Debug log uploads [Nozzle temperature test-bug report.zip](https://github.com/user-attachments/files/25314777/Nozzle.temperature.test-bug.report.zip) ### Checklist of files to include - [ ] Log file - [x] Project file ### Anything else? _No response_

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#778