I'm pretty sure I found what was causing it, as well as the other issue you mentioned. I'm working on a 1.2.0 update that will include fixes for that along with a bunch of other improvements. Thanks again for reporting both of them.
