See:
Hi Roi, Please send us the model to visualarq@asuni.com and we will try to fix this bug.
Hi @rheinason!
This bug has been fixed in VisualARQ 2.8: VisualARQ 2 - Version 2.8 released