This is a known issue that is on our 3.0.5 Known Issues thread. We are currently looking into fixing it.