Skip to content

SlotForge Paddock 1.3.0

Choose a tag to compare

@theDutchmanJames theDutchmanJames released this 10 Nov 18:42

SlotForge Paddock 1.3.0

A major update to the collection, workshop and shared racing library.

Highlights

  • Shared local library with compatible SlotForge Timing: both apps can use the same local SQLite collection, including cars and racing history. Existing collections are preserved during adoption; this is separate from LAN sharing and Dealership Mode.
  • Car merging: review the fields, photos, history and supported settings to include, choose the main car, and retain the retired car's original information in the archive. Late old-car history receives its own review.
  • Rebuilds and planned builds: link an original car to its rebuild, preserve the original history, and plan catalogue parts with shopping items tied to the build.
  • Racing history and comparisons: richer session views, lane records, historical evidence and pace comparisons, with safer corrections, withdrawals and recovery.
  • Workshop and collection tools: job types, Manuals and Part Guides, catalogue management, expanded sorting, UI zoom and improved car comparisons.
  • Easier reviews: Select all / Clear selection and selection counts throughout reviews with selectable fields, including merge sections and catalogue imports.
  • Slotcar product research: the AI import kit includes product category and racing class. Ownership details remain manual; the prompt asks for at least five sources and three agreeing sources for verified values, without mandatory source URLs.
  • Storage and responsiveness: incremental SQLite reads and writes, background result processing, durable operation receipts and more precise refreshes.

Updating and downloads

Create a backup in Paddock before updating. Shared-library features require a compatible Timing build; updating Paddock does not update Timing.

  • Windows: download the portable Windows x64 executable.
  • Linux: native x64 and ARM64 AppImage / Debian packages are attached as their GitHub builds complete.
  • macOS: universal downloads are attached if the native build succeeds.
  • Source: the source ZIP contains the app, build tooling, documentation and tests. Internal handoffs, design drafts, review reports, local test output and databases are excluded.

Checksums accompany the downloads. App packages contain only runtime files and required licences.