You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've plugged my e drum and soon found there's huge noticable input delay in VSync mode.
There's a workaround currently suggested by the wiki that you can turn VSync off.
The lag disappears, but the new problem came in: unsmooth score scroll and an unreasonable high fps, usually around 1000 - 2000.
It made my laptop super hot.
So I want to discuss a solution with contributors.
My thought
When working on metronome #160 , I noticed an issue that the overall app do all the job in "draw", including polling and handling input.
As we know that there's another callback named "update" provided by FDK. In VSync mode, FDK would continous call "update" when waiting sync signal, so we have more frequent polling rate if we put input polling and handing in "update" than in "draw". So that we can achieve both an in-time input handling and a smooth scroll.
I know this is a big refactor that can impact lot of existing function and plans. So I'd like to discuss the possibility here. Thanks
Problem
I've plugged my e drum and soon found there's huge noticable input delay in VSync mode.
There's a workaround currently suggested by the wiki that you can turn VSync off.
The lag disappears, but the new problem came in: unsmooth score scroll and an unreasonable high fps, usually around 1000 - 2000.
It made my laptop super hot.
So I want to discuss a solution with contributors.
My thought
When working on metronome #160 , I noticed an issue that the overall app do all the job in "draw", including polling and handling input.
As we know that there's another callback named "update" provided by FDK. In VSync mode, FDK would continous call "update" when waiting sync signal, so we have more frequent polling rate if we put input polling and handing in "update" than in "draw". So that we can achieve both an in-time input handling and a smooth scroll.
I know this is a big refactor that can impact lot of existing function and plans. So I'd like to discuss the possibility here. Thanks
@limyz @ericpignet @fisyher @approvedtx @aoki-marika @987123879113
The text was updated successfully, but these errors were encountered: