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

Mirror Project File Bug #8451

Closed
zerspaner-gerd opened this issue Sep 26, 2020 · 8 comments
Closed

Mirror Project File Bug #8451

zerspaner-gerd opened this issue Sep 26, 2020 · 8 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

@zerspaner-gerd
Copy link

zerspaner-gerd commented Sep 26, 2020

Application version
Cura 4.7.1
(Tested with 4.6.1 and smartavionics Master Version same behavior)

Platform
Windows 10

Printer
no matter

Reproduction steps

  1. Loading stl
  2. Mirror
  3. Save as a project file
  4. Load project file

Screenshot(s)

STL geladen
STL loaded
Everything OK

STL gespiegelt
STL mirrored
Everything OK

projekt file neu geladen
After opening the project file
Broken

Actual results
STL is now defective, no longer printable

Expected results
Should be loaded exactly as saved

Additional information
I have tried it with different STL, all behave the same

@zerspaner-gerd zerspaner-gerd added the Type: Bug The code does not produce the intended behavior. label Sep 26, 2020
@nallath
Copy link
Member

nallath commented Sep 28, 2020

Why would this make the STL not loadable anymore? It just flipped the normals, which is only used for rendering.

As far as I can see this is just a visualization issue. Did you try and print it?

@zerspaner-gerd
Copy link
Author

Since when have Cura upside down normals not bothered?

As far as I can see this is just a visualization issue. Did you try and print it?

I meant that with me no infill was printed more, unfortunately I have overridden the original project file.
Now I wanted to recreate it and could not reproduce it, so only wrong areas red but is printed correctly

@Ghostkeeper
Copy link
Collaborator

Why would this make the STL not loadable anymore? It just flipped the normals, which is only used for rendering.

Indeed the normals should not affect the print, but they do, through the winding order of the triangles. It's a known issue for us (CURA-6928).

I'm not able to reproduce this issue though. This is a recording of me executing your reproduction steps: http://dulek.net/work/mirror_reload_project.webm
Maybe it still depends on the model? What model are you using?

@zerspaner-gerd
Copy link
Author

Do you have a MAC?

Maybe just a Windows problem?

Here is a link in it is an STL, two project files and a video
https://www.dropbox.com/sh/tj988x8n0kzdmrs/AAA3qiYIm-NbvyCR0dkhW05Ya?dl=0

But for me it is with every STL!
However, it is currently being sliced correctly, I don't know what led to it that no infill was generated for me.

@Ghostkeeper
Copy link
Collaborator

I don't have a Mac. This was tested on Linux.

Thanks to your video I can now also reproduce the issue. The problem with my previous test was that it didn't display the red overhang areas since the surface was too steep for it to be classified as overhang. And by coincidence the stitching happened to work out well so that the model did get properly filled.

@Vandrasc
Copy link
Contributor

Vandrasc commented Oct 7, 2020

Devs see internal ticket CURA-7761 for our own reference.

@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 20, 2024
@GregValiant
Copy link
Collaborator

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

Copy link
Contributor

github-actions bot commented Dec 8, 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 Dec 8, 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. 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

5 participants