Mouse input · Current performance check
Funnel Runners Mouse Delay: Checks and Smoothing
Direct answer
Start by comparing Mouse Smoothing both ways in the same repeatable camera or repair-input situation. Keep the value that feels better; restore your starting value if it does not help.
If the symptom is stutter rather than the control itself, update first and make only one graphics change. Patch #015 says selected graphics changes trigger shader compilation on the next game boot; it fixed one Frame Generation restart-related stutter but does not offer a universal mouse-delay fix.
Patch 0.35.4 added a Mouse Smoothing option, while Patch #015 still lists performance loss or stutter on some setups and changed shader compilation after selected graphics changes.
How to test Funnel Runners mouse delay
A repeatable comparison is more useful than stacking several latency tweaks and guessing which one mattered.
Choose one repeatable input moment
Use the same camera turn, cursor movement, or repair-minigame action for every test.
Write down the starting values
Record Mouse Smoothing and the exact game situation before changing anything. If you change graphics settings, keep a note of the one setting you changed.
Change one relevant setting only
Repeat the same input moment and look for a clear improvement as well as any new stutter, frame pacing, or visual trade-off. If you changed Anti-Aliasing Method, Shadow Quality, or Lumen GI/Reflections, launch the game again so Patch #015's shader compilation can run.
Restore before the next branch
If the comparison is unchanged or worse, restore the starting value. Do not combine unsuccessful tests.
Funnel Runners Mouse Smoothing and current checks
Mouse Smoothing is an official option. The current patch also gives a bounded way to distinguish a graphics-setting change from a general input claim.
Test 1
Mouse Smoothing
Official availability: added to Control settings in patch 0.35.4.
- Change
- Record the current Mouse Smoothing value, then change only that option.
- Observe
- Repeat the same camera or repair-input movement and compare both responsiveness and motion feel.
- Restore
- Return to the starting value if the delay is unchanged or the movement feels worse.
- Limit
- The patch confirms the option exists; it does not say that smoothing causes or fixes input delay, and it does not publish a default value.
Test 2
Graphics changes and the next game boot
Official Patch #015: changing Anti-Aliasing Method, Shadow Quality, or Lumen GI/Reflections triggers shader compilation on the next game boot.
- Change
- If you choose to change one of those graphics settings, record it and restart the game before comparing the same input moment.
- Observe
- Compare the same input moment after the next boot. Separate control feel from shader-compilation hitches or general frame pacing.
- Restore
- Restore the starting value if the result is unchanged or worse; do not stack a second graphics change onto an unsuccessful test.
- Limit
- The patch describes when shader compilation runs; it does not say that any listed graphics setting causes or fixes mouse delay.
Test 3
Frame Generation report after Patch #015
Official Patch #015 says it fixed intense stuttering when FSR Frame Generation was enabled without restarting the game.
- Change
- Update to the current patch before treating Frame Generation as a troubleshooting branch; then return to your baseline situation.
- Observe
- Check whether the named restart-related stutter remains, without assuming it explains every delayed or floaty input report.
- Restore
- Restore any unhelpful in-game setting rather than adding system-wide overrides.
- Limit
- The fixed issue is specifically about enabling FSR Frame Generation without restarting. It is not a universal cause or fix for mouse delay.
Guide scope
Follow the current in-game prompts and the limits below. This page covers the task named above, not every possible failure or game system.
Keep the answer bounded
What these comparisons do not prove
A reversible test can help your setup without establishing a game-wide cause.
- Mouse Smoothing, graphics settings, Frame Generation, or display mode is the universal root cause.
- The current default value or exact effect of Mouse Smoothing on every input surface.
- Whether Raw Input or mouse acceleration controls exist in the current menu.
- That an older player-reported result transfers to the current patch, different hardware, or frame rates.