@deodekabokat If you're on the command line, you can use mc (maybe you're familiar with the Norton Commander/Dos Navigator/etc. interface) and navigate around the filesystem.
Otherwise, you can copy the file on the ROMs folder and look at it over file shares

cp /etc/emulationstation/es_systems.cfg $HOME/RetroPie/roms

I'd advise to use the full image - and not the Berryboot variant - if you can spare a SD card for a few days while you tinker with RetroPie.

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first to your post.
The controller configuration should be done in Emulationstation, it's then automatically translated into RetroArch configuration file(s) so you don't have to re-configure your controller in again in RetroArch.

@lacaca Please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Some how my usb pen drive was corrupted. Uninstaled retropie and did reinstalation process all over again. Must have unpluged pen drive before light stoped blinking so the transfer files with directories not working properly. Everything working properly now.
:-)

@mitu Actually, I meant their physical size, 😊 but their smaller storage size makes backups and upgrades more practical, too. That said, SDHC officially goes up to 32 GB, but there are much bigger "SDHC" cards out there, of which some are said to work in a Pi, so …

I'm using a 32 GB card for my Retropie system and an external ssd for the roms. For my backup, I plug both of them into my PC running Kubuntu Linux (the card via a usb adapter), mount the ssd into the roms directory of the sd, and then backup the whole directory structure like it exists on my Pi. Thus, I do not benefit from the sd card's smaller storage size, but I guess my method is fairly uncommon. 😉

@nans1906 thanks man, yeah i already got it working ;)

@thestarglider said in SNES controller ghosting on Retropie/Kodi etc... An interesting find...:

It would be interesting to know if anyone else had tried an alternative power source to their Pi when they've had issues with ghosting, because in all the threads I have read, I don't remember anyone else bringing it up.

i kinda did :) https://retropie.org.uk/forum/topic/8187/gamepads-making-involuntary-movements-in-emulation-station

the issue is power interference so it figures that changes to power supply or connection can influence it. however it won't fix it for everyone.

@mitu Thanks for your reply, I think I will try to create my own smash Bros

@Mebejedi Well, in lr-mame2010, after you insert a coin, the screen is cleared of the demo, then you can move the ship at the top left or right and fire depth charges left or right, while a sonar sound effect is played and submarines move about below.

@mariobros_54 As @mitu says. ES only displays a system that has roms in its rom directory.

