2 comments
Comment actions Permalink

The new build of 2.0 that came out last night appears to have fixed the issue. Thanks guys.

0
Comment actions Permalink

Well, I don't know how you did it, but the new build of 2.0 from last night fixed this issue (don't see anything about that in the changelog.) You can close this.

0

Please sign in to leave a comment.