GIANTS Software - Forum

MadMax wrote: Thu Feb 12, 2026 9:41 am Hi, issue will be fixed in upcoming update.

Can you tell me when the patch will be released?

argument wrote: Sun Apr 05, 2026 10:39 am

MadMax wrote: Thu Feb 12, 2026 9:41 am Hi, issue will be fixed in upcoming update.

Can you tell me when the patch will be released?

Was released the 24th of March...... Have you updated pf?

Yes, but I'm still having massive performance issues while mowing and turning hay.

Tedding is still an issue whether using PF or not. Especially if you hire a worker to do the tedding.

Since the last update, for me its fixed. No more lag with PF when mowing/tedding grass on modded maps.

The problem persists. As soon as you start harvesting in the field or mowing the grass, the frame rate drops significantly. You get 10–15 fewer FPS.

Hey, thanks for posting the log, that helps a lot. The grasswork drop you describe (80–90 fps normally, 30–40 when mowing/tedding/windrowing) is something a lot of FS25 players have run into, especially on high-end AMD cards at 4K, so you are not alone.

From your log a few things stand out:

you are on 1.15, RX 9070 XT, 4K, Custom Ultra
Foliage View Distance, Foliage LOD and Displacement View Distance are all set to 2.0–2.2 (double the default)
DirectStorage is running in CPU fallback mode ("No GPU decompression")
the shader archive is reported as missing
V-Sync is on in-game
FS25's new ground deformation is the reason grass work is heavier than other jobs. GIANTS stores deformation on a much finer grid than FS22, and a lot of that work runs on the CPU, not the GPU. When you touch mowed grass the game has to update the density map, compress tiles, and draw a huge amount of extra foliage instances — with your distances at 2×, that cost spikes, and V-Sync then locks you to the next step down (around 30–40 fps). Your brother seeing the same thing points to the engine, not a faulty PC.

A few things that have consistently helped others:

1. Rebuild the shader cache first
Close the game, delete the whole Documents\My Games\FarmingSimulator2025\shader_cache folder, then start again and let it sit for 5–10 minutes on the map. The missing shader archive in your log often causes stutter after a driver update.

2. Turn off the hidden head-tracking
In game.xml (same folder) set the three head-tracking entries — tobii, trackIR and openTrack — to false. The menu toggle does not actually stop them, and they add CPU load during foliage updates.

3. Pull back the grass settings
You can stay on Ultra, but set:

Foliage View Distance Factor → 1.0
Foliage LOD Distance Factor → 1.0
Displacement View Distance Factor → 1.0
Tyre Track Segments → 2.0
Foliage Shadows → off
Those four control how much deformed grass is rendered around you.

4. Give the game more VRAM budget and turn V-Sync off
In the same game.xml, raise textureStreamingMemoryBudget from 4 GB to about 12 GB (12884901888) for a 16 GB card, and disable V-Sync in-game. Use the AMD driver if you need sync.

5. Use FSR 3 as intended
At 4K, set FSR 3 to Balanced and turn on Frame Generation. It was added specifically for this CPU-bound scenario and usually recovers 20–30 fps during mowing without a big visual hit.

6. Quick test without mods
Move your mods out temporarily and try a base-game mower on the same field. A couple of popular tedder mods force extra particles that make the drop worse.

None of this is a perfect fix — the deformation system is just heavy by design right now — but with those changes most people go from 30–40 fps back up to the 70–85 range while grassworking, which makes it playable.

If you try the shader rebuild and the distance tweaks, let us know what changes. Happy to look at a new log if it is still dropping.

"5. Use FSR 3 as intended
At 4K, set FSR 3 to Balanced and turn on Frame Generation. It was added specifically for this CPU-bound scenario and usually recovers 20–30 fps during mowing without a big visual hit."

Thanks, thanks, thanks. I had the same issues with grass. I have the 5070 Ti and always got bad FPS when mowing grass. That tip finally helped. I hope Giants fixes it eventually.

your welcome, im glad that someone got some use of this, and i really appretiate you telling me