-
-
Notifications
You must be signed in to change notification settings - Fork 759
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
Error when mirroring detail #5307
Comments
The same happens to me Happened after trying to slice a model exported from fusion 360. Probable cause: After mirroring, Orca tries to create a temperary file next to the original one. Because unzipping or exporting creates a temporary file in their appdata folder, OrcaSlicer may be trying to create a file inside a folder that it cannot have an access to. I exported the model as stl to other location, replaced model with that stl, and redone the mirroring, and no error appeared - which confirms the appdata folder not accessible theory. Everything was working on 01.05.24 version of OrcaSlicer. |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale. |
Is there an existing issue for this problem?
OrcaSlicer Version
2.0.0
Operating System (OS)
Windows
OS Version
Windows 11
Additional system information
No response
Printer
Voron 2.4 300 0,4mm
How to reproduce
7_Skoba_p2.zip
Actual results
If use autoorientation give error
It say that Object has zero size and cant be arranged
With manual placement it say "Fatal error occured "Violation of access rights"
Please save project and restart programm
Save project and import geomery again - make same error
If i place details in prusa and open project in Orca - it can be sliced
Expected results
No error on mirroring detail
Project file & Debug log uploads
Log attached
debug_Thu_May_09_19_44_08_17240.log.zip
project.zip
Checklist of files to include
Anything else?
/
The text was updated successfully, but these errors were encountered: