Noticed since it kept causing consistent frametime spikes in a game I was playing. Happens regardless of how complex the command is, and the frametime spike occurs at the interval set for re-running the command. If executor was inhibited when it's not visible (i.e. a fullscreen app) it could at least be circumvented.
Noticed since it kept causing consistent frametime spikes in a game I was playing. Happens regardless of how complex the command is, and the frametime spike occurs at the interval set for re-running the command. If executor was inhibited when it's not visible (i.e. a fullscreen app) it could at least be circumvented.