Xbox 360 wireless controller stops working after returning from menu to game

[salzix]

Xbox 360 wireless controller stops working after returning from menu to game

[giantclambake]

A few weeks ago, we did a lot of input controller testing ~ that said, I'm not certain if the wireless USB xbox controller was covered (I only have wired controllers, not sure about others' testing ;) That said, I cannot recreate this here using a RPi4 with bookworn, wrt amiberry v5.7.3 or Master ... with wired xbox controllers.

M'kay...lets try constrain the test example...(see attached) ... the whdloader will define controller mapping via the XML, giving us 'common ground' here. Could you please do the following test, and let us know the results?

Download/unzip the attached file, and launch the amiberry GUI --> go to Paths panel and Enable logging:
Go to Quickstart panel, and select the StuntCarRacer_v1.3_0222.lha in WHDLoad auto-config: --> press Start
This title will boot quickly to the game main menu (3 items)...you should be able to use dpad up/down to move selection
Hit F12 ---> can you still use dpad up/down to select panel entries in the amiberry GUI?
IF you click Resume, does the controller still work in the game menu or not?

Quit amiberry, gzip the resultant amiberry.log file, and attach it to your reply.

StuntCarRacer_v1.3_0222.lha.gz

[salzix]

Hello and thanks for quick reply! I went through these test steps. Here's the result, and logs attached. 1. Tested on provided StuntCarRacer: - I've started a game (with logging on), it loaded, I was able to use controller to move selection in in-game menu. - After hitting F12 I was able to move through entries in amiberry GUI - After selecting "Resume" it didn't return to game. Instead a command line showed up, with my ./amiberry command entered on start. It was unresponsive, frozen. I couldn't close it, so i killed process from another terminal session. It looks like another problem :( 2. Tested on ADF file with Rodland game: - As before, I was able to run a game, use controller - Also after going to Amiberry GUI I was able to use controller to move through menus - After selecting "Resume" it returned to game, but controller wasn't working in game. - After hitting F12 again the controller worked in Amiberry GUI - that's one thing I didn't try before. I've attached separate logs of both runs. wt., 16 lip 2024 o 12:36 giantclambake ***@***.***> napisał(a):

…

A few weeks ago, we did a lot of input controller testing ~ that said, I'm not certain if the wireless USB xbox controller was covered (I only have wired controllers, not sure about others' testing ;) That said, I cannot recreate this here using a RPi4 with bookworn, wrt amiberry v5.7.3 or Master ... with *wired* xbox controllers. M'kay...lets try constrain the test example...(see attached) ... the whdloader will define controller mapping via the XML, giving us 'common ground' here. Could you please do the following test, and let us know the results? Download/unzip the attached file, and launch the amiberry GUI --> go to Paths panel and Enable logging: Go to Quickstart panel, and select the StuntCarRacer_v1.3_0222.lha in WHDLoad auto-config: --> press Start This title will boot quickly to the game main menu (3 items)...you should be able to use dpad up/down to move selection Hit F12 ---> can you still use dpad up/down to select panel entries in the amiberry GUI? IF you click Resume, does the controller still work in the game menu or not? Quit amiberry, gzip the resultant amiberry.log file, and attach it to your reply. StuntCarRacer_v1.3_0222.lha.gz <https://github.com/user-attachments/files/16247177/StuntCarRacer_v1.3_0222.lha.gz> — Reply to this email directly, view it on GitHub <#1384 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6MZJE6XXQZQNBOLCWLOGDZMTZRPAVCNFSM6AAAAABK6DMLGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQGU3TAOBQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[giantclambake]

Thanks for testing ;)

Can you retry attaching the logfiles again? For some reason, they're not attached to your reply. (use the 'click to add files' method)

[salzix]

I think they were blocked by antivirus when gzipped. I've decompressed them, they are small anyway. Here you go. wt., 16 lip 2024 o 14:32 giantclambake ***@***.***> napisał(a):

…

Thanks for testing ;) Can you retry attaching the logfiles again? For some reason, they're not attached to your reply. (use the 'click to add files' method) — Reply to this email directly, view it on GitHub <#1384 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6MZJHBHYSHPAMTAMSIWPTZMUHF5AVCNFSM6AAAAABK6DMLGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQG43TGMJYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[giantclambake]

