Log playback does not reflect Range scaling used during collection

To replicate - create log file with multiple Max Ranges selected (e.g. 5m, 10m, 30m)
Next, open log for playback. Range can be set to 50m, or any value, and log will play back in this scale, but not scaled. Thus, targets that are measured at 2.5/5m range look like 25m/50m range.

Expected behavior - user cannot select Range during log playback. Playback updates with changes to range at relevant points in log file, based on what was recorded.
Pingviewer 2.4.1

Screenshots are the same moment of time in same log file, but with range set to different values.
Operating System: Windows 11

Start with the log playback and Range-selection handling, then reproduce the issue using a log recorded with multiple ranges such as 5m, 10m, and 30m. Verify that Range cannot be selected during playback and that the display updates to the recorded ranges at the relevant points in the log.

Written by the indexing model from the issue text.