And the nexstorm archive for the same day. Note that strikes are initially showed on almost the same position, but if there are many strikes nexstorm shows they practically above the detector. Stopping and restarting nexstorm does recover this problem, but depending on the number of strikes per minute the ranging shift can occur very rapidly. You can see on the .nex file several stops to try to recover the ranging.
I've tryed everything with the ranging options, particularly it seems that TRAC settings have nothing to do, and also noise ranging assist or assigned virtual memory does nothing.
It is indeed for me not clear: the ranging becomes better closing and restarting Nexstorm, but maybe the best results are closing and reinitiating the whole windows session - I'm uncertain.