Log Files and mod headaches

[Hessan]

Is there any log files or console in game that can help you figure out what is causing conflicts? I am having a strange error that I am sure is caused by a mod but not sure which one it is so I can uninstall it. I always get all of the ones I run off the mod hub in game but I noticed now that all of my combines are no longer usable and missing their wheels. Even the stock ones. Anyone else seeing this with any particular mods? In my testing so far, I have nailed it down to a mod that is causing the issues by disabling all addons and starting a clean save and the problem is not present.

[TheOriginalMark:-)]

There is a log file at "Documents\My Games\FarmingSimulator2022\log.txt" but it probably won't help much (unless you are very lucky). Generally with mod conflicts the only way to isolate the problem mod is by tedious trial and error. There are a couple of ways.

You can try removing the most recent mods being as one of those is the most likely if the problem is recent.

Or you can take out all mods and then add them back 3 or 4 at a time until the problem reoccurs.

[ProviD]

Are you sure it's mods?

Missing Wheels/Tracks (on many/all equipment) have been a long-time symptom of Corrupted Shaders. Don't ask why.

If you've not done it yet, try deleting "shader_cache" folder in ..documents/MyGames/FarmingSimulator22. Might try Verifying the Integrity of Steam Files too.

If that doesn't fix it, you could try deleting your settings files (game.xml & gameSettings.xml) along with the Shaders Cache. Some times the "reinitiation" of the shaders can fail if something in the settings gets read wrong.

Other than that, there's not much else to do but to hunt for that one outdated mod that suddenly borks up everything..

[Hessan]

Thanks for the info. I am going to try the shader cache and see. I did a test where I disabled all mods and only used one of the original base game maps (the US based one) as a test on a new game. With all mods disabled, it worked like a charm. I guess a feature suggestion that would be useful would be if it kept some kind of modhub install log or offered the ability to sort installed by time of install or last update. Generally when something blows up, it is one of the last ones installed.

[Hessan]

I figured it out. Somehow there is two version of the manual discharge mod on mod-hub. One is stuck at 1.0.0.3 and the other is at 1.0.0.5. Removed the duplicate and it seems to have fixed the issue. I found it because it was throwing an error in the mentioned log file so I lucked out this time.