So I’m trying to merge two files. I scan both sides, lasso and delete extra point clouds at the ends with incomplete cloud points
to make the merge cleaner as I’ve been instructed. Use feature alignment, it looks great. Generate model and it’s way off. Why is this happening?
It don’t matching , because the software can’t recognize unique market points , try to use manual points and select the correct market points on each scan .
Feature merge is only for feature reach scans .
Why does the feature align, show them like perfectly lined up then fail to actually do it after though? That part just seems weird, the preview and outcome aren’t even in the same locations.
1 Like
To tell you honestly, no idea . But I know what can work or not with current feature.
Registration used in Revo Scan is still very simple but it need a good scan without symmetry .
Try to place manual points , if you can’t find it , neither can the software using feature option . 
What process should I be doing to merge 2? I’m struggling trying to get merges to work without a ton of rough surfaces after or clipping etc.
You need to go through cleaning process after merging and follow exactly what I told you early regarding fusing and meshing .
You need always clean the scans to avoid rough surfaces and artifacts.
Check the tutorial sections in the forum for more tips
Sorry I am just checking in for a moment , officially on holidays until next week.
But clean in what way? I know you’re just checking in briefly, but is there a video guide on a proper process with the current version or a similar version of Revoscan? I just would like to see a common step by step approach.
Did you preview the merge and then delete the edges? Generate Model will redo the alignment and it often fails if I’ve edited the components after previewing the alignment. One of the things I very much dislike.
1 Like
No I didn’t in that case. It just decides it’s going to go completely off track after a perfect preview.
Very weird, but I guess it at least highlights the issue that Generate Model and Preview the Alignment do not produce the same results and we have no control over whatever it is that’s happening differently.
1 Like
I have had the same issue with a part. even with manual point selection the preview looks perfect and then the end result is just all over the place. Later on with other files I did not have the issue. I believe it is from a lack of features in the part and also the part being small for the system (<50mm).
If you used manual points and you placed them perfectly then there should be no issues .
If you relay on feature mode only , there is never 100% that the final merge will be proper , especially on a very symmetrical objects. It is the same rule when you are scanning lack of features you are losing tracking , and have to switch to marker points .
So both algorithms here works the same way .
I’ve been having the same issue lately.
Doesn’t matter if I use feature or manual marker mode.
The preview shows perfect alignment - the generated model is offset.
Keeps happening a lot in the 5.5.4. version.
If the software performs second realignment while merging it’s just bad coding.
We work with the preview, we edit the marker points until the preview shows good alignment. When I click Generate Model I expect to get exactly the same alignment that I saw in the preview.
If the software messes up the alignment while creating the merged mesh - I have literally no way of fixing that.
DO NOT realign the point clouds while merging - keep the alignment from the preview.
Or at the very least give us an option to skip realignment during merging. Maybe in some cases it will result in worse quality merge, but at least we will have a merge.
The way it is now - I’m constantly getting scans that I have to merge in Cloud Compare because Revoscan just refuses to merge them properly 
1 Like
That’s what I do for a very long time , but hey on Monday I have other cases to discuss with dev.team so I will add it to the agenda as well . Thanks Filip !
Thanks.
It’s just that it used to work fine.
It didn’t cost you anything to check if the feature merging would align the scans automatically, and if it did, you could merge the scans right there inside of revoscan.
Now even if the preview shows that the alignment is perfect - most of the time after merging the two scans will be offset.
Sure CC does it better, but it was a handy feature to have, especially for quick scans 
1 Like
Same problem here with Revo Track 5.7.1.
I tried this part several times, setting the manual points in different locations each time, but it always produced the same misalignment.
1 Like
Exactly - beautiful example.
Very nice example @FB2210
Thanks for the video , I will forward it to the Dev team as well .
The issue was just reported to the Dev team so work in progress on this issue. Stay tuned !
1 Like
Hi @FB2210
The Dev team requested that you submit your project where you have the issue merging your scans and the video as well for the full documentation and attach it to the email since you will make appointment with them anyway , so a great opportunity to show them off your issue at the same time .
Thank you in advance!
1 Like