Just tried 0.0.0.2 and didn't encounter the bug again, even with the same settings.
Nice, I didn't even mean to fix it!