@ Wolfgang
That screenshot is very helpful, thanks! I located the bug causing this error and have fixed it. I will release a new update asap.