I've just received my FM3 (with 1.06 on it from Fractal), and I'm noticing that the on-device UI is really sluggish to respond to inputs intermittently, and occasionally overreacts to the inputs that were made while it was being unresponsive.
For instance, sometimes when pressing the nav buttons it responds fairly quickly (i.e., within 100ms. Not immediate, but similar to the AXE FX III). but other times it takes longer to respond to the inputs. It seems to me that the UI thread is getting blocked by some sort of longer-running background task and it can't process the inputs and redraw the UI until that task completes. The Axe FX III is rock solid in this regard unless you've got >80% CPU usage and the UI thread is getting starved.
This is a minor annoyance but doesn't severely impede usability.
More frustrating is sometimes when the UI thread appears to be stuck unable to process the input, it eventually catches up and processes that same input too many times. In the video linked below, I am on the Djentlmanly factory preset, unmodified. (It's around 50% CPU usage so that shouldn't be the cause). I click the nav down button twice (you can hear in the video to confirm), but it responds by executing at least 7 down movements, switching me from scene 1 to scene 8. I've experienced this same sort of jumping ahead/multiple reaction behaviour with Value knob as well, both navigating system menus and adjusting values.
To continue blindly speculating on the cause, I wonder if when the UI thread is not active some other process is handling the inputs from the buttons to add them to a queue to be processed. Then when the UI thread gets back to it they are executed. I wonder if there could be any bugs where the code adding them to this queue are not clearing the event from the source and then sometimes repeatedly adding them as events to be processed multiple times for each real event.
I also wondered if the knob acceleration could be partly at play: if the nav buttons are being accelerated when they shouldn't be. However, I've tested this with single nav presses with plenty of time between and sometimes a nav up or nav down gets executed twice when it was the only button hit in that period of time. I've had this happen with single key presses, ruling out any acceleration issues.
Is anyone else experiencing this, or is it just me? I think next I will try a full system reset (despite it being factory fresh from fractal) if others aren't experiencing this.
For instance, sometimes when pressing the nav buttons it responds fairly quickly (i.e., within 100ms. Not immediate, but similar to the AXE FX III). but other times it takes longer to respond to the inputs. It seems to me that the UI thread is getting blocked by some sort of longer-running background task and it can't process the inputs and redraw the UI until that task completes. The Axe FX III is rock solid in this regard unless you've got >80% CPU usage and the UI thread is getting starved.
This is a minor annoyance but doesn't severely impede usability.
More frustrating is sometimes when the UI thread appears to be stuck unable to process the input, it eventually catches up and processes that same input too many times. In the video linked below, I am on the Djentlmanly factory preset, unmodified. (It's around 50% CPU usage so that shouldn't be the cause). I click the nav down button twice (you can hear in the video to confirm), but it responds by executing at least 7 down movements, switching me from scene 1 to scene 8. I've experienced this same sort of jumping ahead/multiple reaction behaviour with Value knob as well, both navigating system menus and adjusting values.
To continue blindly speculating on the cause, I wonder if when the UI thread is not active some other process is handling the inputs from the buttons to add them to a queue to be processed. Then when the UI thread gets back to it they are executed. I wonder if there could be any bugs where the code adding them to this queue are not clearing the event from the source and then sometimes repeatedly adding them as events to be processed multiple times for each real event.
Is anyone else experiencing this, or is it just me? I think next I will try a full system reset (despite it being factory fresh from fractal) if others aren't experiencing this.
Last edited: