Ah ok got you, I’ve changed it back now.

Do you have any idea why this might be happening?

The joystick recognises UP correctly and just for the duration it’s pushed upwards.

When pushed to the LEFT, it reads left but continuously goes left even when released.

When pushed DOWN, it triggers left and down and continuously goes left and down even when released (when slowwwwwly pushed down, it reads left first, then down)

when pushed to the RIGHT, nothing is recognised (when pushed up first then rolled over to the right, it recognises up and right/right once - inconsistent but most of the time it’s up and right, not just right)

I’ve actually got all the code to work now except the joystick part, which is the biggest (new) part for me for this keeb. I’ve been on the QMK discord (that’s how I knew to update QMK to resolve QK_BOOT haha, although I’m not entirely sure the combo works…) What do you mean read the joystick input pins once per scan instead of in every if statement?

edit: yeah config_common is deprecated according to the QMK discord. very unfortunately I actually have no idea what I’m doing with QMK/C++ code (esp the joystick part) in general and have just been kinda sticking things I’ve found on the internet in in hopes of something working out but no luck so far

I’ve tried to rewrite the joystick code and now am getting different errors:

Compiling: quantum/keymap_introspection.c                                                           [OK]
Compiling: quantum/command.c                                                                        [OK]
Compiling: tmk_core/protocol/host.c                                                                tmk_core/protocol/host.c: In function 'host_joystick_send':
tmk_core/protocol/host.c:171:10: error: 'report_joystick_t' {aka 'struct '} has no member named 'axes'
         .axes =
          ^~~~
tmk_core/protocol/host.c:172:13: error: extra brace group at end of initializer
             {
             ^
tmk_core/protocol/host.c:172:13: note: (near initialization for 'report')
tmk_core/protocol/host.c:172:13: error: excess elements in struct initializer [-Werror]
tmk_core/protocol/host.c:172:13: note: (near initialization for 'report')
cc1: all warnings being treated as errors
 [ERRORS]
 | 
 | 
 | 
gmake[1]: *** [builddefs/common_rules.mk:361: .build/obj_eiris_default/protocol/host.o] Error 1
gmake: *** [Makefile:392: eiris:default] Error 1
Make finished with errors

Also, I’m not sure if I need "#include “config_common.h” in my config.h file? I see it in some other config.h files. When I have that in my config.h file, it gives a fatal error: No such file or directory

Yep. QK_BOOT error was resolved after I updated, now it’s just left with the joystick error. I’ve also uploaded rules.mk to the drive link

Yes there’s one extra column on the left.

I’d spotted that error but forgot to update the Google drive after updating the .h file. I’ll try adding no pin!

Thank you!

Edit: that solved the LAYOUT errors!

Now it’s just the QK_BOOT and joystick code errors

Yes I spotted that error and made it 7 but forgot to update the Google drive! 😅

1. Hot glue
2. Yes it’s fine I exclusively use AliExpress knock off usb c pro micros

Thank you! I’ve saved your comment for future use :)

Creating from scratch! I’ve posted some of the things I’ve made here: https://www.reddit.com/user/_denton

I haven’t started experimenting around with the code for joysticks but am in the middle of making a keyboard (half) with a joystick. Did you find it worked ok just for acting as keyboard keys/combinations of keys?

I see under the ‘Accelerated’ portion where you tried to emulate mouse keys there weren’t really any results?

If you’re talking about long term working out, motivation will not cut it. It has to be determination/making it a habit. Like - “Time to take a shower”, “time to workout”.

But working out doesn’t mean you have to push yourself till you feel like puking. Start small, do 10 squats at lunch and another 10 when you finish your work day for e.g… Do something you find fun, not something that’s just “well running is exercise so I guess I have to do that”