Posts made by Cheemix

Didn't succeed... Still don't know why.
The keyboard works OK, but the PS3 controller is like if it didn't exist.

Thank you very much!!

@substring Sorry I'm such a noob! XD I read some conversations about pairing controllers and the truth is I still don't understand very much... I would like to use my original bluetooth Sony PS3 controller in Moonlight as I do with the emulators in Recalbox, but I'm not very sure this will be easy. Is there alredy a way that doesn't imply mapping manually or are you still working on that? The only thing I can do by now is connecting a keyboard and a mouse to the Raspberry, but I want to use Moonlight precisely because I want to play from the sofa... XD
If there is something I can do or read to approach this without bothering you anymore, I would thank you a lot!

PD: Just in order to add a question that doesn't have much to do with Moonlight itself... Have you found a way to avoid Geforce Experience upgrading to 3.13?

Thank you for your patience!!

@substring Done! Thank you very much! The problem was using WinSCP instead of PUTTY... Sorry.

Now the problem is that my PS3 controller doesn't work. It seems you have talked about that before, so I'm going to read it

@substring Sorry, I said ping bt I meant pin. I'm going to try what you said

@cheemix It is like this all the time:

/recalbox/share/system$ /recalbox/scripts/moonlight/Moonlight.sh pair
() /recalbox/share/system/configs/moonlight/moonlight.conf | /recalbox/share/system/configs/moonlight/keydir
Failed to pair to server: Streaming session has failed due to a game management error.
Searching for server...
Connect to XXXXXX...
Generating certificate...done
Please enter the following PIN on the target PC: 0663
YOLO MODE !!!
/recalbox/share/system$ /recalbox/scripts/moonlight/Moonlight.sh pair
() /recalbox/share/system/configs/moonlight/moonlight.conf | /recalbox/share/system/configs/moonlight/keydir
Failed to pair to server: Streaming session has failed due to a game management error.
Searching for server...
Connect to XXXXXX...
Generating certificate...done
Please enter the following PIN on the target PC: 3997
YOLO MODE !!!

@cheemix The weird thing is that, as you say, it says all the time "Failed to pair", but it doesn't tell me the ping before saying that. It gives me the ping after. And to open the Nvidia window I have to put the script again, but then the ping is not the one it told me before, so it fails again.

@substring Sorry, what do you mean by "clean parameter"?
This is what happens to me. This appears at the same time:

If I do nothing, awindow appears saying that WinSCP is going to close. I can ask it not to do so, but then nothing happens neither.
If i push "Connect", it acts like everything is OK but the ping appears later.
If I push "Cancel", the ping appears, but the NVidia window closes, so I have nowhere to put the ping...

Hi!
I've got a problem with Moonlight that I can't understand.
I must say that I have a low level of computering, so maybe I did something wrong. Before anything, also sorry for my english.

First of all, I downloaded Geforce Experience in 3.11 version so Recalbox would be able to connect to it and I added some games.
I connected to Recalbox through WinSCP with SCP protocol. I did what the GitHub says typing:
/recalbox/scripts/moonlight/Moonlight.sh find
After that, I typed:
/recalbox/scripts/moonlight/Moonlight.sh pair
Once I did this, something unexpected happened. A little window of Nvidia Shield oppened asking for a ping so I could connect. I looked into the GitHub and I wondered if the ping should have appeared after what I typed. At least that was what GitHub seemed to be saying. As I had no ping to type, I pushed the "Connect" button anyway and, to my surprise, the ping appeared after that in the WinSCP and a message saying that my device was already paired.
Then, I typed this:
/recalbox/scripts/moonlight/Moonlight.sh init
It said YOLO MODE, you know, but then appeared the text:
Adding and scraping . . .
And nothing more... Everything stopped here. I reseted the Raspberry, I repeated this process, I tried to connect through the new Moonlight option I had in Emulestation... But nothing. No game added, no scraping, no connection possible.

I tried Moonlight in my phone just to check and everything worked, but not in Recalbox.

