Thanks, I did zero all the morphs on the model and that really helped - got rid of over 100 dependencies! The trouble is that the scene contains a lot of presets which get loaded on various buttons, I did resave all of those without saving morphs and then managed to build a scene with a lot less dependencies that appeared to mainly work. Loading into a clean VaM (Well, just by moving aside my own AddOnPackages) showed up a couple of small bugs so I fixed those, resaved it in the clean version then cleaned it again, reloaded it from the hub and it seemed to work OK.
The problem appears to have arrived when I've continued then developing on top of the zero morphed version. Then it's just added so many dependencies in somehow that I just can't weedle them all out, most of them I can't even tell where they are coming from and I have had to revert back to the version from just after I zeroed all the morphs.
So I guess perhaps, zeroing the morphs and then carrying on adding stuff might break it as it now includes stuff that it thinks it has the morphs for and doesn't and goes searching through the entire hub for them maybe.
In future, I'm going to stick to smaller scenes that are less complex, rather than buttons for the different positions etc I'm gonna break it up into separate scenes, which is a shame to be honest as it's nice to have everything all together but this dependency nightmare makes developing it very difficult when if you try something out whilst developing, then change your mind, it seems to leave half the setup in there and create a ton of dependencies.
I'm learning as I go along with this but for this particular scene, I've got it to a stable point where as far as I can tell it's loading properly for everyone so am gonna stick with that for now and move on again.
It would be nice if there was a better way to handle this dependency nightmare though. I seem to have got the hang of the licensing now so maybe in time with more experience and better development practices, I will get the hang of this.
