06-08-2020, 07:16 PM
@darklinkpower
I don't think this was the case. He just clicked wrong button. He basically downloaded whole GitHub repository as a zip file. Which, coincidentally, has a very similar name and the same extension. The extension might be a potential clue for the potential user... Also presence of the mainfest file in the project root is sadly causing it being visible in the Playnite, even though there is no DLL file present. I've created an issue for that.
@L0RD-SiLVER
Well, I do not really know the cause. Are you aware, that you might be using symlinks or junctions, that would lead to some other directory? The algorithm itself is not stellar or complicated. It just recursively iterates through the folders and sums the file sizes. Should there be a junction, the OS/filesystem serves this as an ordinary folder with no clue to recognize this situation.
If not that, I might by at my wits end.
This is, I understand, with the "Size on Disk" option disabled. Just FYI, realted to the properties window https://imgur.com/FYryQnq , disabled means the top size, enabled means the bottom "Size on Disk" value.
There could be some wierd sector rounding up, when using the Size on Disk feature, when it calculates a large amount of small files. But I doubt that it would sum up to over 125 GB...
I don't think this was the case. He just clicked wrong button. He basically downloaded whole GitHub repository as a zip file. Which, coincidentally, has a very similar name and the same extension. The extension might be a potential clue for the potential user... Also presence of the mainfest file in the project root is sadly causing it being visible in the Playnite, even though there is no DLL file present. I've created an issue for that.
@L0RD-SiLVER
Well, I do not really know the cause. Are you aware, that you might be using symlinks or junctions, that would lead to some other directory? The algorithm itself is not stellar or complicated. It just recursively iterates through the folders and sums the file sizes. Should there be a junction, the OS/filesystem serves this as an ordinary folder with no clue to recognize this situation.
If not that, I might by at my wits end.
This is, I understand, with the "Size on Disk" option disabled. Just FYI, realted to the properties window https://imgur.com/FYryQnq , disabled means the top size, enabled means the bottom "Size on Disk" value.
There could be some wierd sector rounding up, when using the Size on Disk feature, when it calculates a large amount of small files. But I doubt that it would sum up to over 125 GB...