What could I be doing wrong?

Thank you very much!

Pues eso, que al scrapear desde Recalbox, de repente, Screenscraper no encuentra nada. Me ocurrió ayer, pensé que podía ser algo del servidor y hoy al volverlo a intentar pasa lo mismo. Probé scrapeando de GamesDB y todo bien. ¿Alguien sabe algo? ¿Os pasa igual?

Same problem!

In my case it happens with retrolink N64 controller since the beginning with 4.1.
I added the ImputAutocfg.ini file as I had it working propperly in the 4.0.2 version and it doesn't help. In fact, it should help PS3 controller work and it doesn't neither. This is the content of the file as I have it:

[Generic USB Joystick ]
plugged = True
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = axis(5+)
DPad L = axis(5-)
DPad D = axis(6+)
DPad U = axis(6-)
Start = button(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig = button(4)
Mempak switch = key(109)
Rumblepak switch = key(114)
Y Axis = axis(1-,1+)
X Axis = axis(0-,0+)

[Sony PLAYSTATION(R)3 Controller]
plugged = True
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = button(5)
DPad L = button(7)
DPad D = button(6)
DPad U = button(4)
Start = button(3)
Z Trig = button(10)
B Button = button(15)
A Button = button(14)
C Button R = axis(2+)
C Button L = axis(2-)
C Button D = axis(3+)
C Button U = axis(3-)
R Trig = button(11)
L Trig = button(8)
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

Is any of this wrong? Does anybody know where could be the problem?

@jesús-bl Perdona por tardar, Jesús! La verdad es que te agradezco la ayuda, pero me siento super perdido... El tema en todo caso no es ni la configuración del mando ni el bluetooth. El de PS3 de hecho lo tengo asociado por bluetooth y sin problemas para el resto de consolas. Lo que me falla es claramente el mupen64, porque ahí no me va ni el de retrolink ni el de PS3. Por eso me pregunto si el ImputAutocfg.ini está mal, ya sea porque hayan cambiado la configuración de mandos o lo que sea.

Estoy intentando cambiar cosas de la configuración del mando, pero la cosa sigue igual. ¿Alguien me ayuda con el mando de PS3 o con el de retrolink de N64?

Muchas gracias!

Si mal no recuerdo (he hecho tantas cosas al actualizar que no te lo puedo asegurar), creo que cambié el InputAutoCfg.ini precisamente porque el mando no respondía bien. El problema es que ya no tengo el archivo original. Me podrías decir cómo te sale a ti la configuración? Para ver si puedo hacerle algún apaño...

Gracias por el link, pero esos posts ya los leí hace tiempo y me ayudaron a tener la configuración que antes me funcionaba y ahora no.

Nadie sabe cómo arreglar esto?

Y, mientras tanto, alguien a quien le funcione el mando de PS3 (a mí ni me responde en la N64) podría decirme cómo aparece su archivo InputAutoCfd.ini ?

Saludos y gracias!

Hola!

Tengo un problema con mi mando de retrobit de Nintendo 64 tras la actualización a Recalbox 4.1 estable.

Le meto el archivo InputAutoCfg.ini que tenía antes, con el que el mando me funcionaba perfecto, y ahora, cuando ejecuto juegos, los controles no funcionan bien. En el Super Mario 64, por ejemplo, el stick me permite girar a Mario a izquierda y derecha, pero no hacia adelante y hacia atrás.

La configuración de InputAutoCfg.ini es la siguiente:

[Generic USB Joystick ]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = hat(0 Right)
DPad L = hat(0 Left)
DPad D = hat(0 Down)
DPad U = hat(0 Up)
Start = button(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig = button(4)
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

Perfecto. Gracias!!

Ok, gracias! Me espera una paliza con eso entonces jaja

Hola, @paradadf
Yo tengo todos los juegos de psx en bin sin los cue. Significa eso que cuando actualice a 4.1 tendré que crear cues para cada archivo porque si no no me van a aparecer los juegos?
Gracias!