Excessive charge count for Expanded Probe Launchers with Core Probes

[R3ality]

Description

When setting the loaded charges of an Expanded Probe Launcher module (any variant) to Core Scanner Probes (any variant) then the charge count is set as 80 (maximum the launcher could technically fit). Expected loaded charge count would be 8 (maximum launchable). Combat Scanner Probes (any variant) are not affected and charge count for these is already set to 8 by default.

Have not found a way to change/limit this manually. Even setting a specific charge count in the ship inventoy and drag-dropping them to the launcher the charge type is changed but not the charge count. A high charge count becomes problematic when exporting the fit into EVE (a multibuy including 80 Sisters probes probes is excessively expensive for example).

When opening a previously saved fit from an earlier version of pyfa (where the default charge count was 8) then this loads correctly and charge count is retained as 8 until the charge type is changed.

Reproduction steps

1. Fit an Expanded Probe Launcher (any variant)
2. Set the loaded charges as any of the following:
   • Core Scanner Probe I
   • RSS Core Scanner Probe
   • Sisters Core Scanner Probe
3. Outcome: Charge count is set to 80 (expected charge count to be set to 8)

Version info

pyfa Version v2.65.2
EVE Data Version: 3137986 (2025-12-11 15:11:21)
Windows 10 64-bit LTSC