Hi Paul, that does help. I didn't quite understand that it was a problem with all attempted booleans after a certain point.

This sounds like some kind of memory corruption problem due to some bug in the booleans. For the next beta I've added a type of "reset" when there is a failure in a command which should let the next command start with a fresh blank slate.

This will probably not stop the initial failure, but I think it should solve the problem of additional booleans not working.

But I can't really be sure though since I can't reproduce the bug. Please let me know if you run into this type of behavior again after the next beta and I will try something else...

Thanks,

- Michael