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

Reduced Print Volume In 5.7.0 from 5.6.0 - Ultimaker S3 #18935

Closed
Kvan-VTC opened this issue Apr 22, 2024 · 6 comments
Closed

Reduced Print Volume In 5.7.0 from 5.6.0 - Ultimaker S3 #18935

Kvan-VTC opened this issue Apr 22, 2024 · 6 comments
Labels
Status: Needs Info Needs more information before action can be taken. Type: Bug The code does not produce the intended behavior.

Comments

@Kvan-VTC
Copy link

Cura Version

5.7.0

Operating System

Windows 11

Printer

Ultimaker S3

Reproduction steps

Printing a model (Ultimaker Project File) close to volume limits works fine in 5.6.0. Same project in 5.7.0 (clearly within limit area) fails notification that it exceeds volume limits.

Actual results

5.7.0 Failed Volume Limits (Sidenote- increase in print time from 5.6.0 on same file)

Expected results

Successful print

Add your .zip and screenshots here ⬇️

5.6.0 Screenshot 2024-04-22 054641.zip

@Kvan-VTC Kvan-VTC added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Apr 22, 2024
@GregValiant
Copy link
Collaborator

Thanks for the report.
I opened the project file in 5.7.0 and didn't have a problem with it. I'm just looking at the preview though. I didn't try to send it anywhere.
Someone from the Cura team will take a look.

@HellAholic
Copy link
Contributor

@Kvan-VTC
Looking at the screenshots you included, your model is sliced with White tough PLA, but the project file you included has Generic TPU selected so none of the changes you have in the White Tough PLA is included in that project file.
The difference in print time is due to having support enabled/disabled or any changes you might have in your local profile.

image

I sliced your model in Cura 5.7.0 with Tough PLA and sent to a UMS3 (printer had black tough PLA loaded and the color doesn't affect the profile). Printer accepted the file and started printing.
image
I manually aborted the print after the start sequence finished and the printer was about to print the first layer. And no build volume warning. I do not see an issue relating to Cura here. You can contact the Support on the forums for more help.

@Kvan-VTC
Copy link
Author

Kvan-VTC commented Apr 22, 2024 via email

@Kvan-VTC
Copy link
Author

Kvan-VTC commented Apr 22, 2024 via email

@HellAholic
Copy link
Contributor

Cura has 500+ settings that get transferred when you open as project, if you do not want the settings you import as model. So why the difference? In every release more settings are available for users to tweak and fine tune their print, and those settings are not present in previous versions of Cura. So when you use an older version, some of the settings included in the project file are ignored.

Pointing back to the above, a project file has all the settings included for that model + nozzle + material + ... when you switch material, the changes are not transferred.
Easy example, try using Generic Tough PLA to slice a model at a certain layer height, then switch to Ultimaker Tough PLA and slice using the same layer height, why is there a difference of 3 hours in the print time? Printer profiles, material settings,... all contribute to how it is being handled.

If you still believe the issue is caused by Cura, please include the project with configuration that you sliced and sent to printer in 5.7.0; in addition try saving the slice file to disk and include that one as well.

@HellAholic HellAholic added Status: Needs Info Needs more information before action can be taken. and removed Status: Triage This ticket requires input from someone of the Cura team labels Apr 22, 2024
Copy link
Contributor

github-actions bot commented May 7, 2024

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot closed this as completed May 7, 2024
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. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

3 participants