What happens is that OBMM keeps track of the fact that the resource is owned by all the omods, and will not remove the resource until you have uninstalled all those omods. The difference from BAIN is that BAIN also keeps track of whether you uninstalled the one that you overwrote the other resources with, and if so revert to the older version, while OBMM only knows that the resource is shared and therefore keeps the last installed version.
(...)
I'm also happy to correct the (common?) misconception stated by ulrim, that OBMM will remove shared resources if you uninstall one of several omods that use the resources
(...)
I'm also happy to correct the (common?) misconception stated by ulrim, that OBMM will remove shared resources if you uninstall one of several omods that use the resources
If the resource is a mesh that points to a non-shared texture resource installed by a different OMOD (as in the case of the example combination of mods) the shared mesh is not updated.
This is not a misconception. Without management of the shared mesh resource (shared resources are kept by the last installed version, only.) the mesh appears and the game shows a pink texture on the mesh.
Don't misunderstand please, OBMM complements Wrye Bash very well.
No problem with WarCry though, even better now that it's packed into a BSA. :tops: