Hi @david25 this error has been fixed in VisualARQ 2.9: VisualARQ 2 - Version 2.9 released (for Rhino 5, 6 and 7)