Canon R5C + RF24-105@24 - lens recognition error

General Feedback & Requests
1

Hi there,

I’m using a Canon R5C + RF24-105@24mm to capture assets. (Yes, poor me…)
I develop my raw images with DXO Photolab 7.15. and export them as jpgs.
When I import these images to RealityCapture/RealityScan, the program recognizes it as a 32.1mm lens. This alone itself this wouldn’t be a problem, but when aligning the images, the program can’t comprehend that it’s not a 32.1mm lens and totally messes up the alignment, and the texturing as well.
I tried several methods (All EXIF data, no EXIF data, when exporting, no optical adjustments, optical adjustments, all the distortion models, all combinations of settings when aligning…) and still no solution. I’m using RC/RS for years now and I did not have any issues with other camera/lens combinations. Any suggestions or recommendations?
Many thanks in advance.
Akos

2

Hello Akos,
I am checking the camera in the database and it looks like it isn’t there. Do you see the yellow triangle in 1Ds view after image import?
In general, RealityScan stores the focal length w.r.t. 35mm file format, so the value can be different to the expected one. In your case, as this is full frame sensor, it should be the same.
Have you tried to set the value in Prior calibration/Focal length before alignment
image
and set the prior as fixed?

1 Like
3

Hi Ondrej,
Many thanks for your tip/answer. We already tried this without any success. But I found a workaround.
For some reason, the DXO export doesn’t get recognized, no matter the method we export the jpg. Distorsion on/off, with/without EXIF data.
However, if we export the files with Lightroom, RealityScan still doesn’t recognize it, but at least it doesn’t recognize it as something else, just as an unknown format. So we can enter the focal length manually, and no we the alignment works perfectly.
Please if you can include this camera in your next update, please do so. We really hate Lightroom, and like to avoid it as much a possible.
Many thanks,
Ákos

4

Hi, thank you for sharing your workaround.
Can you try, if that works for you now? The camera was added to the database.