i was just trying (and failing) to convert a terragator. Thank you for this!
My only wish is that I could delete some decorations, but this map is unbelievable. Keep up the awesome work.
@Hunterfr6 very easy to open in Giants Editor
@exodus1114 no you'd have to add stuff
(sorry about formatting) Running latest version. FS25 fully updated. No longer able to shift gears correctly Powershift, quad track, tested on 2 tractors. field is plowed and it just rained. after <10 shifts, lose the ability to upshift or downshift. Confirmed isolated to mudsystemphysics, although i do have many other mods at work. For what its worth, I had Claude Sonnet take a crack at it. The fix worked. Here's its response since I know basically zero about modding: %%% Mod: Mud System Physics v1.2.9.1 %%% File: scripts/DrivePhysicsCoordinator.lua, lines ~250–316 %%% SYMPTOM: In a plowed, wet field, quad-track tractors (no implement attached) stop being able to upshift, then also stop being able to downshift. %%% CAUSE: This file overwrites VehicleMotor.shiftGear, setGear, shiftGroup, and setGearGroup. Each override silently blocks the call — returns without ever running the original function — whenever it's an upshift and a computed loadFactor (combining slip, wetness, and sink from the field/mud subsystems) exceeds 1.30 for gears or 1.50 for gear groups. That threshold is easy to cross from wheel slip/sink alone on a heavy quad-track, with no implement needed. %%% TEST PERFORMED: Raised both thresholds to 99 (effectively disabling the block) and re-ran the same wet/plowed field conditions. Shifting worked correctly in both directions with no freezing. %%% CONCLUSION: This confirms the gear-block logic in this file is the cause of both symptoms, not just the upshift restriction it was designed to enforce. Since the code never explicitly blocks downshifts, the most likely explanation is that repeatedly short-circuiting the shift call — without ever invoking the real superFunc — leaves whatever internal "shift pending" state the base game's automatic transmission AI relies on unresolved, stalling its whole decision loop rather than just the upshift half. That mechanism wasn't verified against log output (didn't check log.txt/dev console during the test), so it's an inference from the behavior, not a confirmed root cause at the engine level — but the before/after test result is solid. %%% SUGGESTION: rather than swallowing the call outright, consider whether superFunc needs to run with a "deny" signal the transmission AI can recognize as resolved, so it doesn't get stuck waiting on a shift that will never complete.
Happy to help. Love the mod!
(sorry about formatting) Running latest version. FS25 fully updated. No longer able to shift gears correctly Powershift, quad track, tested on 2 tractors. field is plowed and it just rained. after <10 shifts, lose the ability to upshift or downshift. Confirmed isolated to mudsystemphysics, although i do have many other mods at work. For what its worth, I had Claude Sonnet take a crack at it. The fix worked. Here's its response since I know basically zero about modding: %%% Mod: Mud System Physics v1.2.9.1 %%% File: scripts/DrivePhysicsCoordinator.lua, lines ~250–316 %%% SYMPTOM: In a plowed, wet field, quad-track tractors (no implement attached) stop being able to upshift, then also stop being able to downshift. %%% CAUSE: This file overwrites VehicleMotor.shiftGear, setGear, shiftGroup, and setGearGroup. Each override silently blocks the call — returns without ever running the original function — whenever it's an upshift and a computed loadFactor (combining slip, wetness, and sink from the field/mud subsystems) exceeds 1.30 for gears or 1.50 for gear groups. That threshold is easy to cross from wheel slip/sink alone on a heavy quad-track, with no implement needed. %%% TEST PERFORMED: Raised both thresholds to 99 (effectively disabling the block) and re-ran the same wet/plowed field conditions. Shifting worked correctly in both directions with no freezing. %%% CONCLUSION: This confirms the gear-block logic in this file is the cause of both symptoms, not just the upshift restriction it was designed to enforce. Since the code never explicitly blocks downshifts, the most likely explanation is that repeatedly short-circuiting the shift call — without ever invoking the real superFunc — leaves whatever internal "shift pending" state the base game's automatic transmission AI relies on unresolved, stalling its whole decision loop rather than just the upshift half. That mechanism wasn't verified against log output (didn't check log.txt/dev console during the test), so it's an inference from the behavior, not a confirmed root cause at the engine level — but the before/after test result is solid. %%% SUGGESTION: rather than swallowing the call outright, consider whether superFunc needs to run with a "deny" signal the transmission AI can recognize as resolved, so it doesn't get stuck waiting on a shift that will never complete.
