Hi,
Big thanks for reporting it. We've been able to reproduce this behavior here too and we'll continue analyzing this issue - it'll need to be investigated more in deep by our main developers to see, where the problem might be and if it could be fixed from our side or the Otoy team will have to adjust their implementation. Hopefully, a solution will be found soon.
Best regards,