Analog stick switch retroarch12/9/2023 ![]() ![]() I genuinely believe that this list will appeal to most gamers. While they are outstanding games, it wouldn't be appropriate for a list to primarily focus on a single saga. It's important to mention that, for instance, in the 100 most famous games for PSX, I didn't want the majority of the list to be comprised of games from the Final Fantasy series. This way, I've crafted a more balanced and diverse version of each collection. I manually created each compilation with the aim of always including the best games from each system and genre. Additionally, for systems like MAME, with over 45,000 games, narrowing it down to just 100 games is almost an impossible task. It's worth noting that in some systems, the number may vary since not all of them have a full hundred games. This one does have a input_device_display_name though, so the autodetect notification should make it pretty obvious (except the misleading D-Input part).I'd like to share my compilation of the "TOP 100" games for each gaming console. It has the same VID as xbone ctrl but no PID (and input_l_y_axis is also inverted with xbone ctrl). ![]() Note the (D-Input) part in filename/display name, doesn't seem right with xinput driver/folder. There is also the autoconfig\xinput\Retro-Bit Tribute64 - USB (D-Input).cfg that might conflict. So for others facing this issue with a xbone ctrl connected directly, I suggest renaming the autoconfig\xinput folder (even whole autoconfig folder if needed) and relaunching Retroarch to quickly confirm if the issue comes from one of the cfg files. Not sure if I missed something here or if this is also a bug. The online doc says the log file should tell if a profile has been selected, but that part doesn't work (even with debug log level).The (broken) NVIDIA Shield.cfg file doesn't include a input_device_display_name so the RetroArch input autodetect notification says Controller (XBOX 360 for Windows) configured in port #1 which leads me to look anywhere but something named "NVIDIA".What also really didn't help troubleshooting in my case: Working fine for most people, and those trying to troubleshoot this issue are going crazy. ![]() I was thinking maybe others were also streaming and didn't think about mentioning it. Should I open a separate issue to have the two NVIDIA cfg files properly fixed then? I don't have a NVIDIA Shield Controller so I can't tell if the NVIDIA Shield.cfg config file is working fine or inverted as well with the real controller, but it's definitely conflicting with the MUCH more popular xbox 360 and xbox one controllers, and alot of people seem to have been complaining about inverted axis for the last couple Thanks for your reply. However, the file (and issue) will come back when updating controller profiles.Ĭomparing this file with Xbox_One_Controller.cfg in same folder clearly shows the input_l_y_axis (and other things) are inverted in NVIDIA Shield.cfg.Īlso note the NVIDIA_GeForce_Experience_Virtual_Controller.cfg file which is set properly, but has input_vendor_id and input_product_id commented out because they are the same as in NVIDIA Shield.cfg. If you delete the autoconfig\xinput\NVIDIA Shield.cfg file and restart Retroarch, then xbox 360 and xbox one controller works perfectly. The source of this issue seems to be the NVIDIA Shield.cfg xinput autoconfig file, at least when streaming using NVIDIA GameStream (with Moonlight client in my case). Ran into this issue recently, still happens with Retroarch 1.9.0.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |