I can only go back to 6.2, but it works for me in that version as well. I am not aware of any settings that would cause this. Best I can say is maybe the experts from Down under can answer this???
Apart from the Scan Defines/Substitutions, there is no other setting that could affect this behavior.
All I can say is that 6.1 is quite an old version and we’ve fixed quite a few bugs since then. I cannot reproduce the error in the current version. Please upgrade if possible.
I can confirm that I could reproduce the issue you reported in 6.1 (when having the Scan Define ON or OFF), but the latest release v6.4 is working fine when having the Scan Defines ON. As per Roman’s note, please upgrade to v6.4 and let us know if you still have any issue.