Hardware Optimisation & Benchmarking Shenanigans

Hello Ivan,

Thanks for your continued efforts. Though I’m past learning anything new in comparing performance in my previous and upgraded system specs, I saw utility in using the benchmark to isolate against a particularly vexing issue I’m encountering in the Promo version, described here, wherein I’m a) able to align a set of 500 images with default settings, and b) unable to reconstruct the component, always crashing RC with “invalid function call” red flag of death. I wanted to see how the Demo version might behave. Note, I had uninstalled Promo and reinstalled, as well as cleared cache and Shift-hold opened RC Promo to reset settings, so that’s about as tabula rasa as you can go, though I’ll say I suspect settings were not reset, as I saw my assigned cache drive letter hadn’t changed. This goes off topic, so back to this thread, but thought it useful to provide context, to possibly understand the strange results I got in your benchmark.

It took me a few steps to get everything working, not sure why it downloaded the Demo version over Steam this time, used the same installer I had saved to my downloads folder as used previously. Every time I’d launch benchmark.bat with no indication that Steam was doing something, I’d get the txt file open with nothing moving forward, had to hunt around to finally get Steam to load everything and ready RC Demo.

Once I got benchmark.bat to open RC Demo and step through the workflow, I kept an eye on alignment, reconstruction, especially when it came to comparing depth maps, as this is always where I’ve run into problems leading to the invalid function call issue. Interestingly, RC Demo was able to get through depth maps to then reconstruct all the parts, though I missed the show that followed, as that took place in the wee hours. I awakened to RC closed, isn’t that different from before, thought I remembered seeing the finished model, maybe not. Here’s the results.txt which shows echo is off. (Why?)

I surely don’t need to derail this thread with a discussion so overly specific to my issues, which I suspect relate to the combination of something generated by RC (a bug?) and only manifesting during work in RC, but operating at the system level, since reinstalling Promo and running Demo also present problematic behavior, though not identical. That said, I do believe my sharing this with you might trip your understanding of what possible culprits belong on the table, am all ears what you make of this news and possible suggestions moving forward. I’ll then move along, take what I learn back to the other thread with Kevin Cain and Götz Echtenacher.

Again, many thanks for this project.