Error code 3 on print to 3d

[brooked3d]

What is the error code 3? I have been getting the same error code on all my projects and I don’t know what it is or what settings to change to correct it. Does anyone know what the error code is?

[p3d-dev]

Sorry to hear, that you encounter a problem with PrintTo3D. In order to gives us some context, we would appreciate your support. Could you please provide a screenshot and describe, when exactly this error code pops up ?

[brooked3d]

It’s been popping up every time I try to slice with multiple projects Sent from Yahoo Mail for iPhone On Sunday, April 21, 2024, 9:46 AM, p3d-dev ***@***.***> wrote: Sorry to hear, that you encounter a problem with PrintTo3D. In order to gives us some context, we would appreciate your support. Could you please provide a screenshot and describe, when exactly this error code pops up ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[brooked3d]

[p3d-dev]

Thanks a lot. Now it is clear and we can check for the root cause.

[brooked3d]

Has the issue been resolved?

[brooked3d]

Has the issue been resolved ? Or can you tell me what i need to do to get it to work?

[p3d-dev]

Unfortunately, the issue has not been resolved. From our investigation, the slicer process has been terminated and this has happened without further information about possible root cause.

Our best guess is, that the slicer process termination may be due to some printer/process configuration settings, which unexpectedly yields this exception.

Remedy: Start from scratch with new clean printer/process profiles. Default profiles can be created via Sidebar by long press on the "+" symbol and then select "Standard" in the popup menu.

In case this is fixing it, please send us those settings causing this issue - Using Share button/Save File. This should allow us to reproduce the issue on our devices, then narrow down on the problematic settings and inform you about needed changes in your user configuration and prevent it from happening again (or better error reporting) on app side for the next release.