@dustindizzle11 This is a well known issue with 1.2. I fixed it almost two revs after releasing 1.2.0, but had many other bits that made it unfeasible to come out with another fix (and it was mid imaging season.)