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

Print profile is "Not supported", cant create custom profiles or edit new ones #9079

Open
hitech95 opened this issue Jan 6, 2021 · 9 comments
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.

Comments

@hitech95
Copy link

hitech95 commented Jan 6, 2021

Application version
4.8.0

Platform
Windows 10 2004
i7-4790k, GTX1060

Printer
Ender 3 Pro

Reproduction steps

  1. Install Cura
  2. Select the printer in the Setup wizard
  3. Create a new Material or use "PLA+" from eSUN. This happends on a lot non default Material.
  4. Try to create a print profile.

Screenshot(s)
immagine
immagine

Actual results
Print Profile settings are grayed out, cannot store a custom profile.
Default profiles cannot be selected.

Expected results
Beeing able to create a custom priofile is the default one are not available.

Project file
Not needed, this happend even without any file open

Log file
cura.log

Additional information
Other people are facing the same issue.
https://community.ultimaker.com/topic/33336-non-generic-material-selection-causes-profiles-to-show-not-supported/

@hitech95 hitech95 added the Type: Bug The code does not produce the intended behavior. label Jan 6, 2021
@MarkMan0

This comment has been minimized.

@fvrmr
Copy link
Contributor

fvrmr commented Jan 7, 2021

Did you change some print settings (like layer height) before you tried to create a profile?
Because after this you can create a profile even though it is not supported.

@MarkMan0

This comment has been minimized.

@Ghostkeeper

This comment has been minimized.

@Zer025
Copy link

Zer025 commented Dec 18, 2021

I have the same problem: when creating a new material, if Material Type is PLA+ (or Nylon, PC, PVA and many others), Cura gives error "Not Supported". To workaround this problem I just used PLA instead of PLA+
I have Cura 4.12.0

@Ghostkeeper
Copy link
Collaborator

For clarity, the problem reported here is NOT that the print profile is "Not Supported". That part is correct and expected. The problem is that the user is not able to then create custom profiles.

We haven't been able to reproduce that issue so far. I hope we can get some clarity on how to reproduce that.

@hitech95
Copy link
Author

For clarity, the problem reported here is NOT that the print profile is "Not Supported". That part is correct and expected. The problem is that the user is not able to then create custom profiles.

We haven't been able to reproduce that issue so far. I hope we can get some clarity on how to reproduce that.

Unfortunalty I'm not able to replicate the issue. I must have re installed cura in meanwhile.

What is that ""Not Supported" means!?

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Dec 29, 2021

Basically, it means that Cura has no profiles for the combination(s) printer+nozzle+material-type you're using. Instead it will use the default for that combination. It's probably not well optimised.

A related issue is #8229, which started out similar to this one but is currently about the unclarity of making profiles depend on the material type.

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 19, 2024
@GregValiant
Copy link
Collaborator

Is this still an issue in current Cura versions (5.8.0 and up)? Can this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

6 participants