Not sure if the Boolean subtraction method of selecting 2 layers and hiding one mesh on a layer to subtract (merge) from the other layers mesh is disabled, but I cannot seem to get it to work.
It has nothing to do with layers. Make sure you are in the scene menu, hide the object you want to use as a cutting tool, select cutter and cuttee and then do a voxel merge.
1 Like
You need give more details for ācannot seem to get it to workā.
Note that boolean only works with voxel remesher, but not āsimple mergeā.
1 Like
I noticed a behaviour change that might be the issueā¦ if I have 2 objects selected (not grouped in hierarchy) when I try to hide the object that I want to act as Boolean both selected objects are hidden. Have to hide object before selecting it, Iām sure this wasnāt the case before?
(Only tested in web demo as I left iPad at work)
Thatās a behavior change thatās all, but it only impacts UX.
It seems a bit more fiddly now having to [ deselect/hide/select/voxel merge ] rather than [ select/hide/voxel merge ] this behaviour doesnāt happen when in hierarchy, just seems a bit odd is all but if itās by design I guess weāll just have to relearn the nuances 
Itās temporary Iām experimenting.
Also you certainly donāt have to [deselect/hide/select/voxel merge].
You can simply drag the finger on the eye or simply long press.
But Iām changing the behaviour so that long press sync the visibility of the selection instead.
I donāt know yet what Iāll opt for.
I donāt care much about optimising for the boolean thing.
What I have in mind is toggling off the visibility of a group more easily.
2 Likes
cool, the long press is really useful, didnāt know about that. Ideally there would be a Live Boolean system like Zbrush where changes could be made to objects in play with a real time approximation of the result before being committed/validated but I guess that is a project for another timeā¦ donāt want to distract you from current features 
Behaviour change is really good and will make work with complex scenes much more easy.
Just hide before select.
I changed it already (on the web demo).
Iām still unsure what is the best way.
Basically the āsync the visibility of the selectionā is a nice default when you just selected a group and want to toggle visibility on/off.
But it can be annoying if you are in the ābooleanā workflow.
Also not sure if having a different behaviour between item that are selected and items that are not is a good idea.
In any case, long press will always be there for the alternative (as well as the drag-select).
1 Like
I see.
There are different approaches to work with selections and active object. In Webdemo, you already adopted most of my favourites, thank you so much! ! 
Me, I like the āexecute everything to selectionā
Delete all selected at once? Yes all please, but maybe ask first once ? Bullshit. Undo is faster than confirming every time! We are professionals , arenāt we? In one app the user is asked once after restarting the app and deleting first time and one can check a tick if he donāt want to be asked again till restart - with this āI am professionalā hint 
Hide all at once? Sure! If I want to hide single object of selection, I can long press, or hide before selecting. (But itās fine like it is now. Just a bit more consistent to act always same. But this starting to be picky personal taste)
Rename selected? Yep, all same name please, letās give it numerical suffix right away according to appearance order in scene menu from top - down.
Clone, instance, changing materialā¦ā¦.everything already pure pleasure!
Thank you so much!
I added a checkbox in Debug menu to switch the behaviour.
Iāll probably remove the checkbox once I decide.
2 Likes
Omg, thank you! I couldnāt figure this out for the life of me. Sheeeesh