Slicer engine crashed without creating a sliced file

If you see "[slicer engine] crashed while slicing," the selected engine stopped without creating a sliced file or returning a useful error message. SimplyPrint therefore cannot show the exact cause.

This guide explains what happened and which troubleshooting steps are worth trying. For help with other slicing problems, start with the Cloud Slicer troubleshooting overview.

Table of contents

• What this message means
• How SimplyPrint and the slicer engine work together
• Try official profiles
• Remove unused filaments
• Test the setup in the desktop slicer
• Reduce the setup
• Try another engine or version
• Get help

What this message means

This error means the slicer engine did not produce a usable output file. It also did not return an error message that SimplyPrint could explain.

SimplyPrint cannot reconstruct a reason that the engine did not provide. The model, profile, or settings may have triggered the crash, but the message alone does not tell us which one caused it.

How SimplyPrint and the slicer engine work together

SimplyPrint does not use a simplified replacement for OrcaSlicer, PrusaSlicer, BambuStudio, or the other available engines. The Cloud Slicer runs the actual slicer engine in the cloud.

When you start a slice:

1. SimplyPrint prepares your model, machine profile, print profile, filament profiles, and changed settings.
2. The slicing job is sent to the SimplyPrint cloud slicing service.
3. The selected slicer engine and version process the job.
4. The engine should create a sliced file.
5. SimplyPrint receives the file and prepares the preview and output actions.

For this error, step four did not complete. The engine created no file and returned no usable explanation.

The Cloud Slicer feature overview explains more about the engines, profiles, and normal slicing workflow.

Try official profiles

Custom machine, print, and filament profiles can contain settings that the selected engine or version does not accept.

Switch any custom profiles to official profiles and slice again. Official profiles are normally grouped under System presets in the profile selectors.

If the slice succeeds, restore your custom profiles one at a time. This can help identify which profile or group of settings caused the problem.

If you are unsure which settings a profile controls, read How to change slicer settings before slicing.

Remove unused filaments

Extra filament entries can still become part of the slicing setup, even when the model does not use them.

If you are slicing a single-color model but have several filaments configured:

1. Remove filaments that are not assigned to the model.
2. Keep only the filament or filaments required for the print.
3. Check that every remaining filament has a compatible filament profile.
4. Slice again.

This is especially worth trying when the problem started after adding, importing, or changing filament profiles.

Test the setup in the desktop slicer

Open the desktop version of the same slicer engine and try a similar setup.

Use the same model, printer, nozzle size, and important setting changes. Select the same engine version when it is available, or the closest version you can install.

The desktop slicer may show an error dialog or log message that its cloud process did not return. If it shows a specific error, use that information when changing the model or profiles.

If the desktop slicer also crashes, the problem is probably connected to the model, profiles, settings, or slicer engine. If the desktop slicer succeeds, include that detail when asking for help.

Reduce the setup

Start with the smallest possible test:

1. Open a fresh slicer project.
2. Add one model.
3. Configure one filament.
4. Use official machine, print, and filament profiles.
5. Slice without extra setting changes.

If the test works, add the original filaments, profiles, and settings back one at a time. Slice after each change. The first change that brings the crash back is the best clue to the cause.

You can also try a simple test model with the original profiles. This helps separate a model problem from a profile or settings problem.

Try another engine or version

A different stable version of the same slicer engine may handle the model or profile differently. Another compatible engine may also complete the slice.

Profiles belong to a slicer engine. Check the selected machine, print, and filament profiles again after switching engines or versions.

Read How to choose a slicer engine and version before changing engines if you want to preserve a specific profile setup.

Get help

If the crash continues, include:

• The Task ID shown in the error
• The slicer engine and version
• The selected printer or machine profile
• The print and filament profiles
• How many filaments were configured
• Whether official profiles made any difference
• Whether the same setup worked in the desktop slicer
• What changed before the problem started

The Task ID helps SimplyPrint support find the failed cloud slicing attempt. You do not need to upload the model publicly unless someone from support asks for it.

Paying accounts can use the support option shown in the slicer. For community help, join the SimplyPrint Discord.

Related articles

• The Cloud Slicer feature: slice prints directly in SimplyPrint
• Cloud Slicer troubleshooting overview
• Slice failed: what the error means and what to send support
• How to choose a slicer engine and version
• How to change slicer settings before slicing

Updated on: 08/08/2026