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

[Bug] Anycubic Photon Mono M7 Max File Format Incorrect #995

Open
limaciform opened this issue Feb 4, 2025 · 2 comments
Open

[Bug] Anycubic Photon Mono M7 Max File Format Incorrect #995

limaciform opened this issue Feb 4, 2025 · 2 comments
Assignees

Comments

@limaciform
Copy link

System

UVtools v5.0.6 X64
Operative system: Microsoft Windows 10.0.26100 X64
Processor: Intel(R) Core(TM) i9-14900HX
Processor cores: 32
Memory RAM: 9.78 / 31.73 GB
Runtime: win-x64
Framework: .NET 9.0.1
AvaloniaUI: 11.2.3
OpenCV: 4.10.0

Sreens, resolution, working area, usable area:
1: 2560 x 1600 @ 150% (Primary) (On this)
    WA: 2560 x 1528    UA: 1707 x 1019

Path:       C:\Program Files\UVtools\
Executable: C:\Program Files\UVtools\UVtools.exe

Printer and Slicer

  • Printer: Anycubic Photon Mono M7 Max
  • Slicer: PrusaSlicer

Description of the bug

Notes section of PrusaSlicer Printers tab shows file format as PM5M when is should be PM7M, peventing UVTools from autosaving/converting file format.

Image

Works as intended if PM5M is changed to PM7M and saved as a seperate printer profile.

How to reproduce

Add Anycubic Photon Mono M7 Max profile to PrusaSlicer and check printer tab notes to see FILEFORMAT_PM5M.

Files

No response

Copy link

github-actions bot commented Feb 4, 2025

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! 🙌

@sn4k3
Copy link
Owner

sn4k3 commented Feb 4, 2025

Thanks, will fix in next patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants