Thanks for the report, build 355 will fix this issue. More stuff changed from 3.0 -> 3.1 then 2.x->3.0