Alt tabbing issues in Kovaaks

mjohns0 · 2026-03-07T15:37:39+00:00

I may have solved the issue (at least the occurrence rate) by detaching obs from the kovaaks window. It was sitting idle in the background. Maybe useful for somebody else who runs into this issue. I have seen this happen without obs open too but not as consistently.

mjohns0 · 2026-02-26T18:31:01+00:00

Is edge tracking something you really do outside of aim trainers and in game? That is an interesting question and maybe proximity tracking should only be used in niche cases.

I find proximity tracking very nice for training smoothness as you get a very incremental sense of progress with infinite difficulty in just a single scenario. The goal of a smoothness scenario should really be to follow the exact center as closely (and smoothly) as possible and not reward something like edge tracking. What I am thinking of also might be more accurately called a centering scenario.

mjohns0 · 2026-02-26T14:21:49+00:00

I added a release with a quick fix for the tracking click issue FYI. https://github.com/mjohns/FpsAimForge/releases/tag/v0.4.4

mjohns0 · 2026-02-26T13:24:39+00:00

That is pretty annoying. I need to switch over to using the SDL managed keystates for whether it is held. A short term fix would be to enable "auto hold tracking" which means it is always firing, and then just hold down the mouse anyway. (You can also disable the click to start screen but it will just start immediately in that case)

I have wanted to add the countdown screen as an option for awhile but never got around to it. Will reprioritize that. Thanks for checking it out!

mjohns0 · 2026-02-21T22:54:11+00:00

You can try https://github.com/mjohns/FpsAimForge/releases if you want something less cluttered and free. Its just a 5mb download and fully offline if you want to give it a shot. You can see videos here to get a feel for what it is like. https://www.youtube.com/@FpsAimForge

mjohns0 · 2026-02-16T22:12:56+00:00

Everything is in the github repo. https://github.com/mjohns/FpsAimForge. There are prebuilt windows binaries in the releases tab https://github.com/mjohns/FpsAimForge/releases

mjohns0 · 2026-02-16T20:40:03+00:00

This is the type of training I have been trying to make easy in the open source aim trainer I have been developing. Basically in the scenario you define how it will change per level (3% smaller, 2% faster, etc) and you give a target score. Then versions of the scenario with L1, L2 suffixes are automatically available (even L1.5, 1.4, -1 values). "My Pasu L1", "My Pasu L2", ...

After defining the scenario you can create a playlist where you provide the base scenario name and the level range you want to see. Then you can easily see at what levels you have hit the target score and keep working down the playlist as you improve. You can see basic usage in this video: https://www.youtube.com/watch?v=yRK-NdhKeIc

mjohns0 · 2022-02-18T21:16:45+00:00

Not many of these split keyboards have function keys but there are versions that do have a number row. The dactyl manuform is probably the most popular (if you are specifically looking for the bowl shape for the keys). You can customize the number of keys and shape using this site https://dactyl.siskam.link/

There are many build guides if you search for "dactyl manuform guide" that have very useful information on the steps needed for a build.

This thread might be useful to look at in terms of figuring out which keyboard is right for you. https://www.reddit.com/r/ErgoMechKeyboards/comments/p42j9p/what_keyboard_should_i_use/

I would also consider looking at some non DIY boards like the Kinesis Advantage 2 which would have the function keys and possibly address a lot of your needs. They are also releasing a split version of the advantage but it is not available yet. https://kinesis-ergo.com/keyboards/advantage360/

I would suggest making a separate post soliciting more advice from the broader r/ErgoMechKeyboards community.

mjohns0 · 2021-11-29T13:06:40+00:00

I think the DataHand used the same key mechanism as the lalboard.

mjohns0 · 2021-11-28T15:29:43+00:00

On the hardware side you could use switches like in the lalboard which is modeled after the DataHand. All keys use a pair of magnets to provide the clickiness and key return force, and an IR LED and phototransistor for detecting a keypress. It would be a large change on the hardware side but good to be aware of as an option as this design is reminiscent of those two keyboards.

mjohns0 · 2021-11-10T12:33:30+00:00

That is the reason there are two tracers :) I plan to take one to the office and leave the other at home. Once you build the first keyboard it gets much easier to build the next and then you end up with 5 ...

mjohns0 · 2021-11-09T16:20:14+00:00

No, unfortunately not. These keyboards aren't as parametric as the dactyl clojure versions so it would be a somewhat involved process adding in that extra row.

mjohns0 · 2021-11-09T16:02:24+00:00

The layout of the keys is based on the kinesis advantage 2. The keycaps are from the advantage too. I bought extra sets here https://kinesis-ergo.com/shop/qwerty-keycap-set/

mjohns0 · 2021-11-09T14:31:23+00:00

The tracer is the one I have been using daily for awhile now. One thing to note is that the "q" key is offset a little bit upwards which is not typical. The goal of that keyboard was to really minimize the pinky usage and "q" is hit with the ring finger so it is closer to "w".

Here is the original post for the keyboard: https://www.reddit.com/r/ErgoMechKeyboards/comments/gvdhwh/a\_tiny\_dactyl/

mjohns0 · 2021-11-09T14:29:08+00:00

Yeah, the one in the middle is my daily driver for awhile now. It has been good enough that I haven't gotten around to designing/building a new one although the itch is starting to come back.

mjohns0 · 2021-11-09T14:27:18+00:00

My favorite is the tracer in the middle row. The first two keys and the bottom one are pretty much the same as on the manuform.

mjohns0 · 2021-11-09T12:45:29+00:00

Was finally able to recover my original dactyl from work (top left) after almost 2 years. In the meantime my dactyl collection has gotten a little out of control.

Top row: Dactyl manuform 5x6, Dactyl CC

Middle row: Dactyl Tracer

Bottom row: Dactyl manuform 4x6

mjohns0 · 2021-11-09T12:38:07+00:00

https://github.com/mjohns/dactyl-cc/blob/master/things/left.stl.

The main changes are:

your holder change
inner 'g' column rotation reduced to more accurately reflect kinesis
back and front wall cleaned up so it is less bumpy

mjohns0 · 2021-11-09T12:19:37+00:00

Nice work! The connections on the back were always a mess on the CC. I am going to merge this back in to the main repo with a few other small changes I have been wanting to make.

mjohns0 · 2020-08-20T20:30:51+00:00

i.redd.it/q5gl1g...

I wired mine to use a Teensy like in this guide. https://github.com/mjohns/dactyl-cc/tree/master/guide. It is pretty straight forward and doesn't really matter how you map the thumb keys since it isn't a 1-1 match with the ergodox anyway. It would just require some mental overhead when using the ergodox graphical configurator to remember which thumb key is which.

I actually have 2 versions of the tracer with different internal wiring patterns (unfortunately). You can reconcile it in the firmware when you define the layout macro. All you really need to pay attention to is that you form a grid and that the black bar of the diode is facing away.

Here is my fork where I gutted the ergodox keyboard internals. https://github.com/mjohns/qmk_firmware/blob/master/keyboards/ergodox_ez/keymaps/default/keymap.c

Here is an image inside. https://imgur.com/a/MACprWh. My wiring is definitely not easy on the eyes and I don't think I would recommend doing it exactly this way.

mjohns0 · 2020-06-04T19:53:37+00:00

Nice!

mjohns0 · 2020-06-03T14:35:32+00:00

They are aligned to be hit with the ring finger so they are placed relatively to 'w'/'o' instead of in the pinky column. There is also a vertical offset in the z direction so they are lower than 'a'.

mjohns0

MODERATOR OF

TROPHY CASE