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

fatal error: Access violation / object has zero size - if part is mirrored #5578

Closed
3 tasks done
sledwina opened this issue Jun 4, 2024 · 4 comments · Fixed by #5827
Closed
3 tasks done

fatal error: Access violation / object has zero size - if part is mirrored #5578

sledwina opened this issue Jun 4, 2024 · 4 comments · Fixed by #5827
Labels
bug Something isn't working

Comments

@sledwina
Copy link

sledwina commented Jun 4, 2024

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.1.0-beta

Operating System (OS)

Windows

OS Version

Windows 11 Pro

Additional system information

Prozessor AMD Ryzen 9 5950X 16-Core Processor 3.40 GHz
RAM 64,0 GB
AMD Radeon VII
Nvidia RTX 3070 Ti

Printer

Voron 2.4

How to reproduce

Import DDBDOuterNeckRight.stl - Clone the part - Mirror along x or y axis - hit "arrange" button -
gives error "object xxx.stl has zero size and can't be arranged"

zero size

Or:
Import DDBDOuterNeckRight.stl - Clone the part - Mirror around x or y axis - rotate part to fit on the build plate - hit "slice plate" - gives the error "fatal error: Access violation"

fatal error

Actual results

See above...

Expected results

Mirror a part and slice without errors.

Project file & Debug log uploads

DDBDOuterNeckRight.zip
debug_Tue_Jun_04_12_55_12_27044.log.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

No response

@sledwina sledwina added the bug Something isn't working label Jun 4, 2024
@GoldenGorilla123
Copy link

I've got a similar issue, but I can clone, mirror(by x axis) and arrange, but when I go to slice it I get 'access violation'
image

Mirroring by y-axis seems to work around the issue for me temporarily

2.1.0-beta
Windows 11

Intel i7-1185g7
16gb RAM
Integrated Graphics

Voron 2.4 300mm

Project file.zip
debug_Fri_Jun_07_09_03_38_7692.log.zip

@daijoubu
Copy link

Same issue here. Selecting "Fix Model" before arranging seems to solve the issue with arranging, but it still raises an exception when slicing.

2.1.0-beta
Windows 11
AMD Ryzen 7 5800X3D
32GB Ram
Nvidia RTX 4070

Creality K1C rooted.

HornetMountMirrored.zip
debug_Sat_Jun_08_14_28_37_6216.log.zip

@mattddonnelly
Copy link

I'm also having this issue, with the attached file.

I can slice just fine with one object, or with two objects, but if I mirror either one or both objects, I get an access violation error and am unable to slice.

2.1.0-beta
Windows 11
AMD Ryzen 9 5900X 12-Core Processor 4.20 GHz
Installed RAM 64.0 GB
Nvidia RTX 3080

clamp_handle.zip

@sledwina
Copy link
Author

For me the issue is fixed with the 2.1.0 RC.

Noisyfox added a commit to Noisyfox/OrcaSlicer that referenced this issue Jun 23, 2024
…e it cannot properly handle situations that contains negative scale (mirror) / shear (SoftFever#5578)
Noisyfox added a commit to Noisyfox/OrcaSlicer that referenced this issue Jun 23, 2024
…e it cannot properly handle situations that contains negative scale (mirror) / shear (SoftFever#5578, SoftFever#4719)
SoftFever pushed a commit that referenced this issue Jun 26, 2024
* Do not use get_scaling_factor then construct the matrix again, because it cannot properly handle situations that contains negative scale (mirror) / shear (#5578)

* Do not use get_scaling_factor then construct the matrix again, because it cannot properly handle situations that contains negative scale (mirror) / shear (#5578, #4719)
Azio-Pantheon pushed a commit to Pantheon-Design/PantheonSlicer-3 that referenced this issue Jul 31, 2024
* Do not use get_scaling_factor then construct the matrix again, because it cannot properly handle situations that contains negative scale (mirror) / shear (SoftFever/OrcaSlicer#5578)

* Do not use get_scaling_factor then construct the matrix again, because it cannot properly handle situations that contains negative scale (mirror) / shear (SoftFever/OrcaSlicer#5578, SoftFever/OrcaSlicer#4719)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants