No device list and very few logs on Linux Mint about qusb2snes HOT 14 OPEN

Qusb doesn't have any interface beyond the tray icon, except for some popups the very first time you open it.

It watches 8080 as the primary port, and 23074 as secondary. Most clients use 8080, but some are moving to 23074 due to congestion on 8080.

Have you enabled Network Commands in RetroArch? Do you have a rom running while attempting to connect? Both are required.

from qusb2snes.

Thanks for the quick reply. I just tested with a ROM running in RetroArch, then opened QUsb2snes and there are still no devices in the list. Network Commands is indeed enabled. The log is still the same as well.

from qusb2snes.

What does http://usb2snes.com/tester/index.html say?

from qusb2snes.

The debug log is a separate file if that does not output on stdout.
I just pushed something that maybe fix this RA issue.

from qusb2snes.

I am using Manjaro, but experience the same issue: QUsb2Snes does not show any device while a multiworld rom is loaded in retroarch using bsnes mercury performance.

Using usb2snes.com shows the following:

`App version: 7.42.0

Devices:

RetroArch Localhost: ["1.9.14","RetroArch","T1_P1_Gobo_QhG44xT9S6SL9WBTaZPYLQ","NO_ROM_READ","NO_ROM_WRITE","NO_CONTROL_CMD","NO_FILE_CMD"]`

from qusb2snes.

This actually tell you that the device is here x)

from qusb2snes.

That is good to know, but still

• QUsb2snes only shows a very small empty popup when you select the devices menu in its tray (just a few pixels high and about 60 pixels wide)
• the debug log file does not update after restarts reliably but the normal log does
• the pick ups are not transmitted to the other player and do not show up on the tracker

Are the flags shown after my ROM file indicating any error? Is QUsb2snes unable to read and write ROM data and cannot use control or file commands?

Are there any additional steps in RetroArch other than enabling the network commands on port 55355 and using the bsnes mercury core? I also tried connecting to berserkermulti.world on our tracker port and searched for online games in RetroArch, but no connection succeeded. This is my output for netstat on those ports, there are only local connections:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 127.0.0.1:49996         127.0.0.1:8080          ESTABLISHED
tcp6       0      0 :::8080                 :::*                    LISTEN     
tcp6       0      0 :::23074                :::*                    LISTEN     
tcp6       0      0 127.0.0.1:8080          127.0.0.1:49996         ESTABLISHED
udp        0      0 0.0.0.0:55355           0.0.0.0:*

from qusb2snes.

No clue regarding the UI problem, but

for issues where the device shows up in the external program (multiworld or tracker or whatever), but does not work, we need a debug log that was created while the external program tried to to its stuff. After enabling the debug log in qusb's context menu and restarting it, the log file should be placed in ~/.local/share/QUsb2Snes/log-debug.txt.

Besides that I am pretty sure samus.link does not work with RA > 1.9.0, because "complex" memory access in the new interface in RA is just broken for everything that is not HIROM.
As Linux user you can try to build my bsnes-plus fork over at https://github.com/black-sliver/bsnes-plus to figure out if it's specifically RA that's not working (assuming emunw-pre2 support is not broken yet).

from qusb2snes.

What does http://usb2snes.com/tester/index.html say?

It keeps repeating the following:

Connected to websocket
Connection closed
Trying to reconnect

In the bottom text, it says:

App version: 7.42.0
No devices found

I have ports 8080 and 23074 allowed in ufw.

from qusb2snes.

for issues where the device shows up in the external program (multiworld or tracker or whatever), but does not work, we need a debug log that was created while the external program tried to to its stuff. After enabling the debug log in qusb's context menu and restarting it, the log file should be placed in ~/.local/share/QUsb2Snes/log-debug.txt.

I think in addition to the menu issue, berserkermulti is broken, as my browser is able to connect to QUsb2snes on port 8080, but the berserker tools do not. As a result, there are no lines in my debug-log that indicate any connection attempts. Will report the connection issue with berserker66, but as a heads up for anyone else here it is: berserker connects to the archipelago host just fine (the log on their website reports the established connection), but the WebUI shows "not connected" for both the SNES device and the server. On the console, this error message is hinting at an issue with legacy websocket code in python:

No ROM detected, awaiting snes connection to authenticate to the multiworld server (/snes)
connection open
connection handler failed
Traceback (most recent call last):
  File "~/.local/lib/python3.10/site-packages/websockets/legacy/server.py", line 231, in handler
    await self.ws_handler(self)
TypeError: websocket_server() missing 1 required positional argument: 'path'
connection closed

Besides that I am pretty sure samus.link does not work with RA > 1.9.0, because "complex" memory access in the new interface in RA is just broken for everything that is not HIROM.

I did notice commits hinting at issues with RA memory access in this repo ;)

As Linux user you can try to build my bsnes-plus fork over at https://github.com/black-sliver/bsnes-plus to figure out if it's specifically RA that's not working (assuming emunw-pre2 support is not broken yet).

I only ever downloaded cores from within RA. Where would I put the files from the output folder to make them work in RA?

from qusb2snes.

Oh, dang. Sorry for the late reply. Bsnes-plus is stand-alone, not a RA core.

Not sure how well berserker multi still works. It got replaced by archipelago.gg and had little updates since then. The actual communication is incompatible, so if you use the webhost, i think berserkermulti.world still works (and archipelago.gg doesn't). Will ping them in their discord to maybe update the README to reflect that.

If you want to give archipelago (the multi-game version) a try, checkout their Setup Guides on archipelago.gg. They use a new client.

from qusb2snes.

So, does this issue is resolved? confused

from qusb2snes.

It hasn't been resolved for met yet unfortunately. It seems there are problems with RetroArch; however, is the device list supposed to show up only once a connection is made? I was under the presumption that QUsb2snes creates the device which is then to be used by the emulator. Correct me if I'm wrong.

from qusb2snes.

I'm still seeing the same issue on RetroArch 1.9.0. I'm not sure what I have to do to get a device to show up. Network Commands is enabled. Logs have not changed.

from qusb2snes.