Correct - two of the .dlls are version 1,2,0,0, and the other two are version 2,0,0,0 and the package you posted is perfectly fine as it contains both versions. Thing is, only the 1,2,0,0 version can use the "newer" GPU / SourceId options to retrieve data for like the 2nd GPU and such, hence it's the latest version. This is confirmed by:I don't use it, so I will leave it to your expertise, but the .dll files seem to indicate 2.0
1.jpg
- the posts on the guru3d thread, where the last version is the 1.2 one (yep, I read the entire thread, lol)
- an example skin like this that uses the "new" GPU / SourceId syntax
Now, if you try and replace the MSIAfterburner.dll from the C:\Users\[User]\AppData\Roaming\Rainmeter\Plugins folder (which, as you know, are the actual .dll files picked for usage when you run Rainmeter) first with the 1,2,0,0 ones and then with the 2,0,0,0 ones from your package, you'll see that only the 1,2,0,0 one is functioning with the GPU / SourceId combo, especially if you have 2 GPUs like me (GPU0, GPU1) and scroll to see the 2nd GPU data.
Obviously, the About > Plugins tab will always show the higher 2,0,0,0 version if you have all 4 .dlls from your package in the C:\Users\[User]\Documents\Rainmeter\Skins\@Vault\Plugins folder, even though the one you might be using in the C:\Users\[User]\AppData\Roaming\Rainmeter\Plugins folder is the 1,2,0,0 one.
For the record, this is one of the reasons why we have from time to time posts by users complaining that the MSI AB plugin doesn't work for them (when they use the 2,0,0,0 version without knowing). I suspect the plugin author did a "reversioning" at some point in the plugin's life that could explain how a lower version is the latest one.
Statistics: Posted by Yincognito — January 28th, 2025, 1:26 pm
