Thanks for responding. I tried what you suggested. No other blueprints anywhere are using that input action event… just the one on my character blueprint. Nothing in the editor bindings that seems like it would interfere.
I even connected a print string to a “D” keyboard input to see if it would do anything and nothing.
However, D will work if I am just navigating the viewport, but as soon as I play the level in the viewport or as standalone it’s like my “D” key goes dead.
I mapped another key to my strafe right just to see and it worked fine. When I play my level, the D key just doesn’t work. So weird.
The good news is that I am just getting done putting my game’s initial template together where I make sure that all the mechanics are working like they should. It would be pretty easy to just start over and put it all back together in a fresh project.
However, it bothers me not knowing what caused this. I’d hate for it to crop up later in development. It’s just bizarre.