Obj export from RealiyScan slightly rotated?

Hello,

I have noticed a difference when exporting .obj files between Reality Capture 1.5.1
and RealityScan 2.0.1.

When I export a model and then load it into blender, the reality scan model looks to be slightly rotated on
the Y-axis about 13 degrees.

Here is an example image for reality scan:

Here is an example image for reality capture:

Has the default export settings change in RealityScan?
Is that an expected behavior? Is there a way to change it back to how RealityCapture exported the model?
It looks to me, like the RealityCapture export is align to the z and x axis and the RealiytScan export is not.

The example data is from the Gingerbread cookie example data set.

kind regards,
Brian

Hello Brian,
the mentioned dataset doesn’t have georeferenced information or XMP data. That means, that each alignment and therefore model orientation will be slightly different (even in the same version).
Have you used the same project in 1.5.1 and 2.0.1 version or have you created a new project in each version? Or have you used XMP workflow, component workflow or GCP workflow between the versions?

If not, a slight difference in orientation or position is expected.

Hello Ondrej,

thank for the clarification.

Have you used the same project in 1.5.1 and 2.0.1 version or have you created a new project

I have created a new project in each version.

I did not used XMP workflow, what i did was just:

  1. Align
  2. mesh model
  3. export obj

I am not sure what component workflow is, how could that be helpful in this case?

With GCP workflow you mean using ground control points, right? Can I expect that the exported obj output is the same when using markers in the scene? Even with RealiytCapture 1.5.1 and RealityScan?

thank you for your help!

kind regards,

Brian

Component workflow could be helpful, but you need to create the component in one version, export it and open in the other version. So, I suppose it is not ideal for your case.

Yes, I meant ground control points. It will be the same when you’ll use the same GCPs with the same coordinates.