Error with the core only when using netplay

CONTe

@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:

FBNEO Netplay
Megadrive Netplay
Nes Netplay

mitu

@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.

CONTe

@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

mitu

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 used fbneo ?

CONTe

@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.

mitu

@CONTe I didn't tell you to change any settings, I merely asked if you've done it in the past.

CONTe

@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.

mitu

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.

CONTe

@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:

Megadrive Netplay Error

I also did not find the "help" file that it describes in the log

CONTe

@CONTe i think i will reinstall retropie, too much errors. Thank you so much mitu for the help!!

Schmurtz

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

mitu

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.