There is no single best preset for every 2D platformer. Choose settings according to the visible problem: use V-Sync to address tearing, investigate timing and interpolation when motion shakes at a steady frame rate, profile CPU/GPU work when frame rate is low, and look for first-use shader compilation when the game pauses briefly. A frame cap can make pacing and power use more predictable, but it cannot make hardware reach a frame rate it cannot sustain.
Start with the symptom, not a preset
“Smooth” can describe several different failures. Treating all of them as an FPS problem often makes input or image quality worse without fixing the cause.
As an Amazon Associate I earn from qualifying purchases.
| What you see | Likely cause to check first | Best first action |
|---|---|---|
| Horizontal breaks or partial images during movement | Rendered frames are not synchronized with the display scanout. | Test V-Sync. It can remove tearing, with a possible increase in perceived input latency. |
| Constant shaking or uneven movement while the FPS counter is stable | Physics updates and display refresh are running at different rates, or objects are updated in different time domains. | Check physics timing and, where supported, test physics interpolation. |
| Short freezes or repeated pauses | A CPU/GPU frame-time spike or first-use shader compilation. | Profile frame time and reproduce the pause; check whether it happens the first time an effect appears. |
| Low or widely fluctuating FPS | The CPU or GPU cannot consistently meet the target. | Profile first. For a suspected GPU fill-rate limit, compare a large and very small window. |
These categories can overlap. For example, V-Sync may hide tearing while a physics/display mismatch still produces jitter. Diagnose one symptom at a time and change only one setting between tests.
Free tools Windows power users keep installed
One-click scans. No signup required.
V-Sync: the right choice depends on tearing and latency
What V-Sync changes
V-Sync synchronizes presentation with the monitor’s refresh cycle. When it works as intended, a frame is not replaced halfway through a scanout, so a scrolling level is less likely to show a horizontal tear. The trade-off is timing: waiting for the next refresh can make a button press or direction change feel later, especially when the game is already missing its frame deadline.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Godot documents V-Sync as taking precedence over its FPS maximum when V-Sync is enabled or adaptive, and its maximum cannot exceed the monitor refresh rate. Disabling V-Sync can make input lag less noticeable, but it can introduce tearing. That makes V-Sync a preference informed by the symptom, not a universal “on” or “off” rule. See the Godot 4.7 guide to jitter, stutter and input lag.
Godot settings
In a Godot project, set the display’s V-Sync mode in the project display/window settings, then set an FPS maximum only when you have a reason to cap below the display’s capability. With a supported variable-refresh-rate (VRR) display, Godot advises leaving V-Sync enabled and setting the cap slightly below the panel’s maximum refresh rate. Its documented formula is r - (r * r) / 3600.0, where r is the maximum refresh rate. The Godot 4.7 documentation gives these examples:
| Display maximum | Godot’s documented example cap |
|---|---|
| 60 Hz | 58 FPS |
| 120 Hz | 115 FPS |
| 144 Hz | 138 FPS |
Those are Godot guidance examples, not a guarantee for every engine, monitor, driver or game. A cap below the VRR ceiling leaves headroom for the display to stay in its variable-refresh range. If VRR is unavailable, choose a target the hardware can reach consistently and test whether V-Sync produces the best feel.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Unity settings
For desktop Unity projects, Unity recommends QualitySettings.vSyncCount when smooth frame pacing is the priority. Unity describes V-Sync as hardware-based, while Application.targetFrameRate uses software timing and can be susceptible to microstuttering. When V-Sync is active on supported non-mobile platforms, Unity ignores targetFrameRate. On mobile platforms, Unity ignores vSyncCount and uses targetFrameRate instead. Confirm the behavior for the Unity version and target platform in the Unity 6000.5 targetFrameRate reference.
| Choice | Advantages | Costs or risks |
|---|---|---|
| V-Sync on | Reduces tearing and can provide regular presentation intervals. | May add perceived input latency; if the game misses a deadline, pacing can feel uneven. |
| V-Sync off | Can reduce perceived latency, particularly when a high, reachable cap is used on a GPU-limited system. | Tearing is possible. The latency benefit does not apply when the CPU is the bottleneck. |
| Adaptive V-Sync (where offered) | Lets the implementation vary synchronization behavior as frame rate changes. | Behavior is engine- and driver-specific; test it against the actual display. |
Choose an FPS cap that hardware can actually hold
A cap limits how many frames the game attempts to render. It can reduce power consumption, heat, fan noise and battery drain, especially when the game would otherwise render far more frames than the display can show. It cannot force an underpowered CPU or GPU to meet the number: if frame work takes longer than the cap’s interval, actual FPS remains lower.
How to pick a target
- Measure sustained performance. Play the busiest level section, not an empty menu, and watch frame time rather than a short-lived FPS peak.
- Use a reachable target. A stable 60 FPS is usually preferable to a cap that alternates between 60 and 40. On a 120 or 144 Hz display, use a higher target only if the game can sustain it and the engine’s timing behaves well.
- Coordinate with synchronization. With V-Sync, the display refresh and engine rules determine which caps are effective. In Godot, V-Sync or adaptive V-Sync takes precedence over the maximum FPS setting. In Unity desktop builds, active V-Sync causes
targetFrameRateto be ignored. - Re-test input. A lower cap can make timing more consistent but may feel less responsive than a higher, stable target. Keep the setting that matches the platformer’s control demands.
Godot’s documentation notes that a high, consistently reachable cap with V-Sync disabled can reduce input lag compared with uncapped rendering in GPU-bottlenecked cases. That particular benefit does not apply when the CPU is the bottleneck, so profiling matters before treating an uncapped mode as faster.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Fix physics/display timing mismatch and jitter
Why a steady FPS can still look uneven
A platformer’s simulation may advance at a fixed physics rate while rendering occurs at the monitor’s refresh rate. Godot identifies a common case as physics running at a different frequency from the monitor; its documentation describes the typical problem as occurring when game physics, usually 60 Hz, runs at a different rate than the monitor refresh. A 60-Hz simulation displayed on a 144-Hz panel cannot distribute its physics steps evenly across every refresh, so the visual position can appear to repeat and then jump even when the average FPS counter looks healthy.
Jitter can also come from mixing time sources. For instance, a character updated in the physics loop and a camera or effect updated in an idle/render loop may not sample the same position at the same moment. Keep objects that must track one another in a consistent update domain, or deliberately interpolate the visual representation.
Physics interpolation
When the engine supports it, physics interpolation draws a physics object’s transform between the most recent physics frames. This can make motion appear continuous across different render rates and physics tick rates. It is a visual smoothing technique, not a way to make the simulation itself run more often.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Godot warns that physics-dependent behavior, including player movement, can gain input latency when interpolation is enabled. A platformer that prioritizes pixel-perfect, immediate control may prefer a little visible stepping over delayed feedback; a cinematic or slower game may value the smoother path. Enable interpolation for a controlled test, then compare jump timing, edge correction and camera response rather than judging only a static scene.
Changing the physics tick rate
Godot documents 60 physics ticks per second as the default in its 4.6 engine reference. Raising the rate can improve responsiveness or simulation accuracy for some projects, but every extra tick increases CPU work. Do not raise it simply because the monitor has a high refresh rate. First establish that the simulation rate is the source of the artifact, then test a new rate with a profiler and the game’s deterministic behavior in mind. If the new rate does not align with the monitor, interpolation may help the rendered result, while the latency and CPU costs still need evaluation.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Diagnose GPU and CPU limits before lowering visual quality
Use a window-size comparison for fill-rate limits
A large window makes the GPU shade and write more pixels. Godot’s GPU optimization guide states that you can test whether a project is fill-rate-limited by comparing frame rates at a large window size and at a very small one. For context, the guide contrasts 4K’s 8,294,400 pixels with 640 × 480’s 307,200 pixels—27 times as many pixels—not as a platformer benchmark, but as an illustration of why resolution changes can expose GPU work.
- Temporarily turn V-Sync off for the diagnostic comparison so the display’s synchronization does not conceal the measured difference. This is a test, not a recommended gameplay default.
- Run the same busy scene in a large window and record the frame rate or frame time.
- Resize to a very small window without changing the scene, effects or simulation, and record it again.
- If the small window produces a substantial improvement, the project is at least partly fill-rate-limited. Reduce GPU work such as shader complexity, overdraw-heavy effects or excessive texture use, then repeat the comparison.
- If FPS barely changes, the bottleneck is more likely CPU-side, simulation-side, synchronization-related or otherwise independent of pixel count. Use the engine profiler instead of lowering resolution blindly.
Restore the intended V-Sync and window mode after the test. A diagnostic result does not prove that one setting caused every hitch; it identifies which class of work deserves the next investigation.
Separate low FPS from intermittent stutter
Average FPS can hide a long frame. A game that renders 60 frames per second on average can still pause when one frame takes much longer than the others. Inspect frame-time graphs and CPU/GPU timelines while reproducing the event. If the CPU or GPU is saturated during the hitch, reduce or optimize the work on that side; if neither is busy, investigate synchronization, asset loading or engine-specific events.
Check for first-use shader compilation
Godot’s jitter and stutter documentation identifies first-use shader compilation as another source of brief pauses. It commonly appears the first time an effect, material or particle combination is seen, or after a driver update invalidates the shader cache. A pause that happens once when an effect first appears and is absent on a later run has a different remedy from a constant frame-rate shortfall.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Godot 4.4’s Forward+ and Mobile renderers use an ubershader approach intended to avoid some shader-compilation stutter. That is version- and renderer-specific; it does not mean every project or renderer is free of compilation hitches. When diagnosing a release, test a clean run and a repeat run, note whether a graphics-driver update preceded the change, and profile the first appearance of each major effect.
A practical tuning sequence
- Record the baseline. Note engine and version, display refresh rate, V-Sync mode, FPS cap, physics tick rate, renderer, resolution and the exact scene where the problem occurs.
- Classify the artifact. Decide whether it is tearing, steady jitter, intermittent stutter or genuinely low FPS. Use a frame-time graph if the distinction is unclear.
- Test synchronization. Toggle V-Sync once, reproduce the same camera movement and compare tearing, frame pacing and control latency. Do not leave V-Sync off merely because it was needed for a fill-rate test.
- Test timing. If motion is uneven at a stable frame rate, check whether physics and render updates are mixed. Test interpolation and assess its effect on control response.
- Profile before reducing quality. Compare window sizes for a fill-rate clue, then inspect CPU and GPU timings. Lower shader or texture workload only when the profile points to that work.
- Set a sustainable cap. Choose the highest target the busy scene can hold consistently, taking the display’s refresh and any VRR guidance into account.
- Retest the worst case. Verify scrolling, rapid direction changes, jump arcs, moving platforms, particles and the first appearance of major effects. A menu result is not sufficient.
Common mistakes and safer alternatives
- “My FPS is 60, so the game cannot be jittering.” Average FPS does not reveal physics/render timing mismatch or long individual frames. Check frame time and update domains.
- “Turn V-Sync off for less lag.” This may introduce tearing, and the documented latency advantage in Godot’s GPU-limited case does not apply when the CPU is limiting performance. Test both modes on the target display.
- “Raise physics ticks to match a 144-Hz monitor.” A higher tick rate costs CPU and may not solve a rendering mismatch. Establish the cause first; use interpolation only after considering its latency effect.
- “Use an unlimited frame rate for the smoothest result.” Uncapped rendering can waste power and produce inconsistent pacing. A stable, reachable cap is often easier to control.
- “Lower every quality setting when a hitch appears.” First-use shader compilation, CPU stalls and synchronization problems will not necessarily improve when texture quality is reduced. Identify the busy timeline or reproduce the first-use event.
- “Assume an engine rule applies everywhere.” Godot’s V-Sync and interpolation behavior and Unity’s
vSyncCount/targetFrameRateinteraction are engine- and platform-specific. Apply the rule for the engine and platform you are shipping.
Recommended starting profiles
| Situation | Starting configuration | What to verify |
|---|---|---|
| Tearing on a fixed-refresh desktop display | Enable V-Sync; choose a cap that the busy scene can sustain if the engine still applies one. | Check that tearing is gone and that input remains acceptable. |
| VRR display with Godot | Keep V-Sync enabled and start with a cap just below the maximum, such as Godot’s documented 58/60, 115/120 or 138/144 examples. | Confirm the display remains in its VRR range and the game holds the cap. |
| Steady-FPS shaking | Leave image-quality settings alone initially; inspect physics/render update domains and test interpolation. | Compare camera, player and moving-platform motion, then measure any added control latency. |
| Low FPS that improves in a small window | Keep synchronization changes temporary for diagnosis; reduce shader complexity, texture work or other GPU cost. | Repeat the large/small-window test and confirm the busy scene reaches its target. |
| One-time pause when an effect first appears | Profile shader compilation and test a repeat run before changing caps or physics. | Check whether the hitch returns after a driver update or shader-cache invalidation. |
The most reliable setting is the one that matches the measured cause: synchronize when the problem is tearing, align or interpolate timing when the problem is jitter, optimize the limiting CPU/GPU work when frame time is too long, and treat first-use shader pauses as a compilation path rather than a generic FPS failure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
