Hey! First off thankyou for bringing MH to FS25! I just wanted to drop a line and tell you that on field 128, for some reason i get massive framerate drops. Especially if you engage a piece of equipment such as a combine or baler. I have gone back in with no mods and still the same issue. Not sure whats going on as thats just a grass field as default. If you ever get time to look at that id appreciate it. But i know modding is busy so no worries.
Thanks!
Jake
Hello, your welcome.
I just loaded into a new save with easy dev, and store deliveries. I mowed a big chunk of that field, then tedded most of what I mowed. Then windrowed and baled it. I had some FPS drops but nothing crazy. Loaded it in GE and looked around and didnt see anything stuck under the map.
Did you plow that field up and plant a different crop or something that I could try testing? Have you noticed this anywhere else on the map?
Thankyou for checking! So far what im trying to do is to harvest field 77 on a contract, that is when i noticed the issue, its only when around the boundaries of 128. However, with you checking it out, i bet the issue is on my end at this time, not yours. If you have no issues, it has to be on my end.
Ill check my settings and go from there. Ill report back if i figure it out.
How long have you been playing that save? I ask this because when I tested that I was was getting FPS in the 30's. When I went back to my current save, my main farm is 159 and I also have the BSL dairy just north of that. My FPS was maxed out at 60, weird cause I TP'ed to that grass field and my FPS stayed around 60. Only real difference between my current save and the public one is mine runs thundr's RCR.
So I asked about your save maybe it's doing a cache thing similar to after the game updates. If you bought it on steam maybe try verifying files. I'm going to have to keep an eye on it.
After continued investigation, this is what I have found and I am now up and running. So this save has roughly 11 hours on it and its my first save. I have fixed the issue, or rather it fixed itself, but here is what I did.
After loading with no mods did not solve the issue, I cleared my shader cache next. This still did not fix the issue, i would load in, rent a combine and header, go to the spot, still have the wild framerate drop, and the header would spaz out.
Following this, i pulled all mods completly out of my mods folder, cleared the shader cache again, and went back in 100% fresh. This time bingo I had no issues. This solved the problem. Im assuming that even though I was loading in with no mods selected, the game still having them in the background was possibly causing my issue? I do not know how that works I am absolutely an amature.
Since then, I have added back the core mods I use one at a time and tested the same spot the same way since, and so far so good. Currently I have not added all mods I had back, and will continue until i find the issue.
It appears I had a bad mod or mod conflict that had some type of lingering effect?
Every mod I am using is from the ingame modhub or itch/facebook direct links from the modders themselves so im trying to be smart haha.
That process is a PITA, I had to do that once or twice on FS22. Glad you got it working, it seems to still load mods even if they are not active as I get keybinds sometimes for mods that are not active on my save.
Now for testing I have two mods folders and rename them and add mods accordingly to the second one depending on what im testing. If you figure out which mod it was LMK.
