Thanks for reporting this issue with your files. I would like to have you send us your factory files or attach them to your post so we can officially deem this resolved. We were able to recreate a similar issue to what you've described in version 4.1.0 and have since fixed the issue in the latest release (4.1.2). You can read all about the major improvements in this release on our release notes page.