Have ASUS Zephyrus maxed out with 64GB RAM and RTX5090 and found that when I would try to switch from Crossed Line Scan to a SingleLine the program render screen would lock up and no renders would be capturerd. Program would crash also at times. This happens on either a swapping of modes during a scan and or when starting a new scan and switching to single line.
SOLUTION SO FAR:
HAD TO STOP GPU ACCELERATION in Trackit settings: PREFFERENCES - GENERAL and go from GPU Acceleration to CPU Acceleration.
This seem to have worked so far, no crashes and can swap in the middle of a scan or start off with single line scan now.
I think this is one of those things where the software just isn’t catching the state change properly. Newer GPUs (especially the 50-series) might be a bit more sensitive when the render pipeline is still active. I’ve run into similar quirks in other scan tools - if the render thread doesn’t fully clear before the next mode starts, you end up with a frozen screen or straight-up crash. Pausing first basically forces a clean reset, which is why it feels more stable
Would be nice if the devs added some kind of safeguard, like an automatic pause or buffer flush when switching modes. That way you wouldn’t have to remember the extra step every time. Until then, yeah- pausing before the switch seems to be the safest workflow
I was having trouble even trying to start in single line mode. Amd I was pausing before switching modes but was not waiting more than about 5-10 seconds before trying to unpause. Might try a longer pause to see if it works but like I said I was having the freeze up on a new project just trying to start a scan in single line mode. Was freezeing then also. Working with revopoint and will be sending them a video of what happens. They have my log reports also and are quickly trying to resolve. Unfortunately this is not my primary job so I have limited times to get back with them as I travel for work. Trackit is a little to big to take with me through the airport.