We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
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
UVtools v4.0.4 X64 Operative system: Darwin 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020 X64 Processor: Apple M2 Max Processor cores: 12 Memory RAM: 12.91 / 27.72 GB Runtime: osx.14-x64 Framework: .NET 6.0.24 AvaloniaUI: 11.0.5 OpenCV: 4.8.0 Sreens, resolution, working area, usable area: 1: 1728 x 1117 @ 100% (Primary) WA: 1728 x 1023 UA: 1728 x 1023 Path: /Applications/UVtools.app/Contents/MacOS/ Executable: /Applications/UVtools.app/Contents/MacOS/UVtools Loaded file: stock.pm5s [Version: 518] [Class: PhotonWorkshopFile]
The OSX arm64 builds appears to not run. I tested a variety of versions, as far back as 3.6.0 .
The only error output is a simple dialog with: "The application “UVtools” can’t be opened."
This is AFTER permitting the app to run, via the normal quarantine allowance, "Open anyway".
NOTE: the System Information above is for the x86_64 version, which DOES run (through Apple's emulation, I assume).
No response
The text was updated successfully, but these errors were encountered:
sn4k3
No branches or pull requests
System
Printer and Slicer
Description of the bug
The OSX arm64 builds appears to not run. I tested a variety of versions, as far back as 3.6.0 .
The only error output is a simple dialog with:
"The application “UVtools” can’t be opened."
This is AFTER permitting the app to run, via the normal quarantine allowance, "Open anyway".
NOTE: the System Information above is for the x86_64 version, which DOES run (through Apple's emulation, I assume).
How to reproduce
Files
No response
The text was updated successfully, but these errors were encountered: