Linux/K2 Pro+CFS: bed temp still wrong on stable 7.2.0 / community fork; #575 only in prerelease 7.2.1

[ricksouzaa]

Is there an existing issue for this problem?

• I have searched the existing issues

Related:

• Bed temperature mode uses first project filament instead of plate-used filament #575 — bed temperature mode uses first project filament instead of plate-used filament (closed as fixed in 7.2.1, but 7.2.1 is still a GitHub prerelease)
• Linux 7.2.0.5226: CRITICAL — preset UI still read-only after 3 releases (#552 #565) — fix or acknowledge #576 / Linux 7.1.0.4414: settings UI becomes read-only after clean install (filament/process/printer) #552 — Linux preset UI read-only (why many Linux users run the community AppImage)

CrealityPrint Version

• Official stable: v7.2.0 (still latest non-prerelease tag)
• Community Linux build in use: Arm4g3ddon v7.2.1.5226 — this is 7.2.0 + Linux UI/exit fixes, not Creality official 7.2.1.5476
• Official prerelease that claims the bed fix: v7.2.1.5476 (release notes item 17 → Bed temperature mode uses first project filament instead of plate-used filament #575)

Operating System (OS)

Linux (Ubuntu 24.04)

Printer

Creality K2 Pro + CFS

---

Problem summary

On stable 7.2.0 (and on the common Linux community fork based on 7.2.0), bed temperature for START_PRINT / first-layer bed still follows:

bed_temperature_mode = use_first_material

using the first filament in the project list, not the filament assigned to the object / the extruder actually used (T[n]).

This matches #575. Creality stated it is fixed in 7.2.1, but:

1. 7.2.1 is still marked prerelease on GitHub → users who only install stable releases remain affected.
2. The popular Linux fork tag v7.2.1.5226 is easy to confuse with official 7.2.1, but it does not include the Bed temperature mode uses first project filament instead of plate-used filament #575 fix (it is rebased Linux fixes on 7.2.0).

Extra case (print sequence: by object)

Even after patching machine_start_gcode so that:

BED_TEMP=[bed_temperature_initial_layer[initial_no_support_extruder]]

the first object can print with the correct PLA bed temp, but when starting the second object the slicer still emits something like:

M140 S110

when an unused high-temp filament (e.g. ABS/ASA with bed 110 °C) is still slot 1 in the project filament bar.

So please confirm whether the #575 fix in 7.2.1.5476 also scopes between-object M140 in print_sequence = by object, not only START_PRINT / BED_TEMP.

Steps to reproduce

1. Load CFS / project with ABS (or ASA) in filament slot 1 and PLA in another slot.
2. Assign the object(s) to the PLA slot.
3. Slice on stable 7.2.0 (or community 7.2.1.5226 based on 7.2.0).
4. Inspect G-code: START_PRINT ... BED_TEMP= and/or M140 use the ABS/ASA bed temperature.
5. Optional: enable Print sequence → By object with two objects on PLA; first object OK (if start G-code forced), second object bed jumps to the high-temp filament (e.g. 110 °C).

Expected

Bed temperature (start + by-object transitions) comes from the filament actually used by the plate/object, not from an unused first global slot.

Actual

bed_temperature_mode = use_first_material takes the first project filament, including unused CFS slots.

Ask

1. Please promote 7.2.1 (or a hotfix) to a stable release so Linux/stable-only users get Bed temperature mode uses first project filament instead of plate-used filament #575 without installing a prerelease.
2. Please confirm the fix covers by-object M140, not only start G-code.
3. CC community Linux maintainer: once 7.2.1 is stable (or for testing), a rebase of https://github.com/Arm4g3ddon/CrealityPrint onto official 7.2.1.5476 would help Linux users who still need the fork for packaging/UI history — that fork currently has Issues disabled, so filing there is not possible.

Thanks.