LogViewer for GPU-Z available !

[Solaris17]

I can tell you a trick to force that:

1. Select „Number of files = 2“
2. Select „Number of files = 1“

This does exactly what I want TY.

Another (maybe better) UI solution could be instead of hiding the „+“ button in case of three categories are shown, to change it to a „-“ button. So, the number of categories go like:
1 -> 2 -> 3 -> 2 -> 1 -> 2 > 3 -> 2 -> 1 ...

This is also a good idea, its more intuitive.

 

[TomWoB]

Any chance you could add the ability to save images of the graphs? Thanks.

Hi Ryrynz,
one request and one like ... OK, I will think about it . Shouldn't be a lot of work to implement ...

 

[TomWoB]

New version 5.1 available !

Hi all, I built a version 5.1 with the following new features:

• Save Screenshot:
  ability to save a screenshot of the GenericLogViewer window directly in one of the following graphic formats:
  - PNG
  - JPEG
  - TIFF
  - Bitmap
  
  
• Feature "different categories of one file in one diagram" now also has a "-" button

Special thanks to @Solaris17, @Ryrynz and @Naki for beta testing

Download
The zip file (SHA-1 hash, Version 5.1: 3F00587F9019A8215BABDC8A55BE8264D60D7A9E) contains the binary files of the tool.

 

[Ryrynz]

Beautiful.

 

[TomWoB]

New Version 5.2 available !

Hi all, I built a version 5.2 with the following new feature:

• ability to save the current setup
• ability to load a previous saved setup

After loading a logfile, the two new buttons are shown. They allow to save/load your parameters of the GenericLogViewer like:

• number of diagrams
• diagram types
• selected categories
• ...

Only logfile specific parameters are not saved, like filenames, time windows (makes no sense).

Remark:
depending on the "complexity" of the setup (6x2 diagrams, each with 3 categories, ...) it can take "some seconds" until setup is activated ... stay cool

Best regards
Tom

Download:
you can download version 5.2 from first post of this thread: Post #1

 

[vexxiss]

Great Tool. Small feature request: is it possible to add the ability to change the timeline from 00:20:20 to the actual time (14:40:20...)?

 

[TomWoB]

Hi vexxiss,

a long time ago I decided to use only "relative times" instead of "absolute times", because comparing multiple log-files makes only sense with relative times. There are two use cases for that:

• comparing 2 or 3 different log-files
  I think that use case is clear. Maybe you have to optimize the duration of the shown periods in "Edit" window
  
  
• open a single log-file multiple times
  Maybe this is not a well-known use case. Simple example: you have a 3 hour log-file and want to compare hour-by-hour. So, you open this 3 hour log-file 3 times (file 1, 2, 3). Now you select in "Edit" mode for file 1 first hour, for file 2 second hour and for file 3 last hour. In the diagrams you can see now first hour = red curve, second hour = green curve and last hour = blue curve

Both use cases are only possible with "relative times". But I agree, in case of "only a single file" absolute times make sense. But to keep tool simple I decided to support only "relative times". I'm sorry, it will be "a lot of work" to change this and it means, I have to support both (relative and absolute times). So, at the moment it's not an option for me.

Regards
Tom

 

[Polarguin]

Very useful tool!!!
Could you make "1% Low" value displayed ?
And "0.1% Low"

 

[TomWoB]

Hi Polarguin,

sorry, I don't really understand what you want:

• should the tool mark "1% Low" values in a special way?
• should the tool show only "1% Low" values (maximum Y-axis) ?

Maybe you have a look at the "Statistic" mode: it shows how the values are distributed (in percent). With "number of ranges" you can adjust the "width" of the ranges.

 

[MrGRiMv25]

Really nice idea, it's one of those ideas you always wonder why it hadn't already been done! Props.

Hi Polarguin,

sorry, I don't really understand what you want:

• should the tool mark "1% Low" values in a special way?
• should the tool show only "1% Low" values (maximum Y-axis) ?

Maybe you have a look at the "Statistic" mode: it shows how the values are distributed (in percent). With "number of ranges" you can adjust the "width" of the ranges.

I think he means the FPS 1 and .1% lows? I might be wrong but that's what popped in to my mind from reading his post.

 

[TomWoB]

Hi MrGRiMv25,

I think you are right regarding your "FPS 1% and 0.1% lows" assumption. I found a video which explains it: YouTube 1% & 0.1% lows
@Polarguin: OK, I will think about an implementation ...

Regards
Tom

 

[TomWoB]

Hi all,

OK, I did some thoughts and some tests!

The Thoughts
I don't think I have the perfect data to calculate "1% Low" and "0.1% Low" values properly, because in the logs are typically not the needed exact duration times between all frames stored, there are FPS values at "logging interval time" written. So if I calculate "1% Low" and "0.1% Low" with these FPS values I think it's not guaranteed to "consider all lowest values".

The Tests
I logged a Formula 1 Benchmark (3 rounds in Monaco) with two different logging intervals (100ms and 1000ms) with HWINFO + FRAPS. Which delivers the following result:

• red curve = 100ms logging interval (in real 180ms) -> 1400 log values
• green curve = 1000ms logging interval -> 235 log values

The exact values in detail:

• 1% Low: 103.6 (red), 102.3 (green)
• 0.1% Low: 101.0 (red), 100.0 (green) = mimimum values !

I agree with "Tech Deals" (see YouTube), the "0.1 Low" value is useless, because even in case of 1400 logvalues (red curve) only ONE logvalue is "used", which is the "minimum" .
So, only "1% Low" makes sense ... does it ... does it really help ???

Conclusion
Still not clear for me if it makes sense to calculate 1% Low based on "log interval FPS values" without having the exact time durations between all frames.
What do you think?

Regards
Tom

 

[Polarguin]

Hi TomWoB,
Sorry that I did not read your comments in time. This forum is not my usually visit.
Only the quantity of log values more than 2000, can "0.1% Low" value be useful.
Just imagine, you have 1999 log values, 0.1% *1999 = 1.999
The quantity of "0.1% Low" log value must be an integer.

I do not know how HWiNFO round to a whole number, round half up, or round down.
I prefer to use round down.
1.999 rounding down is 1.
That is the reason why only ONE logvalue is "used" , and equal to "minimum".

 

[TomWoB]

Hi Polarguin,

yes, that's clear. But also in case of you have 20'000 log-values, calculating "1.0 Low" from log-values makes no sense, because it's impossible to get the duration between all frames from log-data.
Maybe there is a much easier solution available: "MSI Afterburner" seems to monitor this values directly:

I'm not an Afterburner Guru, but I think these values can be logged into a file -> this log-file can be opened and presented by Generic Log Viewer !

Regards
Tom