TowerPower Thanks a lot for these error reports. I could reproduce most of them.
For your information: Revit has quite good events we receive when you change the model, but we must request the data for the whole model and skip everything we don't want. That makes it slow. SketchUp on the other hand, has very poor events, but we can request the data we need directly, so it's fast.
There are a lot of cases in SketchUp in which we have to guess what happened after we get notified about a change - or ask for more information in some obscure way.
Take the cutting components, for example:
We get notified when you place such an instance, but we don't get notified about the cutted face. This we have to handle ourselves, which might be possible. Likewise when you move the instance or delete it. When using the "Unglue" command in the context menu, we don't get notified about any change, which is really bad.
Undo/Redo events are even worse in general. Like when undoing a component drop, there is no event removing the instance, only removing the component definition. But we should be able to handle this. You can delete it and then purge the model.
Similarly, sometimes when you modify the geometry of a face, it will suddenly dissapear in Enscape and turn black.
This is the only bug I was not able to reproduce. It would help a lot if you provide more detailed steps to reproduce the behavior.
Considering the quality of the events we receive from SketchUp, Enscape will never be able to show the model 100% accurate, only by reacting to the events. Do you have any idea for a workaround? Right now you can click the start button again to reload the model (no need to close Enscape first). We might be able to add a "reload geometry" button, that does not reload any textures (which can take a long time). Not a fan of it, though. Perhaps you have a better idea.