Priority 1
OrcaSlicer
Attack aggressive tuning and Klipper/Bambu/Voron workflows with independent verification.
- Review high-speed jobs against real profiles.
- Compare calibration/profile variants.
- Gate Moonraker upload after slicing.
Appearance
Competitive wedge
Slicer attack map
Dry should not attack slicers by claiming better slicing first. The stronger wedge is after slicing: review, verify, trace, compare, rewrite and gate the G-code before it reaches the machine.
Strategic Take
Dry's sharper positioning:
Slicer output
->Dry review / verify / trace / compare / rewrite
->Accept, warn, reject, upload or archive
The message is: your slicer can generate G-code, but Dry tells you whether that G-code is policy-safe, explainable, reproducible and ready for the machine.
Attack Priority
| Slicer | Target users | Dry attack angle | Proof artifact | Priority |
|---|---|---|---|---|
| OrcaSlicer | Klipper/Bambu/Voron power users | Calibration and speed still need independent verification before upload. | Orca corpus -> Dry review/trace/compare + Moonraker gate | 1 |
| PrusaSlicer | trusted desktop slicer users, farms | Even trusted profiles need release gates and drift detection. | Compare PrusaSlicer profile versions and risk metrics | 2 |
| UltiMaker Cura | broad hobby/pro/prosumer base | Large settings surface creates policy drift. | Cura post-processing/plugin proof that runs Dry after slice | 3 |
| SuperSlicer | advanced tuning users | Advanced knobs need structured verification. | Flow, speed, first-layer and retraction findings | 4 |
| Bambu Studio | Bambu ecosystem, high-speed FFF users | Fast closed workflows still benefit from independent local audit. | Bambu vs Orca comparison pack | 5 |
| Simplify3D | paid slicer users who value control | Paid slicing control is not the same as auditable output. | Dry report pack for Simplify3D output | 6 |
| ideaMaker | Raise3D/prosumer users, print farms | Profile-rich slicers still need fleet policy gates. | ideaMaker/Raise3D batch review report | 7 |
| Kiri:Moto | browser slicer/CAM users | Dry wasm can become browser-side verification. | Browser verification demo | 8 |
| Lychee Slicer | resin + filament users | FFF mode can be reviewed; resin is later. | FFF export only | 9 |
| CHITUBOX | resin users | Resin process model is later. | Watch-list | 10 |
| PreForm | Formlabs users | Closed resin workflow is not first-wave. | Later partner research | 11 |
| VoxelDance Additive | industrial additive users | High value but outside FFF first wedge. | Later industrial research | 12 |
First-Wave Plans
Priority 2
PrusaSlicer
Do not attack trust directly. Sell Dry as the production release gate.
- Detect profile-version drift.
- Compare output after printer/material preset changes.
- Create structured reports for farms and labs.
Priority 3
UltiMaker Cura
Turn the broad settings surface into the reason teams need enforceable checks.
- Build a post-processing hook proof.
- Run Dry after slicing.
- Export JSON reports for support or production review.
Priority 4
SuperSlicer
Advanced tuning users can understand and value strict verification.
- Compare conservative vs aggressive tuned jobs.
- Highlight flow, first-layer and retraction policy violations.
- Use the output as evidence for tuning decisions.
Priority 5
Bambu Studio
Add independent local audit without changing the fast Bambu workflow.
- Review exported G-code.
- Compare Bambu Studio and OrcaSlicer variants.
- Package as a local audit/report story.
Priority 6
Simplify3D
Attack the gap between paid control and auditable verification.
- Run Dry reports on premium slicer output.
- Compare to open slicer output.
- Sell evidence, not another slicing UI.
Attack Vectors
Post-slicer CLI gate
Best targets: OrcaSlicer, PrusaSlicer, Cura, SuperSlicer, Bambu Studio and Simplify3D.
bash
dry review-gcode part.gcode --profile printer-material.json --json > dry-report.json
dry trace-gcode part.gcode --window-s 5 > dry-trace.json
dry compare baseline.gcode candidate.gcode --profile printer-material.jsonUpload gate
Best targets: OrcaSlicer + Klipper/Moonraker, PrusaSlicer + OctoPrint/Moonraker, Cura + OctoPrint/Moonraker.
bash
dry upload part.gcode --moonraker http://printer.local --profile printer-material.jsonCompare/regression workflow
Best targets:
- PrusaSlicer profile updates;
- OrcaSlicer calibration variants;
- Bambu Studio vs OrcaSlicer;
- Simplify3D vs open slicer output.
Messaging Matrix
| Target | Avoid saying | Say instead |
|---|---|---|
| OrcaSlicer | Dry replaces Orca. | Dry verifies aggressive Orca output before upload. |
| PrusaSlicer | Prusa profiles are unsafe. | Dry catches profile drift and creates production reports. |
| Cura | Cura has too many settings. | Dry turns Cura output into enforceable checks. |
| SuperSlicer | Advanced users make mistakes. | Dry keeps advanced tuning inside known constraints. |
| Bambu Studio | Closed ecosystems are bad. | Dry adds independent local audit for high-speed output. |
| Simplify3D | Paid slicers are obsolete. | Paid control still benefits from auditable verification. |
Proof Corpus
Build a slicer corpus with:
- 5 OrcaSlicer jobs: baseline, speed-tuned, flow-tuned, first-layer-tuned, failed/risky known case.
- 5 PrusaSlicer jobs: stable profile, modified profile, version drift, different material, known good baseline.
- 5 Cura jobs: stock profile, custom profile, high-speed profile, support-heavy job, first-layer-sensitive job.
- 3 SuperSlicer jobs: conservative, aggressive, tuned retraction.
- 3 Bambu Studio jobs: default, speed profile, Orca comparison.
For each job:
- input slicer and version;
- printer/material profile;
- raw G-code;
- Dry review JSON;
- Dry trace JSON;
- optional compare report;
- short human interpretation.
Source Notes
- PrusaSlicer
- UltiMaker Cura
- OrcaSlicer
- Bambu Studio
- SuperSlicer
- Simplify3D
- ideaMaker
- Kiri:Moto
- Lychee Slicer
- CHITUBOX
- PreForm
- VoxelDance Additive
The full implementation map is maintained with the private product source.