Skip to content

Commit 468f156

Browse files
authored
Merge pull request #1058 from barbudreadmon/patch-4
Update fbneo.md
2 parents ab5a3c2 + 66accc2 commit 468f156

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

docs/library/fbneo.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -305,11 +305,13 @@ As far as we are concerned, you are supposed to dump your own games, so we can't
305305

306306
### Why am i getting a white screen ?
307307

308-
The white screen tells you if the romset is supported at all and which files are wrong or missing.
309-
Especially, if present, the line "Verify the following romsets : <romset> <parent> <bios>" tells you the list of romset/parent/bios needed by the romset you are trying to run.
308+
If present, the line `Verify the following romsets : <romset> <parent> <bios>` gives you the list of split romsets required by the game you are trying to run. This is mainly for reference since you might not be striving to use romsets in split format. The next few lines give you the list of files it couldn't find within those romsets.
310309

311-
Exceptionally there might be a false positive due to your file being unreadable for some reason (file corruption during transfer, file permission, damaged disk drive, ...).
312-
This is a rabbit hole and something you should only concern yourself if you already used clrmamepro to verify your romsets.
310+
Otherwise, a `Romset is unknown` message means the romset couldn't be found by its filename in our database.
311+
312+
Both problems result from not reading the [arcade documentation](https://docs.libretro.com/guides/arcade-getting-started/#step-3-use-the-correct-version-romsets-for-that-emulator). Exceptionally there might be false positives due to your files being unreadable for some reason (file corruption during transfer, file permission, damaged disk drive, ...). This is a rabbit hole and something you should only concern yourself after using clrmamepro to verify your romsets.
313+
314+
Rarely you could get a "Failed initializing driver" message, this is something you should report [here](https://github.com/finalburnneo/FBNeo/issues)
313315

314316
### How can i run that romhack i found ?
315317

@@ -450,6 +452,10 @@ It is common for arcade machines to execute self-tests at boot, and in many case
450452
Sometimes the NVRAM/EEPROM saved on your disk gets corrupted for some reason, Konami games are especially known for getting this issue *somewhat frequently*.
451453
NVRAM/EEPROM are saved in the `SAVEFILES_DIRECTORY/fbneo` folder, and you can get around this issue by finding the files corresponding to your game and deleting them.
452454

455+
### Should i use retroarch's analog-to-digital feature ?
456+
457+
You should **NEVER** use that feature with this core, it already converts analog to digital and digital to analog internally. Exceptionally it might not do that conversion because each of those controls are already doing their own thing.
458+
453459
### Where is SYSTEM_DIRECTORY ?
454460

455461
Open your `retroarch.cfg` file and look for `system_directory`, or check `Settings > Directory > System/BIOS`.

0 commit comments

Comments
 (0)