I had an interesting time with this scan, and, I may be wrong but I’m getting the impression you can have too much scan data when it comes to merging scans.
My first attempt was to scan the slipper in several positions using the turn table, but after 4 scans which ensured all of the slipper had been captured, the merged scans seemed to had an offset in places, about 3mm which was causing me an issue as I wanted to do all the processing in RevoScan, when meshed it gave me a strange kind of bubbly overlay.
This was present on multiple parts of the model and made it incredibly messy. It looks like its caused by the software trying is best to create what it thinks is 2 outside surface. No amount of smoothing or simplification helped, it just removed detail.
My next decision was to manually scan the slipper, and effectively collect less data to merge due to being able to cover more area per scan, and to target those areas specifically.
This issue didn’t go away, but it was considerably better this time. leaving only 3 specific areas of the slipper with slight overlay.
My solution was to trim the pointclouds before merging, but leave enough of a % overlap that it would still process automatically.
You can see the areas with straight edges are where the pc’s were trimmed
And overlaid onto my base scan
I’m sure there are many ways to get the same results and feel free to discuss them here, I just wanted to show how I improved the results by really looking at where I was having the issue.
Best results before trimming:
Results after trimming 
