Description

Eleven Sovol process profiles carry settings that OrcaSlicer does not define. The loader ignores them, so they never affect a slice:

• wall_loop_direction and initial_solid_infill_acceleration in the three SV08 MAX processes (0.4, 0.6 and 0.8 nozzle).
• minimum_sparse_infill_threshold in eight SV06 ACE and SV06 Plus ACE processes.

Root cause: None of the three names exists in src/. PrintConfigDef::handle_legacy clears a key it does not know, and ConfigBase::set_deserialize_nothrow then skips it without an error. The profile tool only flags a fixed list of retired keys, and these three are not on it. In all eight SV06 files the option that applies, minimum_sparse_infill_area, is already set to 10. The removed key said 0, so the effective value stays 10.

Fix: I removed the 14 lines and raised version in Sovol.json from 02.04.00.08 to 02.04.00.09. No other key, value or key order changes.

I did not rename wall_loop_direction: clockwise to wall_direction: cw. The profile never applied it, and the default is counter clockwise, so a rename would change printed output. If clockwise walls are wanted on the SV08 MAX, that belongs in a separate change with print results.

Screenshots/Recordings/Graphs

Not applicable. No UI change.

Tests

• grep -rn -E "wall_loop_direction|initial_solid_infill_acceleration|minimum_sparse_infill_threshold" src/ finds nothing.
• python3 scripts/orca_profile_tool.py check reports 71 vendors, 0 files with errors and 0 files with warnings, both on main and on this branch.
• For each of the 12 changed files I parsed the JSON at upstream/main and at this branch and compared the key/value pairs in order. The only differences are the 14 removed keys, plus version in Sovol.json. The remaining keys keep their values and their order.
• python3 scripts/orca_profile_tool.py version-check --base upstream/main: Sovol: 02.04.00.08 -> 02.04.00.09, 12 files changed.
• python3 -m unittest discover -s scripts/tests -t scripts: 381 tests, OK (1 skipped).
• scripts/check_profile.sh: all checks passed (profile_tool, version_bump, legacy_compat, validate_system, validate_slice, validate_filament_subtypes, validate_custom), including the validator binaries v2.4.0, v2.4.1 and v2.4.2.
• Not tested on a printer. Since the loader already discards these settings, I expect identical G-code, but I have not compared G-code before and after.

How to Download Pull Requests Artifacts for Testing