@djultimate I always drop the .bin files in a different folder (usually roms\systemnamecopier\ and then scrape, it will go a lot faster that way instead of the scraper hashing every .bin. Once you finish scraping drop the bin files back in the appropriate folder and you're good to go!

Hi,

I'm trying to do this but I can't, and just found this post with no answers.

I can use hi-res textures with mupen64plus-gles2rice-highres and mupen64plus-GLindeN64-highres only:
· For gles2rice and GLindeN64 you must put the images (.PNGs) in /home/pi/.local/share/mupen64plus/hires_texture
· For lr-mupen64plus I found somewhere that you must use the .htc file generated by some Windows emulator, but I found that file also in Retropie inside /home/pi/.cache/mupen64plus/cache which has been created by GLindeN64 (at least with Super Mario and Mario Kart because others not) but I don't know where to put it. I've read it should be in the "cache folder", but defining it with RGUI and putting /home/pi/.cache/mupen64plus/cache folder, doesn't work...
· For mupen64plus-gles2n64 some works but others not.
· For lr-parallel-n64 and mupen64plus-videocore I don't know if you can use hi-res textures.

Any ideas?

Do you guys think there is fix for this?

Take a look at the Configuration hierarchy. You can have the overlays per-system if you add them to the system's retroarch.cfg file. For individual games, you can use the game override in RetroArch to set the overlays.

@mitu Thank you so much. You were right. I had mixed line endings from editing it on Windows. It install and runs. It runs really slow on the Pi, but I'm sure I'll figure that out.

@hhromic I have changed my script module to include the sources_superflappybirdsfunction as you have suggested. I'll also set it up under the ports folder.

I am hoping to get the game added to zerojay/RetroPie-Extra repo, once it is working well.

@Dwarfboysim It's not essential to know what the numbers mean as I would suggest that the sdl-joymap-C64.vjm file is never edited manually. (except for one possible exception, see below). It is better to make the joystick mappings using the VICE menu as shown in the Sir Randall's Gaming C64 configuration video

I would recommend that, once you have the VICE joystick configuration as you would like, the sdl-joymap-C64.vjm file is backed up, to your PC say, as it can easily be overwritten using the VICE menu, something I found out from experience.

You can find my sdl-joymap-C64.vjm file for a PS3 controller at: https://pastebin.com/93iVpBUT.

The explanations of the array of digits are given in lines 13 to 27 but, I have to agree, they are not the most intuitive. I shall try to explain what the numbers allude to.

Digit 1 is the controller number, 0 being the first controller , 1 the second and so on. Digit 2 is the input type, axis (0), button (1), hat axis (2) or ball (3). Digit 3 is the axis or button number, the button numbers as given by jstest.

The meaning subsequent digits, the action parameters, will depend whether it is an axis or button. Let's look at some examples.

Axis mapping

Digit 4 is whether an axis/button is mapped to C64 joystick (0= No, 1=Yes); Digit 5 is the joystick port; Digit 6 is joystick pin, ie axis direction mapped - 1 is up, 2 is down, 4 is left, 8 is right.
(Note: not 100% certain about this)

Let's take a look at line 33 of sdl-joymap-C64.vjm:
0 0 0 1 1 8
Controller 1 | 0 (Axis Input) | Axis No. 0 | 1 (mapped to joystick) | Joystick Port 1 | pin 8 (Right)
Action: Left analog move to the right

If an axis is not mapped, then the fourth digit would be 0, for example 1 0 4 0.

Button mapping

Digit 4 is the type of mapping
2 mapped to keyboard press;
3mapped to the joystick map function in the VICE menu;
4 brings up the VICE menu (UI),;
5 mapped to a VICE menu (UI) function with the menu path description.

(see lines 24 to 27 of the config file for more info).

Let's take a look at some examples.

Line 43
0 1 1 5 Speed settings&Warp mode
Controller 1 | 1 (Button Input) | Button 1 (L3) | 5 (UI Function) | Speed Settings > Warp mode
Action: L3 toggles Warp mode

Line 44
0 1 2 3
Controller 1 | 1 (Button Input) | Button 2 (R3) | 3 (Joystick Map Function)
Action: R3 maps VICE menu item or key press to joystick button

Line 45
0 1 3 2 7 7
Controller 1 | 1 (Button Input) | Button 3 (START) | Keyboard press (2) | row 7, column 7
Action: START button is mapped to Run/Stop

The key row and column position is given in /opt/retropie/emulators/vice/lib/vice/C64/sdl_pos.vkm, not as seen on the virtual keyboard.

Line 47
0 1 5 4
Controller 1 | 1 (Button Input) | Button 5 (D-pad Left) | 4 (UI Activate)
Action: D-Pad Left button brings up VICE menu

Line 56
0 1 14 1 1 16
Controller 1 | 1 (Button Input) | Button 14 (CROSS) | 1 (mapped to joystick) | Joystick Port 1 | pin 16 (Fire)
Action: CROSS is joystick fire button

If there are multiple mappings, then it is possible to disable buttons. For example, in my config, the Joystick Map function is mapped to button 2 (R3), button 6 (D-pad down) and button 12 (Triangle). If I wished to disable the function for button 6, then I could edit the entry (line 48) to 0 1 6 0. This is the only manual edit I would be comfortable in making.

Note: some of this information may be inaccurate as I'm not 100% familiar with the C64 hardware.

TL;DR
Do not manually edit the joystick mapping file sdl-joymap-C64.vjm. Use the VICE menu as described in Sir Randall's Gaming video.

Back up the joystick mapping file.

So I figured it out I believe. You were right on with my joystick. It was mounted opposite of the other one. I also realized that the reason the start button just stopped working is because the master controller which as you say there is only one for now. Is the other controller so it works in menu but not in game. Which makes sense now knowing the retroarch and all hotkeys only apply to the master. Thanks for the insight

@PolarBear123 BIOS files, just like ROMs, are copyrighted assets - they're not distributed with RetroPie and links and request for such items are not within the forum rules.