03.04.2009, 12:09
C6_bandini Wrote:Have you ever installed a bunch of MODS, just to end up with some subtle bugs you don't know how to chase ? Well, here is a diagnosis tool, whose purpose is to detect potential conflict between MOD using the same java classes.
Unzip at the root of your IL2 directory, run classchecker.exe and look at the results in doublon.txt
You might need this piece of Microsoft code if classchecker.exe fails to launch
Here is a sample output :
64F83BC6574C11DE exists with :
CRC 7bd79941 : .\MODS\-VuesexternesETvisilongue\64F83BC6574C11DE
.\MODS\-VuesexternesETvisimoyenne\64F83BC6574C11DE
.\MODS\-VuesexternesETvisireduite\64F83BC6574C11DE
.\MODS\-Vuesexternesseules\64F83BC6574C11DE
CRC 50433e87 : .\MODS\-Flare_Distance\64F83BC6574C11DE
.\MODS\___Avions_nouveaux_slots\64F83BC6574C11DE
From this output, you know that the four first mods will clash with the two last ones, because all six MODs use the same class, but the class can have different content. If two MODs with different classes are used together, then only one of the MOD will really be activated. It can be harmless, or harmful.
This tool is here to help PACK makers, and PACK users chasing those potentially conflicting mods.
I Downloaded the microsoft code but it fails to launch even with the patch installed do you have any idea
just need to be patient works niceely thanks