![capturing reality texture subset of images capturing reality texture subset of images](https://ars.els-cdn.com/content/image/1-s2.0-S0010482516302153-gr2.jpg)
When you click on of the words, the appropriate tab opens up – but NOT necessarily with all the icons and commands you need! What is shown depends on what cell you have active! The active cell has a blue frame around it. They are named on top of it: Workflow, Alignment, Reconstruction and Scene. You will also need to jump between the various tabs of the application ribbon.
![capturing reality texture subset of images capturing reality texture subset of images](https://www.mdpi.com/remotesensing/remotesensing-12-02583/article_deploy/html/images/remotesensing-12-02583-g006.png)
If you hover the mouse over it, a pop-up will show “1 + 2 + 2 + 2 Layout”. You can switch to it by clicking the appropriate icon in the quick access bar (blue arrow). I usually use the one that has a “1Ds” view on the left and six more cells in two rows on the right. Also, you will need to change the layout to one with more cells. You can do this by clicking&holding the name tag and choosing “2Ds”. Unsurprisingly, this 3D view of your project is also still empty.ĭuring the workflow, it may be necessary to change the “1Ds” cell to previews of the images. The green circle shows the name of the other cell: “3D”. This cell details the structure of your project – currently, all is empty. The left cell says “1Ds” on top (yellow circle). The red arrow points at the tabbed(!) application ribbon that holds all the text or icon buttons you need to work the program,Īnd the yellow and green circles shop the name tags of the two cells this layout offers. the number and placement of screen parts or ‘cells’ as RC calls them, The blue arrow points at the quick access bar that allows altering the layout of the user interface, i.e. When you open RC you see something like this: If you are already familiar with it, you can jump down to the “Loading images” section.
#Capturing reality texture subset of images how to#
Let me begin with a quick overview of the user interface and how to adapt it to your purposes. There are several versions of RC I here assume you use a photogrammetry capable one without Command Line Interface (CLI). Additionally, it has by now acquired all the little gimmicks I need, such as automated detection of coded targets. MUCH FASTER! So much faster that it is worth all the bother. So why use RC at all? As mentioned, it is faster. Therefore, I often turn to Metashape in these cases, too.ĮDIT: this bug has been mostly fixed in the latest release! /Edit But that means investing the time for running the model again and again and again. Sometimes, removing a photo or two will help. One thing that also needs to be mentioned here is that RC has a very annoying bug: it will freeze and crash quite often when coloring a mesh, and sometimes also when calculating or texturing. In a certain sense, RC is fast but princess-and-the-pea, more prone not to calculate a good alignment, and Metashape is slow but extremely robust and reliable. If that fails, I typically toss my data into trusty old Metashape, which normally gives me a very good model. However, for my typical objects Reality Capture (RC) produces most models much faster and with a more comfortable workflow. Not because it is “better” in any overall sense – both programs have their strengths and weaknesses, and I am glad to have both available. Over the course of the last two years I have been using Metashape less and less, running most projects in Reality Capture. Basically, it is a sibling, even a twin to my tutorial on how to handle a project in Agisoft Metashape. Well, this is a long overdue post, and I could have saved myself a lot of emailing if I’d written it earlier.