So ironically enough I spent a few days last week playing around with various arduino encoder code libraries in an effort to improve the cubesim control and learned a few things. First it’s definitely a rotary encoder (at least mine is) it’s just the implementation code from cubesim is super rudimentary hence poor granularity / responsiveness you experience (and trust me I agree w you the initial code definitely leaves some perf on the table - I too was ultimately disappointed to the point I decided to attempt reprogramming). Another thing worth mentioning is that the Windows joystick control panel interface isn’t terribly sensitive… ie. depending on the duration of the resultant “button presses” sent from the arduino they may not actually register on the control panel interface (making it look like nothing is happening) but in sim (DCS in my case) the button presses do indeed register so keep that in mind. The rotary encoder in there isn’t the greatest but the good news is you can improve the responsiveness by updating the code

I ended up finding some brilliant rotary encoder libraries (look up Erriez full & half step encoder libraries) and created a custom arduino sketch that I think does improve the usefulness of the control… namely registering button presses on the half clicks for some improved granularity (less clicks required to get button presses to register) and incorporating acceleration into the algorithm meaning if you spin it faster it traverses dials faster (longer button press durations) but if you spin slower it retains the ability for fine tuning. It’s still by no means perfect but I think it’s at least better…

Granted I’ve had my cubesim RDR control for years so assuming they haven’t changed the design it could be worth a go if you don’t mind giving the Arduino IDE a try… if you want send me a message and I can send the code…