Jump to content

Combining Mods error warning in JGSME


Recommended Posts

Posted

I wondered if there are issues with combining MODs I get an error warning  with newtracercouour and the VR clouds.

 

Also the Historically correct markings does not seem to work for me.(TBC)

VBF-12_Stick-95
Posted

I would say is depends on the mods.  Don't know about the VR cloud mods.

 

I know that portions of the Historic markings mod is overwritten when installing the 4K default and white mods.  In this case it is not an issue.

 

When you say the Historic markings doesn't work for you, what is it that happens?  Does it show in JSGME and activate?

TG-55Panthercules
Posted (edited)

There are generally two types of "error" messages from JSGME - one says that certain folder(s) have already been created, and the other says that certain file(s) have already been modified.

 

The first one (folders) is completely harmless and can be safely ignored completely.

 

The second one indicates that the mod you are trying to activate changed one or more files that some mod you previously activated also modified.  This isn't necessarily fatal/troublesome - it may in fact be intended behavior (e.g., the winter default skin mod will overwrite the summer default skin files in the 2K official skins with historical markings mod, and the 4K official skins with historical markings mod will overwrite some of the files in the 2K mod version, and that's OK).

 

However, the file message is alerting you to the fact that the mod you're currently activating will overwrite (some of) the previous mod's files, whch means that whatever the previous mod did to such file(s) will be ignored and only the effects of the second mod (on those files) will be seen.

Edited by TG-55Panthercules
Posted
16 hours ago, VBF-12_Stick-95 said:

When you say the Historic markings doesn't work for you, what is it that happens?  Does it show in JSGME and activate?

I found my error on this one as I  installed JSGME in the data folder not the root folder of the game as clearly stated in the readme file :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...