To add something actually usefull to the discusion here and some information to the user LILU...
If using DSG you can add a additional parameter to xtool command line like ":lib_#" which just tells DSG to use another oodle library which might work better than the other which is actually the same version but not the very same version (if you know what I mean). To specify this a bit more, we can just take oodle library v2.9.10 for example. Currently we have two libraries of this version. The second one (named here as "core_2.9.10\oo2core_9_win64
_2.dll") is a "leaked" library from the oodle SDK, which was never shipped by any game actually. This library will achive much better results then the other v2.9.10 library (in this case "core_2.9.10\oo2core_9_win64.dll"). This is simply due to the fact that the leaked library from the SDK has significant changes and some games were compiled with this specific library, so the other library doesn't work well simply because of the library code changes. But this also means that using the second library version inflationary does not give you automatically better results for games which were compressed with the first library. So this goes in both directions.
Included libraries in DSG are stored here: Resources\Win64\ADDONS\Libraries\Oodle\Oodle_Libs. 7z
There you can also see for which libraries you can use the additional parameter ":lib_#" (
# = oo2core_#_win64
_#.dll)
I suggest to use XToolUI (xtool.exe + xtoolui.dll) to test around with game files and different libraries so you know which library is the optimal to use. Some time ago I wrote some informations for beginners about this case. You should read this
https://fileforums.com/showpost.php?...2&postcount=23
https://fileforums.com/showpost.php?...8&postcount=24