This is an error in 0.38 and has been fixed so far. This will be fixed in the upcoming 0.38b patch later this week.
Awesome! Can't wait
