Adding temperature to gcode preview colour scheme

[Me_Tommie 0]

Just a small feature that most slicer do offer. when I installed the auto tower extension there was nothing i had to do to make a temp tower just select the model. in the gcode preview there is no colour scheme for temperature. no bid deal just opened the gcode file in notpad and ctrl + f to find m104 command to make sure it was actally changing temps. be nice to have this option in the colour scheme.

[MariMakes 204]

Hey @Me_Tommie,

 

Thanks for your report 👍

Interesting feature request! I don't know why this is currently not an option.
I can see that it has been deferred before https://github.com/Ultimaker/Cura/issues/11432

I'll have to ask the Cura team what they think. 🤔

[MariMakes 204]

Hey @Me_Tommie,

 

I brought up your suggestion to the team and it's trickier than expected. 
We get this question most often for temperature towers, but there we would not able to display the temperature since it's added in a post processing script. Our researchers see some value in adding this information, but I don't believe will work on this anytime soon.

 

[UMFrankR 0]

hi,

 

after 2 years any progress on this topic?

 

thanx

br

Frank

[ahoeben 1,981]

Unlikely, since the underlying problem has not changed (much*). Let me try to clarify.

 

In preview mode, Cura does not actually parse the gcode, but instead it displays "layer data" that is created by the slicer in tandem with the gcode data. This speeds up displaying the preview immensely. Postprocessing scripts such as those inserting temperature commands for temp towers act on the gcode well after it has been generated by the slicer; actually only when the gcode file is being saved to disc or printed. It does not touch the "layer data", so any change made by any postprocessing change will not show in the preview.

 

*: Ok, there has been at least some progress, but none that is ready to be used. The slicer, CuraEngine, now supports plugins that act on the gcode during the slicing process. So it should at least be possible to insert the temperature commands before the preview is shown (instead of when the gcode is saved or printed). However writing a plugin that does this is a whole lot more complicated than writing a postprocessing script, so there are hardly any CuraEngine plugins. And I'm still not sure if these plugins can affect the "layer data" that is shown in the preview.

[UMFrankR 0]

thanx @ahoeben for clearification. i understand that probably simple things can solved only with hudge efforts in coding... so thank you for all developers working an that great product! your doing a great job!