Parse flush multiplier and adjust flush matrix accordingly to match Orca and Bambu requested purge volumes #524
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I was experimenting with Blobifier I noticed that the purge matrix was not changing as the flush multiplier was increased or decreased in Orca slicer as I was trying to validate this Orca slicer PR I've raised here: SoftFever/OrcaSlicer#7508
For example:
Multiplier of 1.2
Gcode file:
Multiplier of 0.5
Gcode file:
This results in an incorrect purge matrix being sent to the blobifier for use when purging that does not match the intended action from the user in the UI. Instead the purge matrix is always as if 1.0 multiplier was set in the UI.
This happens because both Orca and Bambu generate a base purge matrix and a separate multiplier and they output both to the gcode for use by Happy Hare etc. To calculate the effective purge volume, these two values need to be multiplied so they match the user intent.
This PR proposes to parse the flush multiplier and apply it to the purge matrix before use in the placeholder variables.
Results:
For example, now with a 0.5 multiplier the purge volumes correspond to what the UI displays