Some issues that popped up and oddities I noticed
-
Model B+
RetroPie 4.4
Image from Retropie.org.ukSo I'll be off to work in a bit, late shift, then very early shift so it'll take more than 24 hours before I can tinker with the RetroPie again, or come on here to reply, so I figure I put in a post now, and see what pops up. I've noticed a few oddities and some issues, so oddities first:
-
A7800 in the emulators in docs it says the bios is optional, only adding an Atari splash screen; and this seems to be the case as I can play A7800 games without a bios just fine; however under the Bios heading in the advanced configuration heading of the docs it mentions the A7800 as requiring a Bios.
-
The NES, aka the Famicom, accepts certain filename extentions, among them is .sfc. Wut? SFC would be Super FamiCom, aka the Super NES which is what all the Super NES games have as an extension and which is accepted by the Super NES emulator, why is that extension with the NES? And .fc (FamiCom) is not accepted... this is weird.
Now some issues I have/questions that need answering:
-
Exiting emulation, the docs say that pushing select+start should end emulation and get you back to ES; however I have tried pushing select+start as well as holding select+start on multiple controllers in multiple emulators and multiple games, but nothing happens when I do.
-
I have a Bluetooth controller and set up with the RetroPie; I can use it once I'm in the ES; however if I unplug my USB controller and boot the RetroPie it blocks on a screen saying something like, "No controllers detected, hold button on attached controller to configure." (First of all, plugging in USB controller now won't help; so why doesn't it just say, "Plug in controller and reboot?") Is there a way to get past this screen, as the bluetooth controller connects just fine when you actually get into ES? If not, is there a way for ES to recognize the Bluetooth controller earlier so it accepts it as the main controller and doesn't show up this message?
-
Several systems don't already have pre-made rom directories; for example in my case the Videopac/Odyssey II, the MSX, and the C64. So I used my FTP program to create the directories that the emulators section of the docs mention and copied my games in there. In case of the Videopac I also copied the bios in the BIOS directory (both o2rom.bin and g7400.bin for good measure), yet none of these systems show up in ES. It's like the emulators are not pre-installed, despite the emulators section saying nothing of the sort. It also doesn't say anything about how to actually install emulators (and in the case it says there are multiple emulators to choose from, how to actually do that.)
-
Atari 5200 games don't work. I've tried 4 now, but each time all I get is a blue square with green border and the text, "Atari800/05 emulation halted. (Some numbers and years) This needs a real 05. Go to website to find out more." Almost sounds like it needs a BIOS although the Emulators section and the previously mentioned BIOS section of the docs don't mention requiring one at all. Anyway, I installed said optional bios, and it still does this. Anyone recognize the problem and know what to do?
Will be checking back tomorrow.
-
-
@3DMaster said in Some issues that popped up and oddities I noticed:
Model B+
RetroPie 4.4
Image from Retropie.org.ukSo I'll be off to work in a bit, late shift, then very early shift so it'll take more than 24 hours before I can tinker with the RetroPie again, or come on here to reply, so I figure I put in a post now, and see what pops up. I've noticed a few oddities and some issues, so oddities first:
- A7800 in the emulators in docs it says the bios is optional, only adding an Atari splash screen; and this seems to be the case as I can play A7800 games without a bios just fine; however under the Bios heading in the advanced configuration heading of the docs it mentions the A7800 as requiring a Bios.
where? https://github.com/RetroPie/RetroPie-Setup/wiki/Atari-7800
- The NES, aka the Famicom, accepts certain filename extentions, among them is .sfc. Wut? SFC would be Super FamiCom, aka the Super NES which is what all the Super NES games have as an extension and which is accepted by the Super NES emulator, why is that extension with the NES? And .fc (FamiCom) is not accepted... this is weird.
this does sound wrong to me. eg, nestopia doesn't sound like it supports them: https://github.com/0ldsk00l/nestopia/blob/master/libretro/libretro.cpp#L380
can someone test to see if .sfc files run in NES? if no, then we can edit the docs.
Now some issues I have/questions that need answering:
- Exiting emulation, the docs say that pushing select+start should end emulation and get you back to ES; however I have tried pushing select+start as well as holding select+start on multiple controllers in multiple emulators and multiple games, but nothing happens when I do.
the docs are written on the assumption you have bound 'hotkey' to 'select'. also, there's a long-standing bug in retroarch that means only player 1's controller will register hotkey combos.
- I have a Bluetooth controller and set up with the RetroPie; I can use it once I'm in the ES; however if I unplug my USB controller and boot the RetroPie it blocks on a screen saying something like, "No controllers detected, hold button on attached controller to configure." (First of all, plugging in USB controller now won't help; so why doesn't it just say, "Plug in controller and reboot?")
if i get that message then i plug in my controller and hold a button and it all works?
- Several systems don't already have pre-made rom directories; for example in my case the Videopac/Odyssey II, the MSX, and the C64. So I used my FTP program to create the directories that the emulators section of the docs mention and copied my games in there. In case of the Videopac I also copied the bios in the BIOS directory (both o2rom.bin and g7400.bin for good measure), yet none of these systems show up in ES. It's like the emulators are not pre-installed, despite the emulators section saying nothing of the sort.
the docs don't say what's installed and what isn't - the installed and default emulators varies from version to version so it's not really practical. anything you don't have the folder for, needs installing:
(and in the case it says there are multiple emulators to choose from, how to actually do that.)
-
@dankcushions said in Some issues that popped up and oddities I noticed:
this does sound wrong to me. eg, nestopia doesn't sound like it supports them: https://github.com/0ldsk00l/nestopia/blob/master/libretro/libretro.cpp#L380
can someone test to see if .sfc files run in NES? if no, then we can edit the docs.I think it's just a docs slip up.
The RetroPie extensions for the NES system are configured as
.nes .zip .7z
, both in theplatforms.cfg
file and in Emulationstation'ses_systems.cfg
. The listings on docs.libretro.com forfceumm
,nestopia
andquickness
include the.nes
extension plus.fds
(which is enabled for the Famicon Disk System in RetroPie),.unif
and.unf
. -
@dankcushions said in Some issues that popped up and oddities I noticed:
where? https://github.com/RetroPie/RetroPie-Setup/wiki/Atari-7800
Here: https://retropie.org.uk/docs/BIOS/
(Or in docs pick "Advanced configuration" and then "BIOS".
the docs are written on the assumption you have bound 'hotkey' to 'select'. also, there's a long-standing bug in retroarch that means only player 1's controller will register
hotkey combos.That's complete counter intuitive, the docs should just say, "Hotkey +"
if i get that message then i plug in my controller and hold a button and it all works?
Well, RetroPie decided to accept my Bluetooth device as plugged in controller now, so no more trouble.
the docs don't say what's installed and what isn't - the installed and default emulators varies from version to version so it's not really practical. anything you don't have the
folder for, needs installing:Well, the way it's written, seeing as there is no mention that it might not be pre-installed, very much seems they are pre-installed. I would start any emulator entry that is not installed in the standard official RetroPie image a mention at the beginning along the the likes of, "This emulator is not installed in official RetroPie image, if you want/need it, you will need to install it yourself." would improve understanding, and then a link to where to the explanation on how to do that is located.
In fact, clicking "Emulators" I wouldn't just have in fold out the systems, I would also load a main page in the main pane that contains a basic description of Emulators, BIOS, how to install emulators and how pick between multiple installed emulators. Makes for more intuitive navigation.
Thanks!
-
@3DMaster said in Some issues that popped up and oddities I noticed:
@dankcushions said in Some issues that popped up and oddities I noticed:
where? https://github.com/RetroPie/RetroPie-Setup/wiki/Atari-7800
Here: https://retropie.org.uk/docs/BIOS/
(Or in docs pick "Advanced configuration" and then "BIOS".
it looks like the live version on the wiki has a note that it is not required: https://github.com/RetroPie/RetroPie-Setup/wiki/BIOS
the docs are transposed from the wiki, but this requires manual intervention. it will happen eventually.
the docs are written on the assumption you have bound 'hotkey' to 'select'. also, there's a long-standing bug in retroarch that means only player 1's controller will register
hotkey combos.That's complete counter intuitive, the docs should just say, "Hotkey +"
i agree - i've reworded that section: https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation#configure-controllers
the docs don't say what's installed and what isn't - the installed and default emulators varies from version to version so it's not really practical. anything you don't have the
folder for, needs installing:Well, the way it's written, seeing as there is no mention that it might not be pre-installed, very much seems they are pre-installed. I would start any emulator entry that is not installed in the standard official RetroPie image a mention at the beginning along the the likes of, "This emulator is not installed in official RetroPie image, if you want/need it, you will need to install it yourself." would improve understanding, and then a link to where to the explanation on how to do that is located.
i sort of agree, but like i said, this situation is in flux so i don't think it's appropriate to attempt to record it in the docs, as it's another thing to have to maintain.
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.