Fixed "master camera" in multi-view capture (fixing the world coordinate system)

Development Asset Creation
, ,
1

Hi,

I am doing 3D reconstruction of objects captured in a multi-camera setup ( ~50 cameras). I would like to set the world coordinate system so that one of the cameras is at [0, 0, 0], so that it’s convenient to process this data elsewhere.

I tried setting the pose of one of the cameras to “Locked” as follows:

image

However, this makes RC crash during alignment. Any suggestions on how I could do this?

image

2

Hi luiz_gustavo_h,
is this also happening after application reset (open RealityCapture with pushed SHIFT and choose the option Make it like a clean install)?
Do the images have some kind of coordinates after import? Are other images set as Unknown in Prior pose?
What are your alignment settings?
Are you sure using those Yaw/Pitch/Roll values? Are they refer to the reality?

3

Hello @OndrejTrhan ,

is this also happening after application reset (open RealityCapture with pushed SHIFT and choose the option Make it like a clean install)?

Yes, I did a clean install, and this issue persists.

Do the images have some kind of coordinates after import? Are other images set as Unknown in Prior pose?

All images have “unknown” prior pose (except the one I am manually changing)

What are your alignment settings?

I am using default settings after a fresh install.

Are you sure using those Yaw/Pitch/Roll values? Are they refer to the reality?

Everything is relative to some defined world coordinate system. What I would like to do is to build this coordinate system such that one of the cameras is at the center. If there’s a better way to do it, please let me know!

4

@OndrejTrhan - I got a workaround working.

  • Set the prior pose to “Position and orientation”. Run alignment. The registered pose for that camera will be close, but not exactly at 0,0,0
  • Set the prior pose to “Locked” and re-run (or “update”)

It’s unfortunate the it doesn’t work out of the box, but at least I have a workaround

5

Hi, I was able to reproduce it (for me it happened if no first images in 1Ds view was selected) and I created a bug for it.
Thank you for noticing and I am sorry for your inconveniences.