@seflorance we have finally fixed this bug in VisualARQ 2.8.4 version, that is already available to download: VisualARQ 2 - Version 2.8.4 released
@seflorance we have finally fixed this bug in VisualARQ 2.8.4 version, that is already available to download: VisualARQ 2 - Version 2.8.4 released