Jump to content
Report an Alpha 21 Bug!

  • Mouse Movement of Any Kind Causes Graphical Stuttering After ~30 Minutes of Playtime

    Kanten

    By Kanten

      • Version: A21.1 (b16)
     Share

    Recently, a seemingly unavoidable gameplay-impacting issue has begun coming up any time when playing 7DTD. After roughly 30 minutes, the game will find itself in a state where the very *movement* of the mouse causes a plummet in performance and causes the game to stutter. It does not matter when, where, or is it done, moving the mouse *will* stutter the game graphically. This goes so far as even causing stuttering in a static menu just from the cursor being moved. Switching over to a controller causes no similar drops in performance, it is only mouse movement that impacts the performance of the game. Lowering, changing settings or the native input module does nothing to resolve the issue, only a hard restart of the game once the issue begins will restore performance.

     

    Log: https://pastebin.com/tA9xT4eK

    A previous Reddit thread of the issue with additional detail.

     

     

    Video of the Stutter Issue (note the torch in the last section): 

     

     

    0
     Share
    Go to records

    User Feedback

    Recommended Comments

    Jugginator

    Can't say I've seen or heard of this one...

     

    I can try to see if I can spot something in the profiler, but if I can't reproduce it, it may not show much. Have you tried the Use Native Input Module in the game launcher? Fullscreen/exclusive/windowed? What mouse do you have, and what DPI is it set to, also if you can find it, the polling rate.

    Link to comment
    Share on other sites
    Kanten

    I've tried native input on and off, fullscreen and borderless, the issue inevitably crops up on any combination of those configurations in my experience.

     

    I'm using a Logitech MX518 (2019 version), running most often at 1600 DPI and a 1000 Hz polling rate.

    Link to comment
    Share on other sites
    Jugginator

    I'm really hoping that it was a bad driver from Nvidia, they were battling that for some time and it should be resolved by now with the newest-updates. Just to make sure, I tried replicating it one last time. 

     

    If you still have the issue, do respond back here though.

    Link to comment
    Share on other sites


    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...