HFM.NET v10.3.2016

Release Date: January 13, 2024

Fix: Compatibility with Core 0x23
Fix: Work Unit History Export to include Platform data

HFM.NET v10.3.2014

Release Date: January 1, 2024

• Fix: Compatibility with Core 0x23

HFM.NET v10.2.2005

Release Date: June 14, 2023

• Enhancement: Add caching layer to benchmark database queries to increase performance

• Fix: #366 benchmark graph query exception reported by artoar11

• Fix: Crash when opening benchmarks while an offline client is selected

• Fix: Crash when opening benchmarks after adding a new client that hasn't been saved reported by bollix47

HFM.NET v10.1.1994

Release Date: November 25, 2022

• Fix: the installer not being started correctly after downloading an msi update

• Fix: the Test link for the FAH User ID on the Preferences screen

• Fix: the user stats (EOC) task failing to start on startup

• Fix: #358 High DPI grid row scaling (contribution from Justaphf)

• Fix: Core name to slot type mapping. Slot types will now be shown correctly again in the Work Unit History.

• Fix: Benchmarks without frame durations throw error when opening Benchmarks dialog

• Change: Removed the Core ID column from the grid and web generated grid

HFM.NET v10.0.1937

Release Date: May 29, 2022

• Feature: This entire release is centered on work unit data capture. The technology (while still SQLite) used to persist work unit history and benchmark data was completely replaced with Microsoft's latest, and recommended, bits. The database itself is a complete rewrite.

• BIG Thank You to muziqaz, rhavern, hayesk, toTOW, & artoar_11 for helping to test these updates and work out the kinks.

  • What to expect after upgrading

    • There will be an upgrade process that runs on startup to migrate your existing work unit history to the new database. Depending on the size of the history this could take minutes. A progress dialog will keep you informed.
    • Existing benchmark data is not migrated. As such, benchmarks will be empty until you start monitoring with this version and accumulating that data. I don't really care about old benchmarks but there has been some interest in continuing to see them in the benchmarks dialog. Rest assured, the data is still there on your disk and if there is enough interest I can pull it in and merge it with new benchmarks in a future version. If that is what you'd like to see, please respond to and give this GitHub issue a thumbs up.
    • There are many new fields captured in the database. Client Version, Operating System, Platform (CPU & Threads, CUDA/OpenCL and Driver versions), and Processor.
    • Core version is captured correctly (as a string, not numeric). Unit result is also captured as a string and not a hidden numeric value. You should be able to craft custom history queries in a WYSIWYG fashion. Most existing queries should continue to function as intended.
    • The goal of this release is to deliver feature parity using the new persistence technology. However, with regards to benchmarks, it opens up a range of possibilities for slicing the data in different ways. I plan to add some options to allow slicing benchmarks not only by the Processor but by Client Version, OS, Driver Version, etc. If that is of interest to you, please respond to and give this GitHub issue a thumbs up.

• Known Issues

  • When updating an msi installation from v9.28 (the last release) you'll encounter this error dialog. Nothing I can do about it because the issue is in v9.28. Please just click OK and allow HFM to exit. You'll need to double-click the downloaded msi file to kick off the installation. I have the fix already included for the next release.

• HFM now requires .NET version 6.0.2 or better. If it is not installed on your machine you will be prompted to download and install it. Please select Windows > Run desktop apps > Download x64 or Download x86, based on your OS architecture.
  • If you have v6.0.0 or v6.0.1 installed, HFM may silently fail to start. Please check your installed programs first before creating a new GitHub issue. The application entry should look something like this. All you need to do is download the latest desktop runtime and install it.

HFM.NET v9.28.1718

Release Date: January 15, 2022

• Fix: Issue #354 Binding Reset Exception (thanks toTOW, bollix47, and PantherX, rhavern, muziqaz)

• Fix: Report Exception button on the exception dialog does not open the website (thanks PantherX)

• Fix: Window size save and restore when log viewer is not visible (thanks toTOW)

• HFM now requires .NET version 6. If it is not installed on your machine you will be prompted to download and install it. Please select Windows > Run desktop apps > Download x64 or Download x86, based on your OS architecture.

HFM.NET v9.27.1700

Release Date: November 14, 2021

• Enhancement: Issue #96 Add an option to "Disable" a Client in a HFM Configuration File

• Enhancement: Issue #281 Hide off-line clients (View > Show/Hide Inactive Slots or Alt+H)

• Enhancement: Issue #316 Changing calculation settings in Preferences/Options should force a RefreshAll

• Enhancement: Issue #319 Better STATUS column state names & sorting (Yellow status now reads "Running with Benchmark TPF")

• Enhancement: Issue #320 CREDIT in summary.html could be right justified

• Enhancement: Issue #347 Work Unit History should store, display and export WU Base Credit

• Fix: Issue #352 Username validation check

• Fix: Progress reporting after CORE_RESTART

HFM.NET v9.26.1685

Release Date: September 15, 2021

• Fix: Issue #353 Error opening web page links in .NET 5 version.

• Fix: Calculate frame duration correctly after work unit is INTERRUPTED (paused). Thanks muziqaz!

• Enhancement: Add Timeout, Expiration, and Collection Server to Work Unit Queue.

• Enhancement: Better Work Unit Queue value formatting to match values in FAHControl.

• Enhancement: Issue #311 Persist Work Unit Queue Splitter Location.

• Enhancement: Add detection for BAD_FRAME_CHECKSUM work unit result as a failed work unit.

• Change: Place system information in it's own section within the Work Unit Queue. Always show CPU Threads.

HFM.NET v9.25.1650

Release Date: August 17, 2021

• Enhancement: .NET 5.0 support. A zip release is now provided and tagged as net5.0-windows. Please give this build a try. The goal with this release is to identify any issues with the migration to modern .NET before moving all releases to this runtime. If you do not have the .NET runtime installed then you should be prompted to install the runtime when running HFM.exe.

  • It will be clear that you're running the .NET 5.0 build when you see "(dotnet)" in the application title bar. You can also see the version of the runtime being used by opening the Help > About dialog.

• Enhancement: Add processor information to the slot summary web generation output (xml and html) #350 (firedfly)

• Enhancement: Move processor information from the queue viewer to the main grid to match web generation output.

• Enhancement: Limit the number of log lines included in the web generation files. #351 (firedfly)

• Enhancement: Rework web generation HTML to modern standards and leverage bootstrap for a responsive layout. There are no breaking changes to the generated xml data.

• Enhancement: Update web generation visual styles (colors). Also added a None style if you prefer no color.

• Change: .NET Framework distribution now requires .NET v4.7.2.

• Change: Format queue combo box as "WU00:FS00:" to better match client logs.

• Change: Remove any remnants of Mono runtime support.

• Change: Update all supporting libraries to versions compatible with .NET 5.0.

HFM.NET v9.24.1531

Release Date: May 11, 2021

• Change: Version scheme removes the leading zero. This is to help with builds and Windows Installer things. You'll now see some version numbers reported with a trailing zero instead.
• Fix: Issue #340 This is a fix for localized characters encoded as hex in the data provided by FAHClient. It also fixes the issues users in those localized areas are having running ARM and Intel GPU clients.
• Fix: Issue #345 Error message when trying to view Benchmark of project which is not on psummary