Skip to content

Handle HCE-only engines that do not advertise UseNNUE - #7

Merged
KnightStackSys merged 2 commits into
mainfrom
fix/optional-usennue-hce-20261115
Nov 15, 2026
Merged

KnightStackSys merged 2 commits into
mainfrom
fix/optional-usennue-hce-20261115

Conversation

@KnightStackSys

Copy link
Copy Markdown
Owner

Fix

  • When UseNNUE is absent from an engine's UCI options and the config requests UseNNUE: false, Tunex treats that engine as HCE-only and does not send an unsupported setoption command.
  • If UseNNUE is advertised, normal configuration remains unchanged.
  • Requests for UseNNUE: true on engines that do not advertise it still fail with strict option validation; all other missing options remain errors.

Tests

Add unit tests for HCE-only skip, advertised option, strict error, and non-strict compatibility.

Reproduction

An IronPhoenix HCE-only build without UseNNUE previously failed with New engine does not advertise UCI option 'UseNNUE' while using the standard UseNNUE: false config. This PR removes that false failure.

@KnightStackSys
KnightStackSys merged commit eece18a into main Nov 15, 2026
4 checks passed
@KnightStackSys
KnightStackSys deleted the fix/optional-usennue-hce-20261115 branch November 15, 2026 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant