RC 1.3.1 FEEDBACK AFTER 1 MONTH

General Feedback & Requests
,
1

Hi RC team,

We re professional, working for VFX & concept art cinema industry since 20 years +, full Epic, full Unreal, full RC since a long time.
This subject is to give my feedback after 1 month of work on the last update patched.
I am on PPI + CLI license
on different Machines i9 128Go RTX 3090 and 4090

So no specific hardware or software version.
This feedback is the result on all config/version tested and it will be the same.

Project with photos only, DSLR + Drone - no Lidar.
Tested on subject from 40 to 1000+ stills

  1. The most important : Alignment Works definitely less well than 1.2.2 Tarasque version.
    Let’s be clear, same images processed on both versions.
    The result talks by itself, the alignment became nightmare on last version. we have to put control point nearly on every picture + and at the end the result is bad on hi Detail… more holes, more misalignments offset.
    doing photogrammetry since 2013, I never had that at this level.

So yes, it process quicker
yes, when it works, result is good
But it s so much more work. On Tarasque, on 2 pictures with 3 control point, 90% of the time, its solved. on last one, definitely not.
We loosed nearly a week before to partly get back on 1.2.2.116899.

I saw a topic with guys changing the parameters to help the software to work (pre selector features, disto mode, etc. …).
I don t want to go there. if it s working better on 1.2.2, then RC has a problem and the community should be alerted quickly.

  1. after defining the reconstruction box. where in normal mode we got it complete, in high detail, mesh is partly missing, not solved …

  2. This is not normal to have a download area of the previous version on the account area. Thx to have my own backups.

I finish to use my PPI credits to deploy more process to get back in time on 1.2.2 for the time we have lost it should have been 2 weeks of process.

I don’t know if some fellows of the community have similar experience.
If that’s the case, please urgent to give the feedback, that’s definitely not where we want RC to go.
I Prefer 1 version over pre tested than this kind of release + patch … no way !!

Cordialy,

2

Hello, and thank you for your honest feedback. We’re sorry to hear about your issues with RC 1.3.1.

Would you be willing to share the images and steps to reproduce the issue with us so we can determine why this is happening? We test on various datasets before every single release, but of course, it is possible to produce worse results on specific datasets.

If you are willing to share, please reach out to our support through our contacts from here:

https://www.capturingreality.com/technical-inquiry

With the data and steps for reproducing the bad results, our support agents will prepare reports for our developers so they can adjust the calculations.

Thank you!

3

Hi RC Team, and Thanks Jakub for your feedback.

We re still in the middle of our project so hard time for being available to manage the datas and talks about it (full Lidar Sat datas + RC + Unreal). It should take us to end Feb.
But I will definitely come back to you to share some pictures collection and share files so we can figure out what is happening there.
I gonna get in contact to your link, and prepare a share area.

and lets ber clear, We Love RC !

Sincerely,

4

Of course, I totally understand. We mean it, so we’re here when you get to chance the share the data with us.

In the meantime, I wish you good luck with your projects and with your deadlines. Good luck!