Skip to content

Troubleshooting

Jump to bottom
TisonK edited this page May 30, 2026 · 4 revisions

Troubleshooting

First step: check the log

All mod output is tagged [Soil Fertilizer] in log.txt:

  • Windows: Documents\My Games\FarmingSimulator2025\log.txt
  • Mac: ~/Library/Application Support/FarmingSimulator2025/log.txt

Search for [Soil Fertilizer] and look for ERROR or WARNING lines. You can also enable verbose output with the SoilDebug console command.

Common problems

HUD does not appear

  1. Press J to toggle — it may simply be hidden
  2. Check that Show HUD is enabled in Settings (ESC → Settings → Soil & Fertilizer)
  3. If you are a client in multiplayer, wait a few seconds after joining — the full sync may still be in progress
  4. Check log.txt for any HUD or SoilHUD error lines

Settings panel shows raw key names (e.g. sf_diff_1 instead of "Simple")

This is a translation resolution issue. Make sure you are running version 1.3.2.0 or later — this was fixed in that release.

Soil report (K key) does not open

  1. You must be on foot — the K binding is registered in the PLAYER input context
  2. If you recently got out of a vehicle, wait 1–2 seconds for the input context to switch
  3. Check log.txt for any SoilReportDialog errors

No field data in HUD — "no field detected"

  • You may be standing between fields or in a road/forest area not covered by any field polygon
  • Move toward the center of the field and wait a moment for the field scan
  • On large maps the field scan runs in the background — data may not be available for the first 10–30 seconds after load

Nutrients not depleting at harvest

  1. Check that Fertility System is enabled in Settings
  2. Check that Nutrient Cycles is enabled
  3. Check log.txt for [Soil Fertilizer] Harvest: lines — if none appear, the harvest hook may not be firing
  4. Run SoilDebug in console and harvest again to see verbose output

Nutrients not restoring when fertilizing

  1. Check that the fill type you are using is recognized (see Fertilizer Types)
  2. Custom fill types from equipment mods may not be in the profile table — check log.txt for unknown fill type warnings
  3. Check SoilFieldInfo <fieldId> before and after to confirm the values changed

Multiplayer: client settings do not match server

  1. Disconnect and reconnect — the full sync runs on join with up to 3 retry attempts
  2. On the server, run SoilShowSettings and compare with the client's soilStatus output
  3. If there is a persistent mismatch, open an issue with both log files

Dedicated server: mod not initializing

  1. Confirm the mod zip is in the server's mods folder
  2. Check the server log for [Soil Fertilizer] Initializing... — if absent, the mod did not load
  3. The GUI is intentionally disabled on dedicated servers — GUI initialization skipped in the log is normal
  4. Run soilStatus from the server console to confirm the mod is running

Soil data not saving

The mod hooks FSCareerMissionInfo:saveToXMLFile to write soilData.xml. If saving fails:

  1. Check log.txt for soil data NOT saved or save hook warnings
  2. Confirm the savegame directory is writable
  3. In multiplayer, only the server saves soil data — clients do not write soilData.xml

AI helper with "Buy fertilizer" — tank never fills / money not deducted

Fixed in v1.8.1.0. If you are on an older version, update to v1.8.1.0 or later.

The helper's BUY mode hook had a shifted function signature that prevented the intercept from ever firing — the helper would spray as if it had unlimited product, but no money was deducted and the fill level was never correctly tracked.

If you see this on v1.8.1.0+, check:

  1. Confirm the AI job is set to "Buy" as the fertilizer source (not "Own supply")
  2. Check log.txt for any BuyMode or addFillUnitFillLevel error lines with SoilDebug enabled
  3. Open an issue with the helper type (vehicle + implement) — the backup path in the sprayer hook should catch all cases, but some unusual vehicle setups may need adjustment

PDA "Owned Fields" filter shows all fields regardless

Fixed in v1.8.1.0. Update to v1.8.1.0 or later.

On older versions, the ownership check was comparing against the wrong ID type (field index vs farmland ID), so every field silently passed the filter. After updating, open the PDA (Shift+P), go to the Fields tab, and toggle the filter button in the footer bar — only fields you own should appear.

PDA filter button label stuck / shows wrong text

Fixed in v1.8.1.0. The footer button label now updates immediately when you toggle the filter.

Log shows attempt to call a nil value in the update loop / simulation stops

Fixed in v1.8.1.0. On older versions, if NetworkEvents.lua failed to load for any reason, three call sites in the update loop would throw a nil-call error and halt the simulation — nutrients would stop depleting and fertilizer effects would stop applying for the rest of the session.

After updating, if you still see nil-call errors tagged [Soil Fertilizer] in the log:

  1. Run soilStatus to confirm the mod is fully initialized
  2. Check that src/NetworkEvents.lua is present in the mod zip (not corrupted)
  3. Look for any earlier Lua errors in log.txt that could interrupt the load sequence

Mod disables itself on load

Cause: Precision Farming (FS25_precisionFarming) was detected as active in the mod manager.

This mod is not compatible with Precision Farming. When PF is detected as active, this mod automatically disables itself at startup and shows an on-screen dialog explaining why. This is intentional behavior to prevent data corruption.

Solution:

  1. Open the mod manager (ESC → Mods)
  2. Disable FS25_precisionFarming
  3. Restart the game or reload the save

If you have PF installed but disabled in the mod manager, this mod will run normally. The detection only triggers when PF is actively enabled.

Version dialog doesn't appear on load

Fixed in v2.2.5.0. On older versions, there were two causes:

  1. If the mod had been previously disabled (via the Enable Mod toggle), the version dialog would not appear even after re-enabling. Fixed.
  2. If a crash occurred during mod initialization, the dialog was suppressed along with any other startup UI. Fixed — the dialog now appears independently of init errors.

After updating to v2.2.5.0, the dialog will appear on the next load. If it still does not appear, check log.txt for [Soil Fertilizer] error lines.

Reporting a bug

Please open an issue at GitHub Issues and include:

  • Your log.txt (filtered for [Soil Fertilizer] lines)
  • Mod version (visible in Mod Manager)
  • Singleplayer or multiplayer
  • Steps to reproduce

Admin settings reset to defaults after dedicated server restart

Fixed in v1.9.9.3. On older versions, settings were loaded before the savegame directory was available on dedicated servers, so the load always failed silently and fell back to defaults.

After updating, settings persist correctly across server restarts. If you still see defaults after restarting:

  1. Make sure your server is running v1.9.9.3 or later
  2. Change at least one setting from the Admin panel or console — this triggers a fresh save to the correct path
  3. Restart and confirm settings persist with SoilShowSettings

Admin changes a setting but their own settings panel does not update

Fixed in v1.9.9.3. On older versions, the setting change broadcast excluded the admin's own connection, so the admin's panel stayed out of sync while all other clients updated correctly.

After updating, the admin's panel refreshes on every setting change alongside all other clients.

Large map: game freezes or crashes when a client joins

Fixed in v1.9.9.1. On older versions, the server sent all field data in a single blocking network packet on client join. On maps with 255+ fields this exceeded the packet budget and caused the join to hang or crash.

As of v1.9.9.1, field data is streamed to the joining client in batches of 32 fields across multiple frames. The settings handshake is sent immediately so the client retry timer is cancelled right away.

Clone this wiki locally