Tag: AutoPilot

  • Playing on PC Shouldn’t Feel Like Managing a System

    There’s a strange thing we’ve normalized in PC gaming.

    Before you actually play, you prepare.

    You open settings.
    You tweak graphics.
    You check performance overlays.
    You think about battery life, temperatures, profiles, limits.

    None of this feels unusual anymore. It’s just “part of PC gaming”.

    But it shouldn’t be.


    When playing became a task

    On consoles, you press a button and play.

    On PC, especially on modern handhelds, you make decisions first.

    Not because you want to, but because you feel responsible for the outcome.

    If performance isn’t great, it’s on you.
    If the battery drains too fast, it’s on you.
    If the experience stutters, you assume you missed a setting.

    Over time, playing starts to feel less like entertainment and more like system administration.

    And that’s the part that bothers me.


    Control is not the problem

    PC gaming has always been about control, and that’s a good thing.

    Being able to tweak, customize, and adapt is what makes the platform powerful.
    The problem isn’t having control.

    The problem is when control turns into constant responsibility.

    When every session begins with questions:

    • Should I change profiles?
    • Is this game using the right resolution?
    • Am I wasting performance or battery?
    • Do I need to adjust something before this feels right?

    At that point, you’re no longer just playing a game.
    You’re managing a system.


    Handhelds made this impossible to ignore

    This becomes especially clear on PC handhelds.

    These devices are meant for quick sessions.
    The couch. The bed. A break between things.

    They’re not desks.
    They’re not benchmarking stations.

    And yet, they inherit all the friction of desktop PC gaming, sometimes amplified.

    Small screens make bad settings more noticeable.
    Battery constraints make every choice feel important.
    Performance swings are harder to ignore.

    On a handheld, friction breaks immersion instantly.

    That’s where the system-management feeling becomes impossible to justify.


    If the user has to think, something failed

    This is where my mindset shifted.

    I don’t believe the solution is more options.
    I don’t believe it’s better overlays or more detailed graphs.

    Those tools are useful, but they’re still asking the user to think.

    My goal has been the opposite:

    The less the user has to touch, the better the system is doing its job.

    Good automation isn’t loud.
    Good automation doesn’t ask for attention.
    Good automation disappears.

    If you’re constantly aware of the tool helping you, it’s probably helping too much — or in the wrong way.


    Automation as respect

    Automation often gets framed as convenience.

    I see it as respect.

    Respect for the player’s time.
    Respect for their focus.
    Respect for the fact that they sat down to play, not to optimize.

    That doesn’t mean blind automation.
    It doesn’t mean guessing.
    It doesn’t mean “AI decided this is optimal”.

    It means being intentional about when the system should act, and when it should stay out of the way.

    Sometimes the best decision is doing nothing at all.


    A shared philosophy across different projects

    At a high level, Winhanced and ZenDeck aim for the same thing:
    a console-like gaming experience on Windows.

    The difference isn’t the goal, it’s the surface.

    Both act as launchers that detect games, and reduce friction so the system feels designed for playing instead of managing Windows.
    The UI changes. Some features change.
    The intent stays the same.

    As that ecosystem evolved, it became clear that automation itself needed to be split by responsibility.

    That’s where the AutoPilot suite started to take shape.

    AutoPilot – Dynamic TDP focuses on system-level behavior.
    It automatically adjusts power limits based on multiple runtime signals, similar in spirit to what Microsoft have recently introduced with Default Game Profiles, with one key difference: it works across all games from any store.

    It handles the kind of decisions that shouldn’t require constant user attention, regardless of where or how the game was launched.

    AutoPilot – Smart Profiles, previously known as AutoPilot+, operate at a different layer.
    Instead of touching the system, they focus on the game itself, managing in-game settings, resolution, and GPU features when required, based on how each title is actually configured.

    The names changed because the boundaries became clearer.

    One system adapts the device.
    The other adapts the game.

    Different layers.
    Different responsibilities.
    Same philosophy.

    Reduce friction, automate what makes sense, and let the player focus on playing.


    The goal isn’t peak numbers

    Another thing that often gets misunderstood is performance.

    Chasing the highest FPS or the longest battery life looks good on paper, but it rarely translates to a better experience.

    What actually matters is consistency.
    Stability.
    Predictability.

    A game that feels right beats one that wins benchmarks but constantly pulls your attention back to the system.

    That’s why I’m far more interested in removing unnecessary decisions than exposing every possible knob.


    Playing should feel simple again

    PC gaming doesn’t need to lose its flexibility.
    It doesn’t need to become locked down.

    But it does need to stop demanding so much mental effort just to feel good.

    If, before playing, you already feel like you’re managing variables, something went wrong upstream.

    Playing should feel like playing.

    Not like maintaining a system.
    Not like preparing a workload.
    Not like doing pre-flight checks.

    Just playing.

    That’s the experience I keep chasing, and the reason I care so much about making the system disappear when it’s doing its job right.

    Follow-up:
    I’ve written a follow-up post explaining how AutoPilot Smart Profiles attempt to solve this problem in practice.

    Read: AutoPilot Smart Profiles Automatically Optimize Games for PC Handhelds

  • Why I built AutoPilot+ (and why PC handheld gaming still feels harder than it should)

    I grew up playing on consoles.

    You turn them on, pick a game, and play.

    That expectation never really left me.

    So when I bought my first PC handheld, a Lenovo Legion Go in mid‑2024, I was genuinely excited… and then quickly overwhelmed.

    Not because the hardware was bad.

    But because everything required decisions.


    The problem I ran into (and kept running into)

    Before I could actually play, I had to think about:

    • In‑game graphics presets
    • In-game resolution vs screen resolution
    • TDP values
    • Refresh rate
    • Scaling (RSR, FSR, in‑game upscalers)
    • Driver‑level GPU features (AFMF, RSR, etc.)

    Every game.
    Every device.
    Every time.

    And the worst part?

    The same game behaved very differently on different handhelds.

    A config that felt smooth on a Legion Go could stutter on a ROG Ally.
    A preset that worked on one device destroyed battery life on another.

    So I did what most PC gamers do:

    I tweaked.
    I tested.
    I retested.
    I took notes.

    Eventually I realized something important:

    The hard part wasn’t performance.
    The hard part was knowing what to change, when, and why.

    That’s the problem AutoPilot+ exists to solve.


    What AutoPilot+ is

    AutoPilot+ is not a magic performance booster.

    It’s a system that applies in-game configuration before the game even starts.

    When you launch a supported game, AutoPilot+:

    • Detects the handheld you’re using
    • Applies the most appropriate in-game settings from the available options
    • Adjusts display resolution when needed
    • Enables or avoids AMD GPU features like RSR or AFMF based on whether their requirements are met

    Some driver-level features like RSR or AFMF only work correctly when both in-game settings and device settings are aligned. AutoPilot+ takes that relationship into account.

    The goal is simple:

    Launch the game already in a playable state that makes sense for the device.

    Not perfect.
    Not ultra.

    Playable.


    What AutoPilot+ does today

    Right now, AutoPilot+:

    • Supports a limited list of games
    • Uses game‑specific configuration logic (not generic presets)
    • Applies settings only when they are stored in plain text or deterministic locations
    • Adjusts resolution and GPU features based on the game’s actual configuration

    This is intentional.

    Each supported game is added manually, tested manually, and validated manually.

    No guessing.
    No auto‑benchmarking.
    No “AI decided this is optimal” claims.


    What AutoPilot+ does NOT do (and why that matters)

    This part is important.

    AutoPilot+ does not:

    • Tune every game on your system
    • Guarantee max FPS or best battery life
    • Replace user choice
    • Apply settings blindly

    If a game isn’t supported, AutoPilot+ stays out of the way.

    That restraint is deliberate.


    Why this isn’t just another “optimizer”

    Most PC optimization tools focus on hardware knobs:

    • TDP up / down
    • FPS limits
    • System‑level tweaks

    Those matter, and ZenDeck’s AutoPilot already handles a lot of that.

    AutoPilot+ exists because:

    Performance problems often start inside the game settings, not the hardware.

    If a game is rendering at an unreasonable resolution or using settings that don’t fit the device, no amount of TDP tuning will fix the experience.


    What comes next

    AutoPilot+ is intentionally built as a foundation.

    The long‑term vision includes:

    • Community‑shared profiles with device-specific variants and community feedback
    • Quality vs performance paths

    No black boxes.
    No locked presets.

    If you understand the system, you can extend it.


    Why I’m writing this now

    This post isn’t a launch announcement.

    It’s an anchor.

    Something I can link to when people ask:

    • Why does this exist?
    • What problem are you actually solving?
    • Why isn’t this open to every game yet?

    PC handheld gaming doesn’t need to be this hard.

    Until it isn’t, AutoPilot+ is my attempt to make it a little less exhausting.


    AutoPilot+ is part of the ZenDeck project and can be tried through ZenDeck.