2015-03-19, 18:43
That has clarified a lot for me, my impression was that every emulator core would need a separate config defining before it was even usable if it didn't have one in the db already.
I have nothing against the trickling in of configs as people create them and a "survival of the fittest" type system to get the "optimum" sounds great in theory. How do you plan to handle cases where the mapping isn't straight forward such as with the N64. PS3 style layouts can be mapped with either the L trigger or L button mapped to L and Z depending on if the game you are playing was designed for dpad or analog. Depending on what the users are playing this might create a sub optimal layout for some use cases. This seems to come up semi-regularly on the RetroArch forums. An A and B config that you could attach to different games in the library after first play would probably be desirable in this situation. The MegaDrive/Genesis suffers a similar situation with the 3 and 6 button pads.
I have nothing against the trickling in of configs as people create them and a "survival of the fittest" type system to get the "optimum" sounds great in theory. How do you plan to handle cases where the mapping isn't straight forward such as with the N64. PS3 style layouts can be mapped with either the L trigger or L button mapped to L and Z depending on if the game you are playing was designed for dpad or analog. Depending on what the users are playing this might create a sub optimal layout for some use cases. This seems to come up semi-regularly on the RetroArch forums. An A and B config that you could attach to different games in the library after first play would probably be desirable in this situation. The MegaDrive/Genesis suffers a similar situation with the 3 and 6 button pads.