So your experience joystick "pile up" ? - and the pileup occurs on the json going back to the webgui ?
The amount of changing display data is really "not that much" as far as the graphics - 5 lines to redraw right? Perhaps the numerical data / logging is overloading it ? I had a similar issue with the Arduino oscope - initially I thought it was the traces, but it turned out that I had subscribed to much more than was needed to the display. I susbcribed to every byte, every codec converted byte, and to graph data :P Once I removed the subscriptions I did not need, performance was better.
this is very interesting!
this is very interesting! Good work
Fantastic
Got to see it with audio ... Awesome !
So your experience joystick "pile up" ? - and the pileup occurs on the json going back to the webgui ?
The amount of changing display data is really "not that much" as far as the graphics - 5 lines to redraw right? Perhaps the numerical data / logging is overloading it ? I had a similar issue with the Arduino oscope - initially I thought it was the traces, but it turned out that I had subscribed to much more than was needed to the display. I susbcribed to every byte, every codec converted byte, and to graph data :P Once I removed the subscriptions I did not need, performance was better.
Really nice to see these updates kwatters !