Yep. It will be the V1.03 update that hopefully wiull have a fix. I know what the error is, I just have to figure out how to deal with it :)
