Custom Start GCode not adding values to S

Hello, I was trying to print after taking a break for a few weeks and when I updated to the latests version of Cura 4.6.2 I could not use custom Codes anymore I'll share a piece of code so I can explain better. M104 S{100} M140 S{material_bed_temperature} M190 S{material_bed_temperature} G29 G1 Z

Interesting discovery. My Gcode flavor swutched from marlin to Marlin Volumetric and I began to have 100% print failures and exstruder clicking(even after multi cleanings) i just wanted to share this if

Using Slicers and PRINT_START macros

Convert Prusa slicer start g code to ideMaker - Official Raise3D Community

Fully Commented Bambu Lab Start Gcode (feat. ChatGPT) - X1C by Shoe, Download free STL model

Extra gcode in the files from Cura. - UltiMaker Cura - UltiMaker Community of 3D Printing Experts

Custom Start G-Code for filament does not apply correctly · Issue #2549 · supermerill/SuperSlicer · GitHub

Changing default gcode output - Page 2 – PrusaSlicer – Prusa3D Forum

Klipper: Start G-code – All You Need to Know

4.7] Can not save custom start gcode if it contains an equal sign · Issue #8230 · Ultimaker/Cura · GitHub

Running without limit switches – ToyBuilder Labs

Custom G-Code Variables - MatterControl Manual

Printer custom start G-code makes part slice under bed – PrusaSlicer – Prusa3D Forum