Xavier Sorry to hear your speed issues are even worse than mine. I got a fast device mainly to reduce lag with Therion and opening the exported pdfs. Not so much because Therion was slow but because it is where I spend my most precious discretionary screen time. Other than the start-lag issue, comparison of my old and new therion.log files showed a typically 2 – 5 times speed increase.
For me there is a 6 seconds lag to open the cmd window, but also a 6 seconds lag at the end when the cmd window is closed and Xtherion reads the output to display it in its interface.
At least I only have the lag at the start of the process. The transition from cmd window to XTherion for me is instantaneous. Although I recall on rare occasions an inordinately long end-lag, probably back with Windows 10. Maybe the content of the project that has just been compiled impacts on that?
However, my main problem is the huge delay (which can be of several minutes) for xtherion to display a large th2 file : it takes 75 seconds to display a th2 of 2500 lines of text (that is 538 commands). During that time, xtherion says "Processing commands ..."
That is a disaster. I just checked a 3500 line th2 file, the largest I could quickly find. It takes 6 s to complete the entire opening process (‘opening image’ - which are 5 large PocketTopo xvi files and ‘processing commands’). Moving an object to another scrap is about 1-2 s. So broadly, except maybe in Yann’s case, is it that Windows 11 has added delays (more, or less, extreme depending on user) to Therion that were not present with Windows 10? I have always thought of Therion as placing minimal load on a device. Has anyone come up with minimum, recommended and optimum processor, graphics and ram parameters (other than more is better)? Bruce