Recent content by TomWoB

Hi all, I have just seen in the release notes that logging with UTF-8 Encoding has now been released: I can confirm that German log files now have an UTF-8 BOM and can be read by the Generic Log Viewer without any problems: @LannTheSmart and @i.bylich1 Please try logging with a HWiNFO...

No problem for GLV, my uploaded UTF-8 example logfile contains already the UTF-8 BOM !

But decimal separator is anyway configurable in HWiNFO Log Settings (?) or "YOU/we" define FIX for HWiNFO UTF8-CSV-logfiles: Encoding UTF-8 value separator: , (comma, but see BTW below) decimal separator: . (point) optional thousands separator: ' (single apostroph) String-values can be within...

Hi all, @i.bylich1 With TXT we have the same encoding issues as with CSV @Martin The described alternatives in the YouTube video have a major issue: not supported by Excel for import so far! You already wrote in Post #207 "Another solution would be to introduce a new CSV format with UTF-8...

Hi all, regarding the last posts in this thread here is a good YouTube video that deals with the pitfalls of the CSV-format. The coding problem is explained from 2:52 onwards: Stop Using CSV ! Regards Tom

BTW: I opened the russian logfile with some other (russian) codepages for character-mapping: 855, 866, 20866, 20880. Codepage 20866 generates category names like this: Does they makes more sense ?

Hi i.bylich1, OK, I had a quick look at your logfile and here are some comments: I translated header line to English (with Deepl), which seems to work two category names are "empty" (?) -> shown in GLV as first log-categories " - Data 1" and " - Data 2" all other translated category names are...

Hi i.bylich1, did you already read Post #205 and the followings? Same with Chinese. Anyway, can you upload the logfile ... Regards Tom

Due to the latest recall of CableMod adapters, cases of melted 12VHPWR plugs seem to be on the rise again. The plugs have now been in use for a year -> I think they are starting to corrode. At these high currents, even a minimal deterioration of the plug connection (fraction of an ohm) is enough...

OK, I mean in case of GLV correct ! GLV don't know how much RAM you have installed. GLV uses the data in the logfile to calculate minimum, average and maximum -> these values are mathematically correct, based on your logdata !

Hi all, in case of HWiNFO the Generic Log Viewer (GLV) needs Comma as value separator Dot as decimal separator which are default-values of HWiNFO (I guess). In my logfiles no thousands separator is used, maybe it's ignored if specified thousands separator is equal to value separator (?). The...

Hi Martin, as I already said above, in Gamers Nexus video it looks like Frametime = log category "msBetweenPresents" GPU Busy = log category "msGPUActive" These two log categories exist in @NCSGeek's sample log file. Aren't they part of the open-source PresentMon or an available SDK ?

Hi LannTheSmart, that's not so easy, reading text or numbers from a file depends a lot on your own Microsoft Windows culture/language settings. E.g. some countries use a dot for decimal numbers, some use commas. The same with "special characters", they can be total different. I think for...

Here are some personal thoughts on PresentMon from Intel: I don't think the new metric called "GPU Busy" is a game changer. Why: it logs an extremely large amount of data, example file contains - 73 different log categories with each - 144 data records per second (so really each...

OK, I did some more analysis (watched Gamers Nexus Video) and had a more detail look at the data: a lot of categories are N/A (not available, because of BETA?) in another video I saw, you can use HWiNFO to get sensor information for PresentMon (?) the most important categories are (Gamers Nexus...