vaSpace bug

Hi @nicolas.noth, we have just published VisualARQ 2.10, which fixes this error you reported: