Weapon Mod conflict text file

[flameshiva]

Hi

 

When installing some weapon mods with Vortex I receive conflicts and so have to confirm dependencies. The file is that is conflicting with each mod is DATA/MESHES/ANIMTEXTDATA/ANIMATIONOFFSETS/PersistantSubgraphInfoAndOffsetData.txt

 

It doesn't happen with all weapon mods but some examples are China Lake and Holo Rifle, R91 Assault Rifle , Chinese Assault Rifle animations, Mosin Nagant script reload, M1 garrand.

 

As the file suggests I guess its something to do with these weapon animations. How should I be sorting these mods or this problem which seems fairly common ?

 

Thanks.

[rmm200]

Good chance all those mods provide an identical offset file.

Check the contents of that specific file. If they all really are identical - order does not matter.

If one does have more offsets than the rest - I would choose that one to "Load after".

[flameshiva]

I just realised i forgot to put in the last file name PersistantSubgraphInfoAndOffsetData but i have edited it now.

 

I had a look at the file and out of the ones I have Chinese assault rifle animations has the most offsets so I will just make sure that has the highest priority which Vortex at least suggested anyway. If this is how it works maybe I will put a suggestion to Vortex so it can be updated to automatically do it for people as it is a little confusing and people don't know exactly whats going on.

[AugustaCalidia]

I just realised i forgot to put in the last file name PersistantSubgraphInfoAndOffsetData but i have edited it now.

 

I had a look at the file and out of the ones I have Chinese assault rifle animations has the most offsets so I will just make sure that has the highest priority which Vortex at least suggested anyway. If this is how it works maybe I will put a suggestion to Vortex so it can be updated to automatically do it for people as it is a little confusing and people don't know exactly whats going on.

 

Every widely used mod manager for Bethesda games that I know of leaves file conflict resolution in your hands. That's because the mod manager doesn't know what meshes and/or textures and/or scripts, etc. you the gamer may want. Do you prefer one-handed or two-handed 3rd person animations when you pull out your bazooka pistol? Do you want long eyelashes or short eyelashes or no eyelashes? Do you want clear, clean skin, or do you want to be tatooed from head to toe? Only you know the answer to those questions when presented with a file conflict.

 

Each mod manager has its own way of allowing you to resolve file conflicts. In the case of Vortex, as you know, the conflicts are spelled out for you in a panel where you make and confirm rules about what has priority (I.e., loads after). Vortex will sometimes offer a suggestion to load after or load before. However, those suggestions are based on file timestamps only and not on file contents. There may be times when you know something that Vortex doesn't and therefore you don't want to follow the Vortex suggestion. In fact, many times I have told Vortex, "Thank you for the suggestion, but no thanks."

 

Yes, file conflict resolution can be confusing, especially if you're not familiar with the contents of the conflicting files. In those cases, make an educated guess and then see how things turn out in the game. If you don't like what you see, then go back and simply change the rules (something I've done many times).