In prusa and superslicer this does not seems to be the case, my feeling is that orca parses the resulting gcode assuming some initial temperatures and defaults to bad values when TN commands are present.
It seems like only first and last layers are affected thus initial values might be to incriminate. When adding some M140 commands manually in the printer start g-code section I'm able to trigger correct temperature detection in my example like follows:
OrcaSlicer Version
1.9.0
OS version
EndeavourOS
Additional system information
Printer
Voron Trident 250
How to reproduce
Actual results
With purge tower activated Without purge tower activated
Expected results
Both colors should have their correct temperatures displayed. (In my case 220°C)
Project file & Debug log uploads
first_last_layer_temp.zip
Thoughts
In prusa and superslicer this does not seems to be the case, my feeling is that orca parses the resulting gcode assuming some initial temperatures and defaults to bad values when TN commands are present.
It seems like only first and last layers are affected thus initial values might be to incriminate. When adding some M140 commands manually in the printer start g-code section I'm able to trigger correct temperature detection in my example like follows:
Notes
Sliced g-code prints without correct temperatures, this only seems to be a viewer issue.
Checklist of files to include