Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printer companies "custom software" #20055

Open
Koselife opened this issue Dec 20, 2024 · 6 comments
Open

Printer companies "custom software" #20055

Koselife opened this issue Dec 20, 2024 · 6 comments
Labels
Type: Discussion Open-ended discussion (compared to specific question).

Comments

@Koselife
Copy link

Cura Version

1.4.11

Operating System

Win 11

Printer

Custom printer Mingda 1000 pro

Name abnormal settings

nothing slices

Describe model location

center

Describe your model

No successful slices have been made

Add your .zip here ⬇️

The company i purchased the printer from has their own version of Cura which i very much dislike because the 5.8.1 version slices everything all of the time. all of my prints don't slice.

@Koselife Koselife added Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Dec 20, 2024
@GregValiant GregValiant added the Status: Needs Info Needs more information before action can be taken. label Dec 20, 2024
@GregValiant
Copy link
Collaborator

I'm not sure what to make of this.
Are you using UltiMaker Cura? It looks like the Mingda Company slicer is based on Orca.

@Koselife
Copy link
Author

Koselife commented Dec 20, 2024 via email

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Dec 20, 2024
@GregValiant
Copy link
Collaborator

You cannot post any files to Github by email. They must be posted directly to the site.

You haven't indicated any sort of bug in UltiMaker Cura. I'm going to close this.

@GregValiant GregValiant added Type: Discussion Open-ended discussion (compared to specific question). and removed Type: Bug The code does not produce the intended behavior. Status: Triage This ticket requires input from someone of the Cura team Slicing Error 💥 A crash is caused by a model or a user interaction. This needs a differnt troubleshooting approach labels Dec 20, 2024
@Koselife
Copy link
Author

Koselife commented Dec 20, 2024 via email

@GregValiant
Copy link
Collaborator

When you filled out the form it specifically asked you to post a zipped "project file" and the cura.log file. Photos don't help. We need to know the model you are attempting to slice, your printer, and how Cura was set up. Those are in the project file.
The log file should show information if the CuraEngine (the actual slicing app) crashed in the background and caused the slice to fail.
The total information I gleaned from the initial report can boil down to "nothing slices" AND there is no UltiMaker Cura version 1.4.11 and you mentioned Mingda Slicer so I had no real idea what slicer you are using.
There certainly isn't enough information to base an investigation on. We need something to work with here and without some leads nothing can be done.
I'll reopen this.
There is a new command in UM Cura 5.9.0 "Help | Export Package for Technical Support". Use that command, open the folder where the 3mf file resides, zip the file, and post the zip folder here directly to the site. Github does not allow posts via email.
The instructions are on the page you originally filled out for the report.
You can copy and paste any image here or click on the "Paste, drop, or click to add files" link below.
image

@GregValiant GregValiant reopened this Dec 20, 2024
@Koselife
Copy link
Author

Koselife commented Dec 20, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Discussion Open-ended discussion (compared to specific question).
Projects
None yet
Development

No branches or pull requests

2 participants