Error with the core only when using netplay
-
Pi Model or other hardware: Pi 4
Power Supply used: -Input: 240v 50/60hz 0.5A MAX -Output 5.0v 3.0A 15.0W
RetroPie Version Used: Retropie setup script 4.8.2
Built From: -Retropie official website: https://github.com/RetroPie/RetroPie-Setup/releases/download/4.8/retropie-buster-4.8-rpi4_400.img.gz
Controller used: Xbox One
Error messages received: "core does not support netplay" "failed to initialize netplay"
Emulator: 1.12.0 - final burn neo (v1.0.0.03 c8d4b82) and all the cores except 1.12.0 - snes9x (1.61 bc3bbb2)
How to replicate the problem: Hello, I just updated everything and set the netplay as host. Then I tried to play games from many of the script emulators and always got that error except with 1.12.0 - snes9x (1.61 bc3bbb2) of Super NES. Same results as a guest. This only happens to me trying to play with netplay, playing alone everything works perfectly for me. It should be noted,
that before it could be both host and guest in any core and that's why I know that the error message is false, since the core support it. In fact my friend at Batocera using the same cores has no problem so it must be a bug for me. -
Update your RetroPie-Setup script and then re-install
retroarch
, it looks like you're missing the core.info
file(s) where Netplay capability is configured. -
@mitu Thanks for answering! I have tried but it has not worked. Could you pass me the correct file and tell me the path where to put it? Maybe I can replace it manually
-
The core
.info
files should be in$HOME/.config/retroarch/cores
. All files from https://github.com/libretro/libretro-core-info should be present there.You can get a verbose log from running and we can see if the
.info
file is loaded or not. -
I manually put the
.info
files I downloaded from the link to make sure they were in$HOME/.config/retroarch/cores
but it still gave me the same problem.I have collected these logs:
FBNeo Alone - runcommand
SNES Alone - runcommand
SNES ONline - runcommandSNES It is the only one that works online and that throws log
-
From the logs you attached (please use pastebin.com for future logs) I see the
.info
files are loaded correctly. Can you get a verbose log from a netplay session, when you get the actual error ? -
@mitu Oh, sorry. Now I bring in paste.bin the ones that it throws when I try to start a game with netplay activated as a server. Its the same error as guest:
-
@CONTe said in Error with the core only when using netplay:
@mitu Oh, sorry. Now I bring in paste.bin the ones that it throws when I try to start a game with netplay activated as a server. Its the same error as guest:
All I see is that RetroArch fails to start, there's no netplay related error.
-
@mitu I have been doing tests and looking at the logs, and when I have the netplay server started and I try to start a game I get that token 5 error in the log, the game does not start and I get the message that the core does not support the netplay. On the other hand, in snes and psx that the netplay DOES work,
in the log appears token 4 and the game starts and netplay works.I think that "Error: Expected no more than 4 tokens for --inputbox, have 5." is the cause that i cant play with netplay in that cores. How i can fix that? Because when I start the game with netplay turned off it works and starts normally
-
Looks to me you've used 'Save Configuration' from RetroArch for the system where netplay doesn't work and the netplay settings are empty, thus the error.
Did you enable 'Save Configuration on Exit' in RetroArch or manually saved the config for the system where you usedfbneo
? -
@mitu I think I have to save the settings manually. I'm still going to check it out and see if that fixes it. Thank you very much for all the help, I'll tell you in a moment if that was it.
-
@CONTe I didn't tell you to change any settings, I merely asked if you've done it in the past.
-
@mitu Oh! Since the last update I started having this problem and I was looking at the settings to see if I could fix it. So it can be. Save configuration when closing retroarch it's off, i save manually.
-
I suggest you reset your Reset the RetroArch settings for the systems where you have issues by:
- renaming
retroarch.cfg
in the respective system's folder (/opt/retropie/configs/all/<system>
) - re-installing the emulator for that system - any
libretro
based emulator would be ok, since its installation would re-generate the default RetroPie config.
For instance,
- rename
/opt/retropie/configs/megadrive/retroarch.cfg
to something elese - re-install the
lr-genesis-plus-gx
emulator.
EDIT: also, check if you have set the hostname and nickname from the 'Netplay Configuration' in RetroPie, it doesn't look like you have.
- renaming
-
@mitu I did everything you suggest and I also tried to activate the option to save configuration when exit Retroarch but it does not stay active no matter how much I save changes and I changed my netplay nick and saved changes in case it was that and it didn't work. The games do not start when I have netplay active due to this error:
I also did not find the "help" file that it describes in the log
-
@CONTe i think i will reinstall retropie, too much errors. Thank you so much mitu for the help!!
-
Same problem here with a different platform : I work on Miyoo Mini.
When I run Genesis-Plus-GX I always have the message : "Core does not support Netplay".
Retroarch, my info file and the core are up to date. Even with core builds from libretro buildbot or classicmodscloud I have the same result.
I don't have the problem on x86 (test OK on Linux and Windows)So 2 solutions :
- it's a problem from current retroarch version
- it's a problem from the core when it's build for arm (probably this one)
Issue created here :
https://github.com/libretro/Genesis-Plus-GX/issues/330 -
it's a problem from current retroarch version
No, since the problem doesn't show up on other platform.
it's a problem from the core when it's build for arm (probably this one)
Unlikely, since the core on RetroPie works with Netplay using the latest RetroArch version.
The issue in this post is related to missing
.info
files, which were not part of Retropie's RetroArch installation until 1 year ago. Users which upgraded their RetroArch package without updating the RetroPie-Setup script had this kind of errors, which are solved with an update of RetroPie-Setup and then re-installing RetroArch.I don't think your issue is related to the current topic.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.