Hi @user992,
I just want to let you know that we have just released VisualARQ 2.13, which fixes this error you reported.
You have all the information about this new version here: VisualARQ 2 - Version 2.13 released
Enjoy!
1 Like