Manettes N64 originales sur Recalbox
-
@substring ups, sorry.
I was saying that it would be great if we could overwrite the standard ES controller configuration on another entry on the menu just for n64, as that controller is really particular. That way the user wouldn‘t need to mess around with configfiles. Adding the dummy on recalbox.conf isn‘t very friendly with mupen64plus standalone.
If your question was answered, please mark it as solved: Topic Tools -> Ask a question + Topic Tools -> Mark as Solved
-
@paradadf prolly ... Too much work for too little result. Contributors are rare and very valuable
-
No worries about the language change and thank you for your answers ! I read your initial topic.
After deleting "" in my es_input.cfg file, all my roms are now playable and it's better than reinstall RC !However, I still can't use my N64 controller. Nothing's happen with any button...
One more thing, I can't anymore exit the emulator because my others controllers seems to be disabled and my N64 controllers don't work. I have to shutdown and restart my Raspberry for each test.What's wrong ?
One more question, if the controller was a bit okay, should it be able to navigate in Recalbox or should it works only when a N64 ROM is playing ?
I agree your sentence about an easier way to add and map N64 controllers
-
@j3r3m can you use the controller in any retroarch core after deleting that html entity?
If your question was answered, please mark it as solved: Topic Tools -> Ask a question + Topic Tools -> Mark as Solved
-
@paradadf
I did another remote configuration on Recalbox.
All my ROMs did not launch before I edit es_input.cfg file.
After a reboot, my controllers can navigate in Recalbox, but can't be used in any core after the file editing : no reaction when I press any button, whatever used emulator. -
@j3r3m try configuring it again in ES. I could navigate right after the mapping.
If your question was answered, please mark it as solved: Topic Tools -> Ask a question + Topic Tools -> Mark as Solved
-
@paradadf, actually, I can navigate in ES, but the remote is not usable when a rom is started.
Or maybe I misunderstood ? -
@j3r3m after configuring the controller in ES and deleting the weird character in es_input.cfg I was able to play.
If your question was answered, please mark it as solved: Topic Tools -> Ask a question + Topic Tools -> Mark as Solved
-
@paradadf, my official remotes are able to play on N64 ROMs!
I just meet some issues :- The L+R keys pressed together don't exit the emulator
- The joystick seems "unatural".
For example, for Super Mario 64 ROM, I have to push strongly on the joystick for the up-side and Mario only walks.
But, on the others joystick sides, its reactions are smoothier.
However, I have no issue with this remote when using it on N64.
Sorry if I'm not clear about this, it's a bit abstract and I don't know how to describe this with my middle-level english!
I also have to test my two unofficial remotes... Later in my daily list!
-
@j3r3m for all your difficulties you should read the topic I posted above. That‘s the hard part which needs configuration. Joytick sensibility is also an issue, that‘s why it feels unnatural. And you must du all those configurations manually.
If your question was answered, please mark it as solved: Topic Tools -> Ask a question + Topic Tools -> Mark as Solved
-
@paradadf Okay, I hope it will be quick to configure!
However, It seems good for another remote.
In fact, original remotes have almost 20yo and I bought 2 copies a few months ago.
I think it explain why I don't have the same sensibility between 2 remotes.I tried N64 games on Emulation Station for the first time a few minutes ago.
I tried GoldenEye and Im disapointed because I met a lot of computeur slowdowns...
Do everybody meet this issue ?
