@fcwilt

going to the release version of 3.3 seems to have fixed it.
Thank you very much indeed!!