Define distance: ill-conditioned constraint

Development Asset Creation
,
1

Hi,

I have a problem setting up a scale-bar to scale my model. Independently of what i try, it returns: Define distance: ill-conditioned constraint.

I’ve had this issue once before and clearing the cache worked, as described in one of the reference issues linked below. However, this time it didn’t work and i’m trying to figure out what is causing this issue.

Workflow;

  1. Place two control points in the scene with known linear distance (5.0m).

  2. Each control point was placed in at least 10 different images (see screenshot below).

  3. Draw a line between these two points and set distance to 5.0 (m).

  4. Due to the photographs being taken with the Phantom 4 Pro, which measures height from take-off point and has a low accuracy GPS;

4.1 Set camera priors to “OFF”.

4.2 Select all cameras and “Prior Pose” to “Unknown”.

A number of ground control points are present in the scene which were measured with RTK (Trimble Catalyst).

 

Unfortunately after all this i continue to get 'Define distance: ill-conditioned constraint’ and i have no idea why. Is this a bug in RC or am i doing something wrong? 

P.S I had a look at the logs in %tmp% but couldn’t find any error messages.

Reference issues:

Issue 1

Issue 2

2

Hello dear user,
so when does this 'Define distance: ill-conditioned constraint’ message exactly show? After which procedure? After using define distance between two control points, you should hit “Update”. Have you done that? 

3

Hi Erik, yes i’ve done that. I’ve also tried aligning everything again without luck. The message appears as soon as i add the " Define Distance"  measurements.  

4

I can send you all data if you woud like to reproduce it. 

5

Yeah that would possibly be leading to some sort of a solution. But I need all of the photos and project files. Also shortly describe what exactly your goal is in a readme.txt file next to the files.

6

Sure, will send those. I just noticed this in the web-render: 

 

Those are the scale-bar tie points, might that be related? It looks like they are projected to 0,0,0 & that causes some conflict in reality capture. Apparently RC doesn’t georeference the tie points on the model, even though the scales are correct.  

7

Here is the link: https://fil.email/X5d8n8tH , contains all data and project files.