Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto tracker gets stuck in disconnect/reconnect loop #252

Open
MattEqualsCoder opened this issue Jan 2, 2023 · 1 comment
Open

Auto tracker gets stuck in disconnect/reconnect loop #252

MattEqualsCoder opened this issue Jan 2, 2023 · 1 comment
Labels
🔗 auto-tracking Issues related to emulator integration via Lua scripts or USB2SNES, such as auto tracking. 🐛 bug Something isn't working

Comments

@MattEqualsCoder
Copy link
Collaborator

This happens every so often, and I'm not sure why. I've pretty much never been able to reproduce it reliably. But, sometimes tracker will get in a loop of disconnecting and reconnecting to the emulator and it can't get out. No errors or anything in the log. There's basically just a loop like this that happens over and over:

2022-12-31T13:17:20.0204007-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.USB2SNESConnector]	[0]	Requesting device list
2022-12-31T13:17:20.0212177-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.USB2SNESConnector]	[0]	Connecting to USB2SNES device Emu - Berrypunch
2022-12-31T13:17:21.1414940-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.AutoTracker]	[0]	Start sending messages 12/31/2022 13:17:21
2022-12-31T13:17:25.0287654-06:00	FAIL	[Randomizer.SMZ3.Tracking.AutoTracking.USB2SNESConnector]	[0]	USB2SNES connection lost NoMessageReceived
2022-12-31T13:17:25.0288040-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.AutoTracker]	[0]	Disconnected
2022-12-31T13:17:25.0316987-06:00	FAIL	[Randomizer.SMZ3.Tracking.AutoTracking.USB2SNESConnector]	[0]	Reconnection happened, type: NoMessageReceived

This happened most recently when betus beat the game, reloaded, then tried to have tracker kill him. Auto tracker got the following message from detecting a region change:

2022-12-31T13:15:10.7662991-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.AutoTracker]	[0]	ChangedMetroidRegion detected

But then when betus enabled cheats and asked tracker to kill him it started:

2022-12-31T13:15:55.5809865-06:00	INFO	[Randomizer.SMZ3.Tracking.VoiceCommands.AutoTrackerModule]	[0]	Recognized "Hey tracker, enable cheats" with 94.65 % confidence.
2022-12-31T13:16:00.7063113-06:00	INFO	[Randomizer.SMZ3.Tracking.VoiceCommands.AutoTrackerModule]	[0]	Recognized "Hey tracker, kill me" with 95.36 % confidence.
2022-12-31T13:16:05.7343622-06:00	FAIL	[Randomizer.SMZ3.Tracking.AutoTracking.USB2SNESConnector]	[0]	USB2SNES connection lost NoMessageReceived
2022-12-31T13:16:05.7348020-06:00	INFO	[Randomizer.SMZ3.Tracking.AutoTracking.AutoTracker]	[0]	Disconnected
@MattEqualsCoder MattEqualsCoder added 🐛 bug Something isn't working 🔗 auto-tracking Issues related to emulator integration via Lua scripts or USB2SNES, such as auto tracking. labels Jan 2, 2023
@MattEqualsCoder
Copy link
Collaborator Author

Honestly, I can't replicate this myself to be able to see what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔗 auto-tracking Issues related to emulator integration via Lua scripts or USB2SNES, such as auto tracking. 🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant