Hi Alan,

you wrote:
> However, one area where I find the workflow kind of difficult
> to get used to is the lack of layers. Will this functionality be
> added? (sorry if this has been mentioned before)

Yup, this is definitely an area that is going to get added for v2.

It looks like I will probably be focusing attention on it just after I get back from SIGGRAPH.

It's a pretty in-depth area that will involve a lot of UI work, so it will probably take a little while before it is complete, like it will probably stretch out over a couple of months and a few beta releases.

But it is definitely planned to be a major focus area for v2, I just haven't quite gotten started on it yet.

- Michael

Hi Kevin,

you wrote:
> Great stuff Michael. Some surfaces that wouldn't join or fillet
> using the previous V2 beta, now work fine.

Aside from just bug fixes for this beta Join has a new approach for its tolerance measurement, where for larger objects it will scale up the joining tolerance (the maximum distance that edges are allowed to be apart before they will be glued together) to be relative to the size of the object's bounding boxes.

That can help a lot with joining objects that are of a larger unit size.


> I'm really looking forward to seeing some layers and a
> construction/work plane in upcoming releases.

These will definitely be coming! I actually wanted to get a construction plane mechanism in for this release but I just did not manage to find enough time to squeeze it in yet.

- Michael

Hi Daniele,

you wrote:
> I've playing around with the new beta (the newest one) and
> unfortunately I've noticed a lot of weird behaviors in almost all
> the complex operations (boolean, trim, join, fillet, merge). I kept
> getting extra planar surfaces in the middle of fillets, missing
> patches when trying to join two surfaces, and in general, the
> sensation that the app is struggling more than usual in doing
> his calculations. Looks like the new library has got more bugs
> than expected.

Just wanted to double-check with you - all of this seems to have been related to a single bug, but which was in a function which was used pretty heavily by those complex operations.

Did the Aug-4 release correct all these problems? Or do you still have a sense that things are not right?

- Michael

Hi Michael,
yes, the new 4th August beta is working fine for me, so far. Although I haven't yet had the chance to intensively test it with a heavy modeling project, the "first time" bug still hasn't showed up. I assume that fixing that single bug pretty much fixed all those weird behaviours once and (hopefully) for all.
Thanks for the feedback, as always!
Cheers Daniele