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

[5.0 beta] Reloading a project after overwriting imports models incorrectly #12089

Closed
1 of 2 tasks
printingotb opened this issue May 4, 2022 · 5 comments
Closed
1 of 2 tasks
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.

Comments

@printingotb
Copy link

Application Version

5.0 beta

Platform

win10

Printer

custom fff

Reproduction steps

1 Load the project.
2 Save project and overwrite the same file.
3 Click reload

Actual results

All models are now duplicates of the same model when using the reload function.

With import or drag&drop, it works as intended.

Expected results

Should work as it does with import or drag&drop.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

Project:
1
Export and overwrite project, then hit "reload":
2
Result:
3
OpticoolerFunels.3mf.zip

@printingotb printingotb added the Type: Bug The code does not produce the intended behavior. label May 4, 2022
@GregValiant
Copy link
Collaborator

That's an odd one.
If Reload is hit right after saving then one or more models is replaced. If the build plate is cleared after the "reload" and the file is opened in a regular way then it opens correctly.

@printingotb
Copy link
Author

Hmm, If I first clear the buildplate and then hit Reload, no objects at all appear on the buildplate. It stays clear. Nothing in the object list either.

@fvrmr
Copy link
Contributor

fvrmr commented May 5, 2022

Hi @printingotb thank you for your report.
I can reproduce this so I will bring it up with the team. Keep you posted!

@fvrmr
Copy link
Contributor

fvrmr commented May 9, 2022

It seems like that this behaviour is not defined. We have ticket on our backlog for this, devs see CURA-7339

@nallath nallath added the Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. label Jun 15, 2022
@MariMakes
Copy link
Contributor

Quick update from our side 👋

I believe this issue is resolved with this pull request from the community: #16610 which will be available with the next release.

We recently released a Nightly version, which already includes this fix, so if you want to you can already try it out here #18080

To me, it doesn't seem like a bug in Ultimaker Cura, since we have a solution in place. Apologies for any inconvenience caused by our delayed response. I'll be closing this issue. I hope you understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

5 participants