This seems to be a rare issue with the input system I'm using that only occurs in certain environments. I unfortunately may not have a quick fix for it, but can you provide your PC specifications and operating system? I can try to submit a help request to Unity.

Sure, here's a summary:
- Device name: ROG-Zephyrus-G14
- Processor: AMD Ryzen 9 4900HS with Radeon Graphics 3.00 GHz
- Installed RAM: 16,0 GB
- Device ID: 9FC556A0-9DB6-44C6-8DAD-7C8834DFABD9
- Product ID: 00325-81989-70641-AAOEM
- OS: Windows 11 (x64)

If you need other infos, just let me know, and thank you very much <3

P.S. = sadly the newest small patch didn't fix the issue for me, oof T - T

Update: after some further testing, I think I get what a possible problem might be, and it might be a "mechanical reason". For how PS controllers are made, unlike the action (shape) buttons, the d-pad is a single block of buttons that tilts in the direction of the button you're pressing, and if the sensitivity/calibration is not properly set, it might cause the game to be confused as to if you're pressing a direction or one of the 2 adjacent ones. There's a chance that when an input is ignored is because it simultaneously sees them as 2 and it doesn't know which one you actually intended to input, thus it might not react to it. Just an example: to prove this , I verified that if you press the "upper part" of the left-button, it recognises that as an up-button press, thus navigating up (same applies to all other d-pad buttons). Seeing you said that you're using a particular input system, it might have something to do with threshold values (just assuming, I have no programming expertise). I hope this helps somehow to figure out the correct adjustments for the game ^~^;

Thank you for the info!
One question, does this issue only occur when navigating menus, or does it occur in gameplay as well with buttons and circle pads?

I just tried going to the Training Grounds to run some intensive tests without being bothered by enemy attacks, and after 5 minutes of inputting I can confirm that the gameplay inputs work just fine, it never missed/misinterpreted once, both with d-pad and action pad, so it's really just happening in navigation (and that includes every possible menu, from title screen to main menu and pause menu)

Thank you! I'll let you know if I find out anything