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

Seam-sphere seams seem not saved with project #3153

Closed
jhlchu opened this issue Aug 30, 2022 · 6 comments
Closed

Seam-sphere seams seem not saved with project #3153

jhlchu opened this issue Aug 30, 2022 · 6 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@jhlchu
Copy link

jhlchu commented Aug 30, 2022

What happened?

Seam positions added via seam-sphere are not loaded when project is re-opened. Seam positions from seam-sphere only apply in same session seam-sphere is added. Re-opening same project shows seam-sphere object still exists but seams revert back to what is specified in "Print Settings" instead. Seam-sphere seams seemingly seem not saved.

Project file & How to reproduce

  1. Create a project and add an *.stl.
  2. Right-click *.stl and select "Add seam position" via context menu.
  3. Place seam-sphere to where seams are desired. View sliced gcode preview to confirm.
  4. Save project and close superslicer.
  5. Re-open superslicer and open project.
  6. Slice.
  7. Seams are now ignoring seam-sphere location and default to whatever is set in "Print Settings"

Version

2.5.59 Nightly

Operating system

Win 10 Enterprise

Printer model

No response

@supermerill
Copy link
Owner

can't reproduce.
If you have a project that has an ignored seam-sphere on load+slice, give it to me.

@jhlchu
Copy link
Author

jhlchu commented Aug 31, 2022

Project File

Seam.zip

Seam sphere position

Correct seam in same session

New session, same file

@supermerill
Copy link
Owner

I can't extract your zip file, maybe there was an upload error?

@jhlchu
Copy link
Author

jhlchu commented Sep 1, 2022

This one is just the extension changed *.3mf to *.zip instead of compressing the *.3mf.

Project File

90Deg.zip

@supermerill supermerill added bug Something isn't working as intended and removed could not reproduce labels Sep 6, 2022
@supermerill
Copy link
Owner

funny. I found this bug last February, and I fixed it. Now the root cause (loading modifier position) seems "fixed" and I need to remove the old fix.

supermerill added a commit that referenced this issue Sep 6, 2022
@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Sep 7, 2022
supermerill added a commit that referenced this issue Sep 12, 2022
supermerill added a commit that referenced this issue Sep 16, 2022
@VanessaE
Copy link

VanessaE commented Jul 19, 2023

This occurs in the Ubuntu 18.04 Appimage build also, v2.5.59.0.... in fact, it happens with 2.5.59.2 as well. Exactly as described by the parent.

I've attached a project file demonstrating it:

Pneumatic Actuator (21828, plunger, with support structure).3mf.zip

In this project, a correctly-placed seam would be dead center at the back of the support tower structure as well as the back of the round shaft of the plunger object, and that's more or less what I get if I place a seam object appropriately and slice (it's not entirely correct but it's close enough).

However, if I save, restart, reload, and slice again, the plunger object is still correct, but the support structure has the seam in the wrong place. I wonder if it's because the support structure is not an independent object, but instead was loaded onto the plunger object as a "part"?

Note that I even have the global seam position set to "Rear" in this project, so there are two things telling the slicer to put the seam on the back side.

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

3 participants