First layer temperature set to other layer temperature at beginning of print.

[Merlin246]

Description of the bug

Problem: the "other layer" temperature is being used for the first layer instead of first_layer_temperature.

Cause: extra gcode after custom start gcode causing the temperature to be set to "other layer" temperature instead of first_layer_temperature. See attached "GCODE.pdf", the highlighted line is causing the issue.

Misc: Running RepRap Firmware 3.4.3 on Duet 2 Wifi with Duex Expansion Board.

Project file & How to reproduce

Issue.zip
GCODE.pdf

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

2.5.0+win64

Operating system

Windows 11

Printer model

E3D Toolchanger w Revo-Volcano-N/A-N/A

[DragonFinlay]

I see the issue. The problematic G10 g-code is not part of the Slicer custom g-codes, but rather emitted by the printer profile (toolchanger), and it seems to think it's not in the first layer anymore.
It's difficult for me to reproduce without having an E3D Toolchanger though. I'll see if there's anything we can do.

[Merlin246]

I see the issue. The problematic G10 g-code is not part of the Slicer custom g-codes, but rather emitted by the printer profile (toolchanger), and it seems to think it's not in the first layer anymore. It's difficult for me to reproduce without having an E3D Toolchanger though. I'll see if there's anything we can do.

Let me know if there is anything I can do to help (sharing the config, testing, etc). Would love to help get to the bottom of this!

Would it be easier to use an alternative to G10 in my custom startcode? Something like the M568 gcode (M104 doesn't allow separate active & standby temperatures).

[kubispe1]

Hi, in this case, PS Ooze prevention caused this issue. So the solution is to disable Ooze prevention.
After that there is a G-Code preview bug, that was already fixed in 2.6.0. G-Code itself should be fine.
So, I see this:

[kubispe1]

I am closing this issue as solved with new alpha: 2.6.0-alpha2