Hi Kevin, I'll try to answer as precisely as I can.
Firstly, wow, your setup file is really amazing. We really love when users are pushing the limits of the software.
And you are. Bravo.
However, looking at your sample project, I don't really think it is suitable for calibration in the first place.
The building consists of 4 different parallel planes, if I had to map it, I would NOT calibrate through 3d object,
I'd go the old classical way.
The calibration is more suitable for 3d objects that really have a lot volumetric complexities, seen from an angle
where there's a minimum of Z depth. You've noticed that when there's not enough depth, the calibration algo will give a lot of error.
That's normal and that's the main issue with calibration algos.
However is sorta DOES work for your projects, so let's assume that.
1. There's a "show video cursor" that will just does that, and you can adjust the crossair amount. We could add a preference to make the points bigger tho'. They are fixed size, so I assume if you output at 4k they will be much smaller that at 1080p.
2. As I said before, for the calibration process to work you need quite a bit of Z depth, however a flat facade doesn't have enough depth. That's a limitation, all the more as you're cropping smaller bits of the facade, for even less depth.
If you want to understand how it works under the hood, have a look here:
https://docs.opencv.org/4.x/d9/d0c/grou ... 63b5af1d7b
https://docs.opencv.org/4.x/d5/d1f/cali ... vePnP.html
3. Internal loops are just a render, so they should not kill your computer'performance. For 3 4k outputs (splitted by FX4), I'd go on a big PC sporting a 4090. Haven't tested the MacStudio ultra, it should handle ProRes really well. If you're using HAP, you could try on a PC4090 to see the difference in performance.
Hope this helps,
frZ