Editing Emulators
From Retroid Handhelds
Jump to navigationJump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
== Emulation within Retroid OS == | == Emulation within Retroid OS == | ||
There are no changeable settings for emulators within RetroidOS, and currently there is no way to add new emulation cores. Switch to the Android OS for custom options. | |||
RetroidOS supports the following systems out of the box, with the listed emulator cores for Retroarch: | RetroidOS supports the following systems out of the box, with the listed emulator cores for Retroarch: | ||
Line 692: | Line 694: | ||
| Standalone | | Standalone | ||
| Free | | Free | ||
| Shows no directories on launch. | | Shows no directories on launch. Fix is to search for a game and place a “/“ in the search box and select “Choose”. This will bring up the directory listing. | ||
|} | |} | ||
Line 699: | Line 701: | ||
==== N64 Emulation Tips ====[New] | |||
With over 300 games tested with the universal profile provided by Expertwooden, | With over 300 games tested with the universal profile provided by Expertwooden, | ||
Retroid Pocket 2 is now able to play most of the | Retroid Pocket 2 is now able to play most of the N64 games smoothly without further configurations. | ||
You can find the video tutorial here | You can find the video tutorial here: | ||
https://youtu.be/nF8Mb9WIF5Q | https://youtu.be/nF8Mb9WIF5Q | ||
You will need a specific Mupen64 FZ version: | You will need a specific Mupen64 FZ version: | ||
Line 717: | Line 712: | ||
==== N64 Core Tips ====[Old] | |||
You can use N64 in your RP2 with RetroArch (so you can use RetroAchievements, for instance). Not every game runs | You can use N64 in your RP2 with RetroArch (so you can use RetroAchievements, for instance). Not every game runs perfect, and many need further tweaking, but overall you should be pleasantly surprised. | ||
This only works with Mupen64Next or NextGLES2 (GLES3 and Parallel simply crash). | This only works with Mupen64Next or NextGLES2 (GLES3 and Parallel simply crash). | ||
Line 733: | Line 728: | ||
Please note: | Please note: | ||
* Use only glide64 for video ( | * Use only glide64 for video (angrylion is slow, parallel simply fails). | ||
* All Mupen Cores share the same configs. | * All Mupen Cores share the same configs. | ||
Line 739: | Line 734: | ||
===Dreamcast Configuration Tips=== | ===Dreamcast Configuration Tips=== | ||
This only applies to beta batch units (Pink, Blue, and Orange). Later units do not include Reicast and include Flycast pre-installed by itself. | This only applies to beta batch units (Pink, Blue, and Orange). Later units do not include Reicast, and include Flycast pre-installed by itself. | ||
Configuration for the pre-installed Flycast Standalone app is done through the pre-installed Reicast app. Flycast will have | Configuration for the pre-installed Flycast Standalone app is done through the pre-installed Reicast app. Flycast will have better performance than Reicast. | ||
Open Reicast and click on the DC BIOS and format Memory Card 1. For controller settings, set the ports of all to "None", and the port for Android PlayStation to A. Click Map, and map the buttons to their appropriate locations - you may not need to map all buttons. Click Done, then Done again. You may now close Reicast. | Open Reicast and click on the DC BIOS and format Memory Card 1. For controller settings, set the ports of all to "None", and the port for Android PlayStation to A. Click Map, and map the buttons to their appropriate locations - you may not need to map all buttons. Click Done, then Done again. You may now close Reicast. | ||
Line 747: | Line 742: | ||
Launch Flycast, which shares a config with Reicast, and load and play your game. | Launch Flycast, which shares a config with Reicast, and load and play your game. | ||
If there are issues with the controller, you may need to modify the .cfg file in Flycast. To do this, go into the directory path for Flycast and find the folder named mappings. Inside, there should be a file named Android_Playstation3.cfg. Open the file, scroll to the bottom, and erase the line for | If there are issues with the controller, you may need to modify the .cfg file in Flycast. To do this, go into the directory path for Flycast and find the folder named mappings. Inside, there should be a file named Android_Playstation3.cfg. Open the file, scroll to the bottom, and erase the line for deadzone value. This should not be needed if Reicast 20.02b or newer is installed, or if you have used the .cfg file. | ||