Home

Awesome

UVtools

License GitHub repo size Code size Total code Nuget GitHub release (latest by date including pre-releases) Downloads Chocolatey GitHub Sponsors

Download the latest version at:

https://github.com/sn4k3/UVtools/releases/latest

To auto install on Windows (package manager):

Note: Winget is included on Windows 10 with recent updates and Windows 11 by default.

To auto install on Linux:

[ "$(command -v apt)" -a -z "$(command -v curl)" ] && sudo apt-get install -y curl 
[ "$(command -v dnf)" -a -z "$(command -v curl)" ] && sudo dnf install -y curl
[ "$(command -v pacman)" -a -z "$(command -v curl)" ] && sudo pacman -S curl
[ "$(command -v zypper)" -a -z "$(command -v curl)" ] && sudo zypper install -y curl
bash -c "$(curl -fsSL https://raw.githubusercontent.com/sn4k3/UVtools/master/Scripts/install-uvtools.sh)"

To auto install on MacOS:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/sn4k3/UVtools/master/Scripts/install-uvtools.sh)"

To downgrade to a previous version:

# Replace x.x.x by the version you want to install
bash -c "$(curl -fsSL https://raw.githubusercontent.com/sn4k3/UVtools/master/Scripts/install-uvtools.sh)" -- x.x.x

MSLA/DLP, file analysis, calibration, repair, conversion and manipulation

This simple tool can give you insight of supports and find key failures.
Did you forget what resin or other settings you used on a project? This can also save you, check every setting that were used with or simply change them!

GUI Screenshot GUI Screenshot Islands

Why this project?

I don't own a Prusa SL1 or any other resin printer, for now I’m only a FDM user with Prusa MK3 and a Ender3. PrusaSlicer is my only choose, why? Because I think it's the best and feature more, at least for me, simple but powerful.

So why this project? Well in fact I’m looking for a resin printer and i like to study and learn first before buy, get good and don't regret, and while inspecting i found that resin printers firmwares are not as universal as FDM, too many file formats and there before each printer can use their own property file, this of course limit the software selection, for example, only PrusaSlicer can slice SL1 files. So with that in mind I'm preparing when I get a resin printer in future I can use PrusaSlicer instead of others. I've explored the other slicers and again, no one give me joy, and i feel them unstable, many users slice model on PrusaSlicer just to get those supports and export STL to load in another, that means again PrusaSlicer is on the win side, the problem is they can't slice directly on PrusaSlicer, so, in the end, my project aims to do almost that, configure a printer on PrusaSlicer, eg: EPAX X1, slice, export file, convert SL1 to native printer file and print.

Please note I don't own any resin printer! All my work is virtual and calculated, so, use experimental functions with care! Once things got confirmed a list will show. But also, I need victims for test subject. Proceed at your own risk!

Features

Known File Formats

PrusaSlicer

Note that some variables will only work if the target format supports them, otherwise they will be ignored.
Replace the "xxx" by your desired value in the correct units

Command-line

UVtoolsCmd (Console) executable

Usage:
  UVtoolsCmd [command] [options]

Options:
  -q, --quiet     Make output silent but exceptions error will still show
  --no-progress   Show no progress
  --dummy         Do not save alterations to file
  --core-version  Show core version information
  --version       Show version information
  -?, -h, --help  Show help and usage information

Commands:
  set-properties <input-file> <property=value>                                            Set properties in a file or to it layers with new values
  run <input-file> <classes/files>                                                        Run operations, suggestions and/or scripts
  convert <input-file> <target-type/ext> <output-file>                                    Convert input file into a output file format by a known type or extension []
  extract <input-file> <output-folder>                                                    Extract file contents to a folder []
  copy-parameters <input-file> <target-files>                                             Copy print parameters from one file to another
  set-preview, set-thumbnail <input-file> <file path|layer index|:random-layer|:heatmap>  Sets and replace thumbnail(s) in the file [default: :heatmap]
  compare <input-file-a> <input-file-b>                                                   Compare two files and output the differences
  print-issues <input-file>                                                               Detect and print issues
  print-properties <input-file>                                                           Prints available properties
  print-gcode <input-file>                                                                Prints the gcode of the file if available
  print-machines                                                                          Prints machine settings
  print-formats                                                                           Prints the available formats

Note: On each command you can use -? to see specific command help and extra options

UVtools (UI) executable

Legacy

The following commands are the old way and commands under the UI executable, they will be removed in near future, try to not use them, please prefer UVtoolsCmd.

Requirements

Windows

  1. Windows 10 or greater
    1. If on Windows 10/11 N or NK:
      • Media Feature Pack must be installed
      • Press Windows + R
      • Type: appwiz.cpl (and press Enter key)
      • Click on: Turn Windows features on or off
      • Check the "Media Extensions" and click Ok
  2. 8GB RAM or higher + 512MB per CPU core
  3. 64 bit System
  4. 1920 x 1080 @ 100% scale as minimum resolution

Linux

  1. 8GB RAM or higher + 512MB per CPU core
  2. 64 bit System
  3. 1920 x 1080 @ 100% scale as minimum resolution

Installing the dependencies

Copy the following script, paste and run on a terminal:
(Required if you didn't use the auto installer or if it failed to detect and install dependencies)

[ "$(command -v apt-get)" -a -z "$(command -v curl)" ] && sudo apt-get install -y curl 
[ "$(command -v pacman)" -a -z "$(command -v curl)" ] && sudo pacman -S curl
[ "$(command -v dnf)" -a -z "$(command -v curl)" ] && sudo dnf install -y curl
[ "$(command -v zypper)" -a -z "$(command -v curl)" ] && sudo zypper install -y curl
sudo bash -c "$(curl -fsSL https://raw.githubusercontent.com/sn4k3/UVtools/master/Scripts/install-dependencies.sh)"
<!-- sudo bash -c "$(curl -fsSL https://raw.githubusercontent.com/sn4k3/UVtools/master/Scripts/libdl-solver.sh)" !-->

To run UVtools open it folder on a terminal and call one of:

If you downloaded the .AppImage package variant you must set run permissions to it before attempt to run it:
AppImage permissions

Mac

  1. macOS 13 Monterey or higher
  2. 8GB RAM or higher + 512MB per CPU core
  3. Install UVtools via the auto installer

To run UVtools open it folder on a terminal and call one of:

How to use

There are multiple ways to open your file in UVtools:

  1. Open UVtools and load your file (CTRL + O) (File -> Open)
  2. Open UVtools and drag and drop your file inside window
  3. Drag and drop file into UVtools.exe
  4. Set UVtools the default program to open your files

Library -> Developers

Are you a developer? This project include a .NET 6.0 library (UVtools.Core) that can be referenced in your application to make use of my work. Easy to use calls that allow you work with the formats. For more information navigate main code to see some calls.

Nuget package: https://www.nuget.org/packages/UVtools.Core

Nuget

dotnet add package UVtools.Core

Scripting:

Develop and build from Source

Build directions
The fastest way to compile the project is by run the build/compile.bat, however if you wish to develop with visual studio follow the following steps:

  1. Install Visual Studio and include .NET development support
  2. Install the .NET 6.0 SDK if not included on previous installation
  3. Install the Avalonia for Visual Studio:
  4. Install the Wix Toolset: (Required only for MSI build, optional)
  5. Open UVtools.sln
  6. Build

TODO

Support my work / Donate

All my work here is given for free (OpenSource), it took some hours to build, test and polish the program. If you're happy to contribute for a better program and for my work i will appreciate the tip.
Use one of the following methods:

GitHub Sponsors Donate PayPal

Contributors

GitHub contributors
Contributors