(2017-06-11, 01:00)garbear Wrote: What do you think about this idea: Instead of leaving unused buttons ignored, we can double-map them to virtual features. For example, when emulating a SNES controler, both the D-pad and left analog stick can control the player. In a N64 or Genesis game, the physical Start and Back buttons would both map to the virtual Start button. In math terms, this would be called a surjective button map.

(2017-06-12, 16:03)OmniBlade Wrote: When you talk of people not all that familiar with emulation and then worrying how they will struggle to map something like a genesis controller, the intersection of people that are both unfamiliar with emulators and plugged a genesis controller into their kodi box is surely going to be vanishingly small. Most people unfamiliar with emulation are probably going to plug their xbox or PS3/4 controller in and they have guide buttons that can be mapped and will behave pretty much like it does on an xbox/playstation. Anyone else can probably live with the shortcomings of button combos as I would expect them to be preferred over anything that increases input latency like waiting to decide if there was just a push or a hold.

(2017-06-12, 20:48)garbear Wrote: I could see Genesis controllers being popular in the DIY community though, so I could create a solution friendly to common controllers with more advanced emulation options for the power users.

(2017-06-14, 15:56)cmiller1 Wrote: Question for garbear, if the final solution for this ends up increasing input latency, how difficult would it be to make sure that it can be completely turned off with a setting?

(2017-06-14, 15:56)cmiller1 Wrote: Question for garbear, if the final solution for this ends up increasing input latency, how difficult would it be to make sure that it can be completely turned off with a setting?

• None
  
• Down + L1 + R1 + Y
  
• L3 + R3
  
• L1 + R1 + Start + Select
  
• Start + Select
  

(2017-06-15, 13:24)cmiller1 Wrote: The people that want to operate everything with a gamepad seem to be people looking at this as an alternative to solutions like EmulationStation for playing games on your TV, but I feel like a lot of Kodi users are like me, they've set up boxes to run Kodi on their TV that are controlled by IR remotes or remotely through HTTP and are just looking at this as a way to add gaming to those existing boxes.

(2017-06-15, 23:29)garbear Wrote:

(2017-06-15, 13:24)cmiller1 Wrote: The people that want to operate everything with a gamepad seem to be people looking at this as an alternative to solutions like EmulationStation for playing games on your TV, but I feel like a lot of Kodi users are like me, they've set up boxes to run Kodi on their TV that are controlled by IR remotes or remotely through HTTP and are just looking at this as a way to add gaming to those existing boxes.

I'm targeting both dedicated console and media center uses of Kodi. It sounds like for media center uses, button combos (or nothing) is the preferred option. For dedicated consoles with only Genesis controllers, holding start to bring up the menu is a possible solution.

To address both usecases, I'd like to create a set of input settings that lets the user customize their experience. I'm generating a list of all input settings and a list of all usecases. When I've completed both, I'll address settings fatigue by eliminating settings for the more niche usecases. I want to complete both lists before I make these decisions, so if you can think of any additional settings or usecases, let me know.

(2017-06-16, 01:26)zachmorris Wrote: Here's a devils advocate use case: Touch screen users. Kodi has touch screen support currently. Retroarch has touch screen overlay input support. Is this already planned, or is this just a potential limitation of the first iteration of Retroplayer?

(2017-06-15, 01:16)garbear Wrote: The interesting setting here is "Menu Toggle Gamepad Combo":



The options are:

• None
  
• Down + L1 + R1 + Y
  
• L3 + R3
  
• L1 + R1 + Start + Select
  
• Start + Select
  

Like Ferk said, all but the last button pressed in the combo will fall through to the game.

(2017-06-17, 11:17)Julipo Wrote: But is because I have this in the "Input Hotkeys bind" section:

(2017-06-17, 11:17)Julipo Wrote: When I click "select" it does the normal select action, it didn't ignores it until it decides if you are doing an action or a game input. It does the game input AND enable the hotkey input (until the key is unpressed, that disables the hotkey input). For example, I'm playing now a game that uses select to change the current player so every time that I click select to do a input hotkey it changes the player (because I clicked select, and then the hotkey)

(2017-06-17, 16:32)garbear Wrote: I count 34 binds in that section. This totally screams "keyboard". The problem is that we're targeting the living room, which usually doesn't have a keyboard. This means we have like 15 hotkeys, max, and even that stresses the goal of 10-foot display and remote-friendly.