Agisoft Metashape
Agisoft Metashape => General => Topic started by: nomino on April 07, 2015, 12:53:46 PM
-
What do the fields embedded in the tag <regoin> </region> refer to?
Are the coordinates of the 3d .obj defined in the region space? Should I therefore translate the 3d coordinates according to it?
Who can help me?
Thank you in advance.
-
I think this is for the region box? (The box you define to tell where Photoscan will build the Dense Cloud and Mesh.)
-
Therefore the exported coordinates in the .obj file are already in the world frame coordinates, right?
Because I am trying to project the 3D mesh in a corresponding input image of the model using the P = K[R|t] matrix extracted from the camera .xml file but it doesn't project the coordinates correctly.
I've tried to do this test with the data of the doll of the first tutorial...
I even notice that the Q = [R | t] matrices from the photoscan camera .xml and phi kappa omega .txt are different...
Is there a bug in Photoscan or I am missing something?
-
Can't you export the scene to FBX? I think that includes the cameras as well (I don't have Maya or Max so I cannot check).
-
Yes the FBX export includes the camera positions (Unity is free (non-commercial) now)
-
You can use also Blender for import an FBX file.
-
I give a look at the parameters in the fbx file, the coordinates ot the points of the 3D mesh are the same as in the .obj file, the translation vector also, but the not rotation matrix (or better the angles that define the rotation matrix).
No one ever tried to project a computed 3d mesh into the original frames?
-
Hi nomino,
Have you found a solution to your problem? I also try to project the model into the original camera image. Haven't managed yet. Can you help me?