dov_EL Posted October 28, 2019 Share Posted October 28, 2019 @Jason Carr this is retroarch default config setting. Can it help you understand the cause of the problem? Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted October 28, 2019 Share Posted October 28, 2019 Unfortunately not. It's a Retroarch glitch in that it doesn't obey the default settings. Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 15 hours ago, Jason Carr said: Unfortunately not. It's a Retroarch glitch in that it doesn't obey the default settings. we have some retroarch dev here? To whom can we report this problem which is very serious for those who use launchbox and retroarch in the bartop? Quote Link to comment Share on other sites More sharing options...
Mr. RetroLust Posted October 29, 2019 Share Posted October 29, 2019 2 hours ago, dov_EL said: we have some retroarch dev here? To whom can we report this problem which is very serious for those who use launchbox and retroarch in the bartop? https://forums.libretro.com/ Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 3 hours ago, Mr. RetroLust said: https://forums.libretro.com/ OK https://forums.libretro.com/t/retroarch-and-launchbox-big-problem-windows-volume/24891 If I have described the problem incorrectly, can you help me with your English so that we can hear from developers? Quote Link to comment Share on other sites More sharing options...
Mr. RetroLust Posted October 29, 2019 Share Posted October 29, 2019 23 minutes ago, dov_EL said: OK https://forums.libretro.com/t/retroarch-and-launchbox-big-problem-windows-volume/24891 If I have described the problem incorrectly, can you help me with your English so that we can hear from developers? Pinpoint is another term for telling exactly at what point the problem started Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 Maybe I understood the problem. I could not visualize everything because I deactivated the "MENU WIDGET" function. As soon as we try to increase or decrease the volume, the game pauses for the first time, then it works. The reararch PAUSE appears at the top right (last version) Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 the problem should be this, but I still don't get results even by turning off the function Quote Link to comment Share on other sites More sharing options...
DOS76 Posted October 29, 2019 Share Posted October 29, 2019 In the input settings under hot key binds is the pause toggle set to the same key your bartop is using for LB volume? Quote Link to comment Share on other sites More sharing options...
dov_EL Posted October 29, 2019 Author Share Posted October 29, 2019 Just now, DOS76 said: In the input settings under hot key binds is the pause toggle set to the same key your bartop is using for LB volume? Er not. P is keyboard . Bartop have gamepad input . However I tried to change this too, but I don't get any results. unbelievable Quote Link to comment Share on other sites More sharing options...
dov_EL Posted November 1, 2019 Author Share Posted November 1, 2019 @Jason Carr https://forums.libretro.com/t/retroarch-and-launchbox-big-problem-windows-volume/24891/21 Quote Link to comment Share on other sites More sharing options...
dov_EL Posted November 4, 2019 Author Share Posted November 4, 2019 99% the problem is this Quote Link to comment Share on other sites More sharing options...
dov_EL Posted November 4, 2019 Author Share Posted November 4, 2019 K is not the only key that creates conflicts, they also have F9 - F10 and other keys that I'm trying to understand. RetroArch 2019.11.04 - 10.49.57.01.mp4 Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted November 4, 2019 Share Posted November 4, 2019 @dov_EL I did some additional testing over the weekend, and my initial thoughts that it was related to Retroarch's controller settings were wrong, as I couldn't replicate the issue without the keyboard being involved. But all LaunchBox should be doing is sending volume up and volume down keyboard presses, so I'm still lost here. What do the K and F9/F10 keys have to do with it? Quote Link to comment Share on other sites More sharing options...
dov_EL Posted November 4, 2019 Author Share Posted November 4, 2019 3 hours ago, Jason Carr said: @dov_EL I did some additional testing over the weekend, and my initial thoughts that it was related to Retroarch's controller settings were wrong, as I couldn't replicate the issue without the keyboard being involved. But all LaunchBox should be doing is sending volume up and volume down keyboard presses, so I'm still lost here. What do the K and F9/F10 keys have to do with it? F10 in retroarch SEND DIAGNOSTIC . Probably the system you used goes to touch a series of keys that goes into conflict with retroarch. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted November 7, 2019 Share Posted November 7, 2019 On 11/4/2019 at 12:05 PM, dov_EL said: F10 in retroarch SEND DIAGNOSTIC . Probably the system you used goes to touch a series of keys that goes into conflict with retroarch. The LaunchBox code doesn't do anything with F9, F10, or K, unless you bind to those keys. So I'm still confused as to what's going on here. Quote Link to comment Share on other sites More sharing options...
sundogak Posted November 8, 2019 Share Posted November 8, 2019 (edited) There was another thread, although more related to controller and may be unrelated to this issue. Have you tried changing the RA Input to "Raw" Edited November 8, 2019 by sundogak 1 Quote Link to comment Share on other sites More sharing options...
dov_EL Posted November 12, 2019 Author Share Posted November 12, 2019 On 11/8/2019 at 2:55 AM, sundogak said: There was another thread, although more related to controller and may be unrelated to this issue. Have you tried changing the RA Input to "Raw" WORK PERFECT !!! THANK YOU !!!! 1 1 Quote Link to comment Share on other sites More sharing options...
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.