The good developers encapsulate their code segments with call's like QueryPerformanceCounter to catch these consumption peaks, so it should not be a big thing. It happens often then SC brings a new update out, that they run into this gui-input-lag trap. Perhaps they have fired their old development team. oeemm..![]()



clicked?

