That seems to make it work, thanks!
We’ve now released v1.1.1 which undoes the last-minute renderer change – so hopefully this bug shouldn’t happen anymore!
