Hi @avatarlucas this issue should be fixed in VisualARQ 3.8 RC1, released yesterday. You can find it here: VisualARQ 3 - Version 3.8 RC1 released
Hi @avatarlucas this issue should be fixed in VisualARQ 3.8 RC1, released yesterday. You can find it here: VisualARQ 3 - Version 3.8 RC1 released