Over the Hill Best PC Settings: Keep the Scenery

Keep the landscape, then decide which details you can spare. Our Over the Hill recommendation favors selective graphics reductions and a frame rate your PC can hold through a drive. Turning everything down at once gives you a poorer view before you know which compromise was worthwhile.

This is a scenery-first tuning guide for the Windows release, checked October 15, 2026. Hone hasn’t benchmarked a best preset or measured FPS gains. The recommendations below combine observed launch-era menus with the developer’s support guidance; June demo performance reports don’t establish how the released game runs.

Choose a frame rate you can keep

Try 60 FPS as a starting goal, then lower the goal if your PC cannot sustain it in the places you want to drive. A cap won’t raise a slower frame rate. Copying a higher number from someone else’s setup doesn’t make the difficult stretch of your route any easier.

Open Settings → Graphics → Basic and use your display’s native output resolution. If performance is insufficient, compare an available quality-oriented upscaling choice. Judge moving foliage and vehicle trails at the same output resolution.

For the in-game Framerate Cap path, leave VSync off and choose a maintainable limit. If you prefer VSync for your display and tearing tolerance, use that path instead: PCGamingWiki reports that enabling it disables the game’s limiter. Don’t expect an inactive cap to govern the result.

The official minimum is a useful reality check:

The listing says these specifications were tested at Full HD, but gives no FPS or preset target. Its recommended field supplies no useful hardware tier. Meeting the minimum therefore doesn’t establish a 60-FPS setup, and older demo numbers are a poor substitute for that missing target.

Keep the hillsides, trim selected effects first

Simple textures don’t make the landscape free to draw. Funselektor points to distant vegetation, shadows, effects and processing as real work for the game. That makes selective changes more useful than assuming the art style should run effortlessly.

Terrain LOD Quality and Tire Tracks Quality are separate graphics controls, without an established physics or grip adjustment. Picture preferences aren’t measured FPS improvements. Observed build 26.10.12_BE848F1 supplies menu labels, not defaults or complete value ranges.

Give the change a fair test drive

Pick a short stretch you can repeat and use the same camera. Include the part that actually bothers you. A result beside a parked vehicle won’t settle a problem that appears farther into the drive.

Keep the conditions close: Over the Hill has changing weather and a day-night cycle, so a clear daytime pass and a rainy night pass are different comparisons. Keep the player count the same too. If trouble happens only with friends, compare solo and co-op separately before treating it as a graphics problem.

Change one setting, drive the stretch again, and ask two questions: did the difficult part improve, and do you like the picture enough to keep the change? If the answer to the second is no, restore it and try another compromise. A higher average isn’t much consolation if you dislike what you removed.

If only controller input feels wrong, compare keyboard input and, where possible, a wired controller connection. That comparison is more useful than immediately reducing graphics. It can narrow the circumstances without proving a particular connection fault or latency gain.

Keep any performance counter and its settings consistent between passes. Persistent hitches alone don’t identify a CPU, GPU or network cause. Our guide to comparing FPS benchmarks ↗ (opens in a new tab) explains how different counters and changing conditions can turn a plausible comparison into a misleading one.

When the picture is broken, use the matching workaround

A missing hillside needs a different response from an ordinary slow frame rate. The developer documents two specific Windows rendering problems:

Use the symptom to choose the instruction. Adding a launch flag to an otherwise intact scene gives you another change to untangle without an established performance benefit.

Send a report worth investigating

From the affected screen, use the pause-menu bug report or Ctrl+F. Funselektor says this sends an error log and screenshot automatically.

For a forum report, describe the problem and the steps that reproduce it; add images or video if possible. Include Player.log and Player-prev.log, found in Windows at:

%USERPROFILE%\AppData\LocalLow\Funselektor\over the hill

Add your hardware, current graphics choices and whether the issue happens alone or with friends. “The same bend slows down with this configuration” gives someone a starting point; “bad optimization” gives them little to investigate.