This may not be a bug in the strict sense of the software not working, but rather a badly implemented feature:
RC consistently (in ca. 70% of cases) auto-creates a reconstruction region that is very badly sized. Sometimes, it is simply huge and leads to very long unnecessary creation of undesired trace elements in the background.
WORSE: it often cuts of one or more small part of the object! This despite OBVIOUS continuity of the sparse cloud and an OBVIOUS drop in density beyond the object.
Example screenshot here: https://dinosaurpalaeogerman.files.wordpress.com/2018/11/why.jpg
As a consequence, the START button is useless: I need to check the region before model creation, as otherwise only a partial model is created.
PLEASE FIX!
nothing fixed! That is a workaround that causes its own issues. For one thing, it causes massive unnecessary computing time to create all the background ■■■■ around the object.
EDIT:
thank you for your condescending post that shows you have not properly read my opening post.
the key here is that no or a bad reconstruction region make the START button useless, as my MANUAL interference after alignment is required to achieve a useful model.
MY MANUAL INTERFERENCE!
which is EXACTLY what I could skip, as the START button (you may know this already?) allows me to run through a workflow.
Sorry, Jasper, I have little patience with people who write long condescending posts without bothering to read the OP. I don’t INTEND to be rude to you, and I do feel your tone was rude: assuming I am an idiot because you didn’t read or didn’t think.
I edited my initial post (and hope you responded to that) as it indeed was written in a very rough tone - sorry.
Now, again, you lecture me on things I obviously know, and make wide-ranging assumption that are not warranted:
“If you read what the “Start” button does; “Create a complete 3D reconstruction with texture or vertex colors using all inputs.” … meaning that it goes through all the workflow steps. This is helpful for specific projects such as close ranged scanning rigs. From what I gathered this is not relevant to a statue project which you are doing.”
Yes, I HAVE read what it does. Yes, I KNOW it goes “through all steps”. And NO, it doesn’t mean that it is intended to be helpful for “specific projects”. Also, I gave a fictitious example to make a point; don’t jump to conclusions.
The key thing is the same as posted in the very first post: if the recon region would not usually cut of a tiny part of the OBVIOUS continuously dense sparse cloud, the START button would be much more helpful. Nothing you write addresses this issue.
For your sake, you should change your fanboy attitude - you are not helping making RC, a great software, that tiny bit better that makes it a software that is a joy to use.
oh, and did you actually LOOK AT the screenshot I linked?
Do you even UNDERSTAND the issue I am talking about?
Did you NOTICE that my typical projects obviously do not involve a statue?
Hello, please follow our code of conduct: https://support.capturingreality.com/hc/en-us/community/posts/115000790911-Code-Of-Conduct
@Mallison: could you please provide us with a sample reconstructed RC project, where you are experiencing the behaviour described in your initial post, for inspection? you can use our contact form for this purpose: https://www.capturingreality.com/Contact
