xokia Posted Monday at 08:13 PM Posted Monday at 08:13 PM (edited) Can someone help me understand the game controller feature? I typically buy wireless game controllers to match the specific system I want to use. For example I have N64 wireless USB controllers to work with retroarch mugenplus_next emulator. I usually go into retroarch and then remap all the button to work with the controller I am using. (I think I want to leave these mapped to game pad setting and use this game controller feature instead?) I think and please correct me if I am wrong "game pad" is for dinput basically an xbox controller layout? If I assign a platform to Nintendo Switch joy-con does that then map the switch controller to the xbox gamepad layout? I have struggled with the controller terminology and how all the conversions work so if anyone can help that would be appreciated. Edited yesterday at 12:44 AM by xokia Quote
JoeViking245 Posted 18 hours ago Posted 18 hours ago 16 hours ago, xokia said: Can someone help me understand the game controller feature? The game controller management system you're showing is informational only. It adds another layer of metadata for games (and platforms) that can be used to filter from and/or show badges for quick identification. Its intent is to show the supported controllers for games and allow full flexibility for customization. aka Customize it to have information that makes sense to you. LaunchBox does not (can not, and most likely will not ever) do any in-emulator controller configuring (outside of being able to access the LaunchBox Pause Menu and exiting the emulator). Quote
xokia Posted 12 hours ago Author Posted 12 hours ago (edited) 5 hours ago, JoeViking245 said: The game controller management system you're showing is informational only. It adds another layer of metadata for games (and platforms) that can be used to filter from and/or show badges for quick identification. Its intent is to show the supported controllers for games and allow full flexibility for customization. aka Customize it to have information that makes sense to you. LaunchBox does not (can not, and most likely will not ever) do any in-emulator controller configuring (outside of being able to access the LaunchBox Pause Menu and exiting the emulator). So me configuring the controller or creating a map file and passing via the command line is still the correct thing to do. Thank you for the explanation. What value is the metadata? Just trying to figure out why someone would care. Not trying to be negative here just generally curios how someone would use this info/metadata. i.e. What is the use case that this info is helpful. Edited 12 hours ago by xokia Quote
JoeViking245 Posted 11 hours ago Posted 11 hours ago 43 minutes ago, xokia said: What is the use case that this info is helpful. Some examples (the last 2 probably being the more "popular" use case(s)): "I want to see (filter) only games that are controlled with a [steering] wheel." "I want to (play) see only games that can use a VR headset." "I like visually seeing the controller 'badges' a game uses." "I want to create a playlist that shows only games using a VR headset." ("so I can just select the playlist rather than clicking through filters") Quote
xokia Posted 6 hours ago Author Posted 6 hours ago 4 hours ago, JoeViking245 said: Some examples (the last 2 probably being the more "popular" use case(s)): "I want to see (filter) only games that are controlled with a [steering] wheel." "I want to (play) see only games that can use a VR headset." "I like visually seeing the controller 'badges' a game uses." "I want to create a playlist that shows only games using a VR headset." ("so I can just select the playlist rather than clicking through filters") ok now I see it. Thanks for that explanation 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.