Skip to content

Releases: sn4k3/UVtools

v1.1.2

02 Nov 23:56
Compare
Choose a tag to compare
  • (Add) Program start elapsed seconds on Log
  • (Add) Lift heights @ speeds, retract speed, light-off information to status bar
  • (Fix) Per layer settings are being lost when doing operations via tools that changes the layer count
  • (Fix) Current layer height mm was being calculated instead of showing the stored position Z value (For hacked files)
  • (Fix) Zip: By using hacked gcodes were possible to do a lift sequence without returning back to Z layer position
  • (Fix) ZCodex: Read per layer lift height/speed, retract speed and pwm from GCode
  • (Fix) Status bar, layer top and bottom bar: Break content down for the next line if window size overlaps the controls
  • (Fix) Status bar: Make right buttons same height as left buttons
  • (Improvement) CWS: Better gcode parser for decoding
  • (Change) GCodes: Cure commands (Light-on/Cure time/Light-off) are only exposed when exposure time and pwm are present and greater than 0 [Safe guard]
  • (Change) Zip: If only one G0 command found per layer, it will be associated to the cure z position (No lift height)
  • (Change) Merged bottom/normal exposure times on status bar
  • (Change) Tabs: Change controls spacing from 5 to 2 for better looking
  • (Change) Deploy UVtools self-contained per platform specific: (#89)
    • Platform optimized
    • Reduced the package size
    • Includes .NET Core assemblies and dont require the installation of .NET Core
    • Can execute UVtools by double click on "UVtools" file or via "./UVtools" on terminal
    • Naming: UVtools_[os]-[architecture]_v[version].zip
    • "universal" zip file that includes the portable version, os and architecture independent but requires dotnet to run, these build were used in all previous versions

v1.1.1

01 Nov 05:52
Compare
Choose a tag to compare
  • (Fix) PHZ, PWS, LGS, SL1 and ZCodex per layer settings and implement missing properties on decode
  • (Fix) LGS and PHZ Zip wasn't setting the position z per layer
  • (Fix) Add missing ctb v3 per layer settings on edit parameters window
  • (Fix) PWS per layer settings internal LiftSpeed was calculating in mm/min, changed to mm/sec

v1.1.0

01 Nov 02:46
Compare
Choose a tag to compare
  • (Add) photons file format (Read-only)
  • (Add) Allow mouse scroll wheel on layer slider and issue tracker to change layers (#81)
  • (Add) Menu - Help - Open settings folder: To open user settings folder
  • (Add) When a file doesn't have a print time field or it's 0, UVtools calculate the approximate time based on parameters
  • (Add) Per layer settings override on UVtools layer core
  • (Add) Tool - Edit print parameters: Allow change per layer settings on a layer range
  • (Add) Tool Window - Layer range synchronization and lock for single layer navigation (Checkbox)
  • (Add) Tool Window - Change the start layer index on range will also change the layer image on background
  • (Improvement) Adapt every file format to accept per layer settings where possible
  • (Improvement) Better gcode checks and per layer settings parses
  • (Change) When converting to CTB, version 3 of the file will be used instead of version 2
  • (Change) When converting to photon or cbddlp, version 2 of the file will be used
  • (Change) New logo, thanks to (Vinicius Silva @Photonsters)
  • (Fix) MSI installer was creating multiple entries/uninstallers on windows Apps and Features (#79)
  • (Fix) Release builder script (CreateRelease.WPF.ps1): Replace backslash with shash for zip releases (#82)
  • (Fix) CWS file reader when come from Chitubox (#84)
  • (Fix) CWS was introducing a big delay after each layer, LiftHeight was being used 2 times instead of LiftSpeed (#85)
  • (Fix) CWS fix Build Direction property name, was lacking a whitespace
  • (Fix) Layer bounds was being show for empty layers on 0x0 position with 1px wide
  • (Fix) Empty layers caused miscalculation of print volume bounds
  • (Fix) Recalculate GCode didn't unlock save button
  • (Fix) Tool - Calculator - Light-Off Delay: Wasn't calculating bottom layers
  • (Change) Drop a digit from program version for simplicity, now: MAJOR.MINOR.PATCH
    • Major: new UI, lots of new features, conceptual change, incompatible API changes, etc.
    • Minor: add functionality in a backwards-compatible manner
    • Patch: backwards-compatible bug fixes
  • (Upgrade) Avalonia framework to preview6

v1.0.0.2

23 Oct 21:54
Compare
Choose a tag to compare
  • (Fix) ROI selection button on bottom was always disabled even when a region is selected
  • (Fix) Settings - Issues- "Pixel intensity threshold" defaults to 0, but can't be set back to 0 after change (minimum is 1). (#78)
  • (Fix) Settings - Issues - "Supporting safe pixels..." is present twice (#78)
  • (Fix) Settings - Layer repair - Empty layers / Resin traps texts are swapped in the settings window (#78)

v1.0.0.1

23 Oct 02:11
Compare
Choose a tag to compare
  • (Change) Checked and click buttons highlight color for better distinguish
  • (Fix) Move user settings to LocalUser folder to allow save without run as admin
  • (Fix) Save button for print parameters were invisible

v1.0.0.0

22 Oct 03:34
Compare
Choose a tag to compare
  • (Add) Multi-OS with Linux and MacOS support
  • (Add) Themes support
  • (Add) Fullscreen support (F11)
  • (Change) GUI was rewritten from Windows Forms to WPF Avalonia, C#
  • (Improvement) GUI is now scalable
  • (Fix) Some bug found and fixed during convertion

v0.8.6.0

17 Oct 03:36
Compare
Choose a tag to compare
  • (Change) Island detection system:
    • Before: A island is consider safe by just have a static amount of pixels, this mean it's possible to have a mass with 100000px supported by only 10px (If safe pixels are configured to this value), so there's no relation with island size and it supporting size. This leads to a big problem and not detecting some potential/unsafe islands.
    • Now: Instead of a static number of safe pixels, now there's a multiplier value, which will multiply the island total pixels per the multiplier, the supporting pixels count must be higher than the result of the multiplication.
      • Formula: Supporting pixels >= Island pixels * multiplier
      • Example: Multiplier of 0.25, an island with 1000px * 0.25 = 250px, so this island will not be considered if below exists at least 250px to support it, otherwise will be flagged as an island.
      • Notes: This is a much more fair system but still not optimal, bridges and big planes with micro supports can trigger false islands. While this is a improvement over old system it's not perfect and you probably will have islands which you must ignore. Renember that you not have to clear out the issue list! Simply step over and ignore the issues you think are false-positives.

v0.8.5.0

14 Oct 17:43
Compare
Choose a tag to compare
  • (Add) Tool - Calculator: Convert millimeters to pixels
  • (Add) Tool - Calculator: Find the optimal "Ligth-Off Delay"
  • (Add) Internal abstraction of display size to all file formats
  • (Add) Default demo file that loads on startup when no file is specified (this can be disable/enabled on settings)

v0.8.4.3

13 Oct 01:06
Compare
Choose a tag to compare
  • (Add) Tool - Layer repair: Allow remove islands recursively (#74)
  • (Fix) Pixel Editor: Cursor dimentions when using brushes with thickness > 1 (#73)

v0.8.4.2

10 Oct 22:00
Compare
Choose a tag to compare
  • (Fix) pws and pw0: Error when try to save or copy to clipboard the slicer information / properties
  • (Fix) photon, ctb, cbbdlp, phz, pws, pw0: Rare cases were decoding image generate noise and malformed image
  • (Fix) Rare cases where manipulation of images generate areas with noise