//I live in AU and zulu +10 timezone puts me out of step with the EU ;)

Logfiles still not attached ~ I think it's because you're replying by email, and not replying to this github page directly ; when replying to this github page, the logfiles have to be gzipped =)

1. Tested on provided StuntCarRacer:

• I've started a game (with logging on), it loaded, I was able to use
  controller to move selection in in-game menu.
• After hitting F12 I was able to move through entries in amiberry GUI
• After selecting "Resume" it didn't return to game. Instead a command line
  showed up, with my ./amiberry command entered on start. It was
  unresponsive, frozen. I couldn't close it, so i killed process from another
  terminal session.

This is an odd result ~ I'm presuming here you're using console only (no desktop environment)? If you've enabled logging in the GUI, that setting will stick (logging is always turned on). It would be interesting to know what happens if you redo this test, except direct launching the title instead of using GUI...ie; ./amiberry StuntCarRacer_v1.3_0222.lha (presumes the whdload.lha file is in same directory as amiberry, if not, ./amiberry path/to/StuntCarRacer_v1.3_0222.lha will work) A logfile of this might be handy.

2. Tested on ADF file with Rodland game:

• As before, I was able to run a game, use controller
• Also after going to Amiberry GUI I was able to use controller to move through menus
• After selecting "Resume" it returned to game, but controller wasn't working in game.
• After hitting F12 again the controller worked in Amiberry GUI - that's one thing I didn't try before.

This is interesting ~ I've got a hunch this is all somehow related to #1351 in some way....at least, the behavior roughly follows that pattern. I'll setup the RPi4 here today in console mode, and see if I can recreate it.

[giantclambake]

@salzix ~ I can recreate this on the RPi4 when booting to console (CLI) mode, using a USB wired Xbox controller. I'll have to do some more testing here to try isolate the cause, but my immediate appreciation is that this is some other machination of #1351 as well, as I'm seeing the same reticence wrt the F12 key action therein described.

Thanks for reporting this ~ as I can recreate the issue here, we no longer need your logfiles as such ;) I don't think it's related to the wireless xbox controller, but I do have a question --- are you using a USB wired, or wireless keyboard?

@midwan ~ I'll need to tease this out some more, as I don't use CLI mode on the RPi4 often, and I'll have to check how KMS/DRM are set. Further, I'm becoming suspicious of host-side kbd input wrt the F12 key action, particularly with USB wireless keyboards ; in layman's terms (laypersons? ;), it's as though hitting F12 once, results in multiple F12 keypress events being actioned (I got the same impression on the LFS x86-64 build in console mode using USB wireless KBD), so I'll need dig a bit deeper and swap hw around to get a better handle on it =)

[salzix]

Hi, // good morning from EU :) I'm using USB wired keyboard, and booting to CLI mode. I'll check how it works under GUI. Let me know if you need anything more, I'll be happy to help to resolve these issues. śr., 17 lip 2024 o 05:11 giantclambake ***@***.***> napisał(a):

…

@salzix <https://github.com/salzix> ~ I can recreate this on the RPi4 when booting to console (CLI) mode, using a USB *wired* Xbox controller. I'll have to do some more testing here to try isolate the cause, but my immediate appreciation is that this is some other machination of #1351 <#1351> as well, as I'm seeing the same reticence wrt the F12 key action therein described. Thanks for reporting this ~ as I can recreate the issue here, we no longer need your logfiles as such ;) I don't *think* it's related to the wireless xbox controller, but I do have a question --- are you using a USB wired, or wireless keyboard? @midwan <https://github.com/midwan> ~ I'll need to tease this out some more, as I don't use CLI mode on the RPi4 often, and I'll have to check how KMS/DRM are set. Further, I'm becoming suspicious of host-side kbd input wrt the F12 key action, particularly with USB wireless keyboards ; in layman's terms (laypersons? ;), it's as though hitting F12 once, results in multiple F12 keypress events being actioned (I got the same impression on the LFS x86-64 build in console mode using USB wireless KBD), so I'll need dig a bit deeper and swap hw around to get a better handle on it =) — Reply to this email directly, view it on GitHub <#1384 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6MZJAWGFLJC4X7YKB3R5TZMXOEJAVCNFSM6AAAAABK6DMLGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSGI4DGNBXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>