-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The quest for the perfect ploopy A trackball with good internals? Yes please. I have never liked the explorer shape so Here we are with me trying to find the right one. Making progress on the shape... So a bit more contouring to go to get it to fit just right. However, of course NOW I decide I need a wedge, so I do not want to sculpt any further until I have one. It already feels improved. Flashing with QMK SYS. I only mention it first as it happened before playing with RawAccel. I will get back to it. RawAccel What is it? Customizable acceleration without the usual bloatware. https://github.com/a1xd/rawaccel/releases/tag/v1.6.0 I do leave on 'Enhanced Pointer Precision' in Windows 10 advanced mouse settings. I think the 'Motivity' curve is ideal for trackballs. So one of the things somebody mentioned about RawAccel was the idea of taking a high DPI and using a sens multiplier to make it 'seem' like a more typical DPI, such as 800 or 1600. Along those lines I tried various settings but what I settled on was this... Flash the DPI settings of { 6000, 12000 } in RawAccel us Sens Multiplier of 0.135 Now the DPI's are effectively ( 810, 1620 ) The reason for the high DPI is smoothness. That was the theory anyhow, and it seems pretty good to me. I did tinker with the Growth Rate (of Motivity) at 2, but I think the default 1.5 will probably be the best for my purposes - it will take in game hours to tell for sure. Other Settings and numbers... { 800, 12000 } 0.1 sens multiplier for effective 80 lol and 1200 { 3000, 6000, 12000 } 0.27 sens effectively ( 810, 1620, 3240)
QMK SYS and me. It's like Roger and Me, except it ends well. Yeha, QMK toolbox? nope. dfu-programmer -nope. Just QMK SYS. https://msys.qmk.fm/ After farting around I eventually found a link with 3 lines to type in the QMK SYS box in order to upgrade QMK. This may not be needed, but I did not know that then. That's all and good, but I did not have the ploopyco/trackball_thumb directory! https://github.com/ploopyco/qmk-firmware-ploopyco-dev/blob/ploopyco/thumb/keyboards/ploopyco/trackball\_thumb/trackball\_thumb.c#L34 Yes this is the only file I actually changed, and only the DPI 's on line 34. But to be sure I manually copied everydirectory and file in the trackball_thumb folder. Yes, too lazy to git good. AND THEN I get this QMK error (except I have newer QMK firmware) QMK Firmware 0.13.16 0 [] make 9468 cygwin_exception::open_stackdumpfile: Dumping stack trace to make.exe.stackdump ☒ Invalid return_code: 35584 And the consensus seemed to be 'too many keyboards'. so I deleted every keyboard except planck, ploopy and pluckey and ... it compiled, took a few seconds. qmk compile -kb -km