You’re right that both KB and button/axis bindings are allowed simultaneously. I’ve tried binding the d-pad again so that I can get on with per-core configs like I wanted. However I’m still stumped as to why, with input_autodetect_enable = “false”, I can bind the d-pad in RGUI or manually and the d-pad will work fine in-game but not for navigating the RGUI menu. It works perfectly when using an autoconfig.cfg. This makes absolutely no sense to me. I’ve tried in both a June and July Win64 build.
Here’s the fully-working autoconfig file:
input_device = "USB Gamepad"
input_driver = "dinput"
input_b_btn = "1"
input_y_btn = "0"
input_start_btn = "8"
input_select_btn = "5"
input_up_axis = "-1"
input_down_axis = "+1"
input_left_axis = "-0"
input_right_axis = "+0"
input_a_btn = "2"
input_menu_toggle_btn = "6"
And here’s the retroarch.cfg bindings:
input_driver = "dinput"
input_device_p1 = "0"
input_player1_joypad_index = "1"
input_libretro_device_p1 = "1"
input_player1_analog_dpad_mode = "0"
...
input_player1_b = "z"
input_player1_b_btn = "1"
input_player1_b_axis = "nul"
input_player1_y = "a"
input_player1_y_btn = "0"
input_player1_y_axis = "nul"
input_player1_start = "enter"
input_player1_start_btn = "8"
input_player1_start_axis = "nul"
input_player1_select = "rshift"
input_player1_select_btn = "5"
input_player1_select_axis = "nul"
input_player1_up = "up"
input_player1_up_btn = "nul"
input_player1_up_axis = "-1"
input_player1_down = "down"
input_player1_down_btn = "nul"
input_player1_down_axis = "+1"
input_player1_left = "left"
input_player1_left_btn = "nul"
input_player1_left_axis = "-0"
input_player1_right = "right"
input_player1_right_btn = "nul"
input_player1_right_axis = "+0"
input_player1_a = "x"
input_player1_a_btn = "2"
input_player1_a_axis = "nul"
First works in RGUI and in-game, second works in RGUI except for axis assignments but they work perfectly in-game. input_player1_joypad_index = “1” is correct. What could the difference possibly be?