Help & community
Over the Hill PC Performance: Reduce Stutter
Troubleshoot Over the Hill PC stutter with graphics preset and resolution tests, frame cap checks, minimum PC requirements, and the older-GPU terrain fix.
Updated
- Guides
- 45
- Topics
- 3
- On this page
- 8
Start With an Update and Lower Graphics Quality
To reduce stutter in Over the Hill, install the current Steam update, compare your PC with the minimum requirements, and test a lower graphics preset or resolution. Judge each change on your own system: graphics settings and community configurations do not guarantee a particular frame rate.
Begin with the symptom that bothers you most, then change settings individually. Use a familiar stretch of driving to compare the result. Keep a brief note of whether the picture becomes smoother, the hitches remain, or only the image quality changes.
Compare Your PC With the Minimum Requirements
Steam lists Windows 10, an Intel Core i5-7400 or AMD Ryzen 5 2600, 8 GB RAM, and an Nvidia GTX 1070 or AMD Radeon RX 5600. The Windows requirements also specify DirectX 11 and 4 GB of available storage. The specifications were tested at Full HD resolution.
Use that comparison to set a sensible starting point for testing. Record your current resolution and graphics preset before adjusting them. Having those original settings written down makes it easier to undo changes that do not help.
Test Presets, Resolution and Frame Caps
- Install the current Steam update and relaunch Over the Hill. This includes the developer's older-GPU terrain fix before you begin comparing graphics settings. Check whether your original symptom remains.
- Select a lower graphics preset as your initial comparison. The PC game starts on its highest preset, so check the selection instead of assuming it already suits your hardware. Treat the lower preset as a test configuration.
- Test a lower resolution while keeping your other choices unchanged. Compare the result with your previous resolution on familiar ground. Restore the original resolution if the change does not provide a useful improvement for you.
- Test an available frame-rate cap. The game offers selectable caps and defaults to 60 FPS, but that default is not a guaranteed result for your PC. Compare how consistently the game moves with your chosen cap.
- Replay your comparison stretch after each adjustment. Keep the route and camera movement as similar as practical. This gives you a clearer basis for deciding whether to keep the change.
- Restore individual visual options gradually once you find an acceptable starting point. Recheck the result after each adjustment. Stop where the balance between image quality and smoothness feels comfortable on your system.
Graphics Options to Compare
Low and Medium provide useful preset values to compare when testing reduced graphics quality. The settings below describe those presets rather than a measured ranking of performance gains. Start with a preset comparison, then use individual options to refine your preferred image.
| Setting | Low and Medium Preset Values |
|---|---|
| Shadow Resolution | Lowest on Low; Low on Medium. |
| Shadow Distance | None on Low; Low on Medium. |
| Additional Light Shadows | Off on both Low and Medium. |
| Vegetation Distance | Lowest on Low; Low on Medium. |
| Vegetation Density | Lowest on Low; Low on Medium. |
| Terrain Detail | Lowest on Low; Low on Medium. |
| Volumetric Light | Off on Low; Low on Medium. |
| Ambient Occlusion | Off on Low; Low on Medium. |
Check Anti-Aliasing and Upscaling Separately
Anti-Aliasing and Upscaling remain unchanged across the graphics presets because the game leaves those choices to you. The preset listing shows Anti-Aliasing Off and Upscaling (DLSS / FSR) Balanced. Check these selections separately when comparing presets so you know which options have actually changed.
Treat a shared configuration as a starting suggestion for your own testing. The frame-rate cost of a setting depends on hardware and resolution. Keep the configuration that works acceptably during your driving rather than chasing somebody else's reported result.
Update First if Terrain Is Invisible
The October 16 update fixed invisible terrain affecting some older GPUs, including Nvidia GTX hardware. The previous -msTessOnce 0 Steam launch option is no longer required for this fix. The update applies the fix automatically whether or not you previously used that option.
If the ground is missing, install the update and reassess that rendering defect before continuing your stutter tests. Keep missing terrain and uneven motion as separate observations in your notes. This helps you describe what still needs attention after updating.
Check Camera Movement Separately
Camera settings are separate from the graphics presets. Available options include Camera Sensitivity, Rotation Damping and Follow vehicle rotation, while the post-launch update also reworked camera collision logic. If the problem feels concentrated in camera movement, retest after updating before adjusting those preferences.
Try camera adjustments individually and judge them by comfort and control. Keep a setting only if it makes the view easier for you to use. Continue evaluating overall smoothness through the graphics, resolution and frame-cap comparisons.
Report Problems That Persist After Testing
If the terrain problem continues on the updated game, include your hardware, game version and Player.log in a support report. The default keyboard shortcut for Feedback/Bug Report is Ctrl + F. Describe the remaining symptom and the changes you tested so the report explains what happens on your PC.
