PrusaSlicer trying to validate Start G-Code comments /// G-Code substitution
In the printer custom G-Code fields if you have anything within brackets like a placeholder/variable, PS will try and validate it, even if it's as part of a comment.
Is there any way around this?
The reason I'm looking at this is that in Bambu Slicer, they've added a load of additional variables that can be read for the current print, like volumetric speed of certain features.
I was looking to see if you could do something similar (although in a limited manner as it wouldn't take into account any max volumetric speed settings of the filament) by adding a volumetric speed into the print settings as a G-code substitution of a custom variable.
Obviously in the future it would be lovely to see more print variables available, but for now if there's any way to fudge something in, that would be great too.