Okay, I found the plugin and got it functioning. Then I tried a sample slice with tree support. Boy, what a mistake. Ate up 2.5G of RAM trying to slice it, and got stuck half way through. For compairison, 3.1 sliced it in 1.6G of RAM and powered through it to the end with normal supports. Is this what we can expect with 3.2 overall, or are they working on tightening it up a bit? I get the feeling that if I used regular support 3.2 would still not be as efficient, and that was really causing me issues in 3.1 already. 3.0 was okay, but 3.1 fixed rafts and support interfaces so nicely, that I was willing to overlook some of the clunkyness. I'm not too keen on what I am seeing in 3.2 so far. the 3.1 beta was a lot more polished that this. Are they pushing this out too early? Will they have a beta update to clean a bit up before going production? I hope so. I like the promised features, but this release is a bit bloated and clunky.