Skip to content

RAPIID v4.0.1

Choose a tag to compare

View all tags
@aharmer aharmer released this 23 Jul 05:22
· 5 commits to main since this release
v4.0.1
7d00d83

Changelog

All notable changes to this project are documented here.

[4.0.1] — 2026-07-23

Patch release. Fixes a packaging fault that prevented v4.0 from starting on
machines without a conda installation, and makes FLIR camera setup diagnosable.

Added

  • Documented the FLIR Spinnaker SDK prerequisite in the installer section of
    the README. The SDK supplies the FLIR camera driver, which cannot be bundled
    into the installer, so a clean machine detects no FLIR camera even though the
    app is otherwise working. The note explains that the SDK version need not
    match the app — RAPIID ships its own Spinnaker runtime (2.7.0.128) and needs
    the SDK only for the driver — and makes clear it is not needed for
    webcam-only use.
  • Step-by-step Spinnaker SDK installer instructions: which installer to
    download (x64), the Application Development profile, the Visual Studio
    prompt, when to tick "I will use GigE cameras" (not for the USB 3.0
    Blackfly S), and that evaluation programs can be declined. Also notes that
    SpinView can be used to test the camera independently of RAPIID.

Fixed

  • FLIR detection failures were invisible. Diagnostics were written with
    print(), but the app is frozen with base="Win32GUI" and therefore has no
    console, so end users saw cameras silently missing with no explanation. The
    reason a FLIR camera was not found is now reported in the in-app log panel,
    along with a note that the Spinnaker SDK is only required for FLIR cameras.
    The camera-discovery error handler no longer refers users to a console that
    does not exist.

  • Frozen builds failed to start on machines without a conda install, with
    "The code execution cannot proceed because zlib.dll was not found".
    python38.dll links against zlib.dll dynamically in conda builds, but
    cx_Freeze placed zlib.dll under lib/, where the Windows loader does not
    look — it searches the executable's own directory. Development machines
    masked this because the conda environment is on PATH. setup.py now ships
    zlib.dll alongside the executable, and fails the build early if it cannot
    be located in the active environment.

Assets 3
Loading