DisplayCAL 3.1.3 released

This is a maintenance release for 3.1.

Added in this release:

  • Device link profile as possible 3D LUT output format.
  • French ReadMe (thanks to Jean-Luc Coulon).
  • Partial traditional chinese localization (work-in-progress, thanks to 楊添明).
  • When you change the language in DisplayCAL, the Windows Profile Loader will follow on-the-fly if running.
  • Synthetic ICC profile creator: Capability to specify profile class, technology and colorimetric image state.
  • Windows: When the display configuration is changed while DisplayCAL is running, automatically re-enumerate displays, and load calibration if using the profile loader.
  • Profile loader (Windows): Starting the loader with the --oneshot argument will make it exit after launching.

Changed in this release:

  • Updated ReShade 3D LUT installation instructions in the ReadMe.
  • Improved “Enhance effective resolution of PCS to device tables” smoothing accuracy slightly.
  • Profile loader (Windows):
    • Detect CPKeeper (Color Profile Keeper) and HCFR.
    • Show any calibration loading errors on startup or display/profile change in a notification popup, and also reflect this with a different icon.

Fixed in this release:

  • Added semicolon (“;”) to disallowed profile name characters.
  • ICC profile objects were leaking memory.
  • Windows: Made sure that the virtual console size is not larger than the maximum allowed size (fixes possible inability to launch Argyll CMS tools on some systems if the Windows scaling factor was equal to or above 175%).
  • Windows (Vista and newer): Use system-wide profiles if per-user profiles are disabled.
  • Profile loader (Windows):
    • If Windows calibration management is enabled (not recommended!), correctly reflect the disabled state of the profile loader in the task tray icon and don’t load calibration when launching the profile loader (but keep track of profile assignment changes).
    • Prevent a race condition when “Fix profile associations automatically” is enabled and changing the display configuration, which could lead to wrong profile associations not being fixed.
    • Sometimes the loader did not exit cleanly if using taskkill or similar external methods.
    • Prevent a race condition where the loader could try to access a no longer available display device right after a display configuration change, which resulted in no longer being able to influence the calibration state (requiring a loader restart to fix).
    • Profile loader not reacting to display changes under Windows XP.