Hi all,
new feature "Sensor refresh rate is adjustable now" of version 0.7.7 causes a problem in case of
Date , GPU Core Clock [MHz] , ...
2014-02-16 14:32:05 , 378.9 , ...
2014-02-16 14:32:05 , 378.9 , ...
2014-02-16 14:32:05 , 378.9 , ...
So, we have ambiguous time informatin within any second and tools which handle such log-files show strange diagrams with e.g. vertical lines (like my LogViewer, see http://www.techpowerup.com/forums/threads/logviewer-for-gpu-z-available.185299).
Solution: please add milliseconds to log-time to solve this problem:
Date , GPU Core Clock [MHz] , ...
2014-02-16 14:32:05.123 , 378.9 , ...
2014-02-16 14:32:05.456 , 378.9 , ...
2014-02-16 14:32:05.678 , 378.9 , ...
Hope you can include this in next version of GPU-Z !
new feature "Sensor refresh rate is adjustable now" of version 0.7.7 causes a problem in case of
- "Log to file" is switched on and
- "Sensor refresh rate" is defined < 1s
Date , GPU Core Clock [MHz] , ...
2014-02-16 14:32:05 , 378.9 , ...
2014-02-16 14:32:05 , 378.9 , ...
2014-02-16 14:32:05 , 378.9 , ...
So, we have ambiguous time informatin within any second and tools which handle such log-files show strange diagrams with e.g. vertical lines (like my LogViewer, see http://www.techpowerup.com/forums/threads/logviewer-for-gpu-z-available.185299).
Solution: please add milliseconds to log-time to solve this problem:
Date , GPU Core Clock [MHz] , ...
2014-02-16 14:32:05.123 , 378.9 , ...
2014-02-16 14:32:05.456 , 378.9 , ...
2014-02-16 14:32:05.678 , 378.9 , ...
Hope you can include this in next version of GPU-Z !