Thanks for the update. I’m glad you got it working.
Our team really loves this feature, and we use it quite a bit.
One important “safety tip”: Importing small assets, such as a a single model or a couple of textures, is fine when in MUE mode. The change will propagate across the network. That said, this is NOT the right way to propagate a large import, such as adding a package from the Marketplace.
I did that without thinking a week or so ago – fortunately on an experimental branch of our project! – and the results were extremely bad. The team member who did the import had a UE editor crash as the data was propagating across the MUE server. When we restored, it was a complete mess with some of the import journaled on the MUE server, some not.
We recovered by reverting the branch to a previous changeset in SCM, and deleting that MUE session from the server and creating a fresh one.
I don’t blame Unreal for this – if I hadn’t been in a hurry, I knew better than to suggest she import this during MUE mode.
The CORRECT way to do this would be for one person to do the import and push the changeset to source control, outside of MUE, and then have other team members update their workspaces to that changeset before everyone goes into MUE.