SlicerX / Help improve SlicerX
How to report a slicing problem that others can reproduce
Help improve SlicerX with a small reproducible example: app version, printer settings, model, preview screenshots and expected behavior.
By SlicerX. The app is pre-alpha; these guides distinguish current tools from features still in development.
Describe the first surprising result
A useful report starts with a specific observation: a thin wall disappears, support is missing under one overhang, or a tool change happens where you did not expect it. “The slice is wrong” is a starting point, but the next person needs to know where to look.
Write what you expected, what actually happened and the shortest sequence of actions that shows the difference. If the problem is visible in Preview, give the layer number and the affected object. If it appears only in a physical print, include a photo as well as the preview.
Record the environment
Include the SlicerX version, operating system, printer model, nozzle size and material. Say whether you used the desktop app or the browser app. Copy the exact error text when there is one.
For slicing differences, record layer height, wall settings, infill, supports and material assignments. A screenshot of a single setting may miss another setting that changes the result, so attach a project or settings export when available and appropriate. If you are comparing another slicer, name its version too.
Reduce the model without losing the problem
A small example is easier to investigate than a crowded plate. Try removing unrelated objects or using a simple shape that produces the same behavior. Keep the original project, then work on a copy for the report.
Only attach files you have permission to share. If the original is a customer part or a restricted model, describe the geometry and try to reproduce it with your own simple example. Remove printer access codes, API keys and private network details from screenshots or logs before posting them publicly.
Use this report outline
- Summary: one sentence describing the problem.
- Environment: app version, desktop or browser, operating system, printer, nozzle and filament.
- Steps to reproduce: start from opening the model and list the exact actions.
- Expected result: the toolpaths or behavior you expected.
- Actual result: the layer, object, error or physical outcome you observed.
- Attachments: a shareable minimal model/project, relevant settings, preview screenshots and optional print photo.
- Frequency: every time, intermittent, or only with a particular setting.
Choose the right place and follow up
If you are not sure whether you found a bug, ask the SlicerX community on Discord. For a repeatable problem, search the GitHub issues first and add your example to an existing issue when it is the same problem. Otherwise, open a new issue with the outline above.
If someone provides a fix or asks for a smaller example, a follow-up test is valuable. Report the version you tried and whether the original steps now work. A clear “fixed in this version” is as useful as the initial report, and it gives other people a result they can trust.