The main problem is in sampler routine for identifying elements which is slow as a snail, and certainly the recent addition of visualizing the residual points made it even worse.

There is no good reason for this to be so slow, prime suspect are UI updates which are done too much.

The recently discovered Tracy Profiler is perfectly fit to investigate this.

Claude already made an analysis of the alignment process, we can build upon that to instruct Claude to add Tracy and instrument the code, see how far it gets.

Steps

• Claude: add tracy as GIT sub repository, as the vcpkg has a 1-year old version
• Add Tracy configuration based on Release
• Claude: recapture past analysis and based on that place Tracy instrumentation
• Claude: analyse capture and solve the shit

It is important to get a clear view before and after, that is also something that should be doable with Tracy.

We also need to make sure that we put "Frame" instrumentations on the 3D rendering in OpenCascade somewhere.

Instrumenting CTrack

Add Tracy as git submodule

Go to the root of the project, where the solution file is.

git submodule add https://github.com/wolfpld/tracy.git tracy
cd tracy
git checkout tags/v0.12.2

Open the folder C:\CTrack-software\Software\V5.0git\tracy\profiler.

Add a Release configuration to cmake, configure cmake and build.

Run  the profiler and pint the taskbar icon.

Build a release version of profiler

Side sorrows

Error reporting

The engine was not compiled, this triggered an error which was logged but not show in a dialog box because PrintError is used, which only makes sense on the engine

-> task for Claude

VC freezing up

Making the whole thing utterly un-useable.