-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
[Bug] System.IO.Compression.Native is missing #957
Comments
This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌 |
I have the same issue. installed V5 and when I go to launch UVTools, I get the same crash report as Gruntsky My system info: Path: C:\Program Files\UVtools |
I get an error while saving goo file but is different from yours. |
I tried your UVTools-core dll my my issue, but no change. My issue shows on launch. Do you want me to create a different issue? |
No, it may be related to the OP, as the launch it open the SL1 file which is a ZIP. Let me find some information about this. Meanwhile revert back to previous version. |
Looks like the problem is the missing |
Just replaced the .dll file and opened the file. Save looks to have worked with the new .dll |
@mjf55 I just downloaded the v5 zip and Native.dll is there... I also reinstalled via MSI and I got the native dll in my folder. |
Yes, I can confirm System.IO.Compression.Native.dll is present in installation folder |
Found the cause: dotnet/runtime#82518 Solution:For who land here, Uninstall UVtools and Reinstall. |
System
Printer and Slicer
Description of the bug
Updated to newest version, now when I try to save an edited file I receive this error:
Uninstalled UVTools and re-installed, received the same error upon saving.
How to reproduce
Files
No response
The text was updated successfully, but these errors were encountered: