• Garbled Audio when crt shaders enabled

    5
    0 Votes
    5 Posts
    982 Views
    AlturisA

    @dankcushions said in Garbled Audio when crt shaders enabled:

    the ‘new style’ xmb menu is not enabled in retropie by default. we use the old green menu for these kind of reasons. i guess your configs are all messed up and it’s using default retroarch settings, so all bets are off.

    Yep. I got it fixed now. Not even sure how exactly but I noticed that my nes and gb system cfg files had a ton of stuff in there copied from the default retroarch. I just rebuilt them by hand and all is well now.

  • SSH retropie msg logo doesnt show

    4
    0 Votes
    4 Posts
    663 Views
    W

    @sano I would try later, but you are probably right.

    ~ edit ~ It works. Thank you dude.

  • Need help with psx controller config

    9
    0 Votes
    9 Posts
    3k Views
    J

    So i tested the remote on some snes games and the shoulder buttons worked. I also have been able to play some ps1 games also. Not sure whats going on but it didnt work this well last time i messed with it nor did the graphics look as good and i hadn't messed with it since i encountered the issue about a month back.

  • Analog Input Help

    1
    0 Votes
    1 Posts
    424 Views
    No one has replied
  • 0 Votes
    2 Posts
    641 Views
    R

    I think I have now resolved this issue - for anyone else who has suffered from similar woes, I quit out of Emulation Station and did

    sudo rpi-update

    to update the firmware. Now the left and up axes seem to be recognised properly - watch this space to see if I have other problems! (I'll bet good money that I do lol)

  • N64 with 7" CVT Display

    3
    0 Votes
    3 Posts
    723 Views
    S

    @obsidianspider Thanks for the reply =), no that is not the problem. The problem is that the emulator dont use the CVT standard.

  • Raspberry Pi, Xbox online gaming, and Xkai

    Moved
    18
    0 Votes
    18 Posts
    3k Views
    AddisonA

    What exactly did that do though?

    I would like for the script to only execute when I click on an icon or something of it in Emulation Station.

    Sorry if I'm still being a pain on this. :(

  • How can I use this to power my raspberry pi 2?

    1
    0 Votes
    1 Posts
    536 Views
    No one has replied
  • Help with LED??

    Moved
    4
    0 Votes
    4 Posts
    1k Views
    cyperghostC

    @psychosious You can also try to connect to 3.3 rail directly!
    This might work for a status LED (on/off/error). If you want to use it for illumination effect the 3.3V can be a bit low.
    Usually the forward current for blue LEDs are 2.9-3.1V
    Keep in mind, the 3.3V rail delievers only 100mA!
    That's enough for a few microcontrollers and a bunch of LEDs - not enough for your XMas tree!

  • Switch to desktop with CLI (not startx)

    2
    0 Votes
    2 Posts
    2k Views
    mituM

    @rasp_renegade said in Switch to desktop with CLI (not startx):

    What am I doing wrong?

    Did you install the desktop environment on your system ? As noted in the https://retropie.org.uk/docs/FAQ/#where-did-the-desktop-go, you need to install the Pixel DM from the script, then exit ES and execute startx only.

  • 0 Votes
    9 Posts
    2k Views
    mediamogulM

    @bland328

    Actually, in both cases you'd need an external tool. I use xboxdrv, as outlined in the guide I linked to above. Having analog movement available on the stick comes in handy for everything from 'Marble Madness' to 'Spy Hunter'. It's especially nice in 'Centipede', where you're normally all over the place much too quickly with digital controls.

  • 0 Votes
    7 Posts
    1k Views
    V

    @clyde That's right, edit 10 solved my initial query from the topic post, and edit 9 solved the second problem of poor wifi performance caused by wminput.

    I think for most users who are trying to fix the latter issue, wminput -q -w would be perfectly acceptable. This way, wminput will keep searching (-w, waiting) for the Wiimote until it connects (clobbering wifi in the process). The "risk" here is that you can't find your Wiimote, or it's out of battery or something, so your Internet will go dead until you manage to get it synced. For me, when the entire network is relying on the Pi maintaining its connection, I'm better off with it timing out "just in case" the Wiimote isn't available, vs. the extra convenience of being able to connect any time after EmulationStation starts.

    The biggest loss here is not being able to reconnect Wii Remotes after a disconnect, e.g. because of drained batteries, especially if it happens mid-game. Presumably you can SSH in and run attachwii again whenever you're ready to reconnect. Not terribly pretty, but for users who need their wifi up it's the best tradeoff I can see, short of changing how you handle your connections (e.g. wired internet, separate Bluetooth dongle, etc.)

    There's probably a middle ground somewhere where you have a version of attachwii running in the background that periodically runs an hcitool scan and greps the result for your Wiimote, launching a wminput -q [-w] to reconnect if it finds it. Depending on how often you ran the scan it might not have the same devastating effect on your wifi, and it would otherwise be similar to running wminput -d, in terms of getting you (re)connected at arbitrary times. I'm just spitballing here though, I'm not sure how much impact hcitool scan has on wifi performance on a Pi 3 or other setups where BT/wifi interference is a major issue. For all I know, running hcitool scan constantly is just what wminput is doing behind the scenes that's causing all the problems.

    EDIT: I also quickly threw together /home/pi/RetroPie/roms/ports/Attach Wiimote.sh:

    #!/bin/bash attachwii >/dev/null 2>&1

    This can be run from the Ports menu in EmulationStation to sync the Wiimote without having to exit to command line to do it. It's of limited use, basically just if you forget to connect or get disconnected while you're in the EmulationStation menu. It's no help if you get disconnected mid-game, ssh is still the best option there currently.

  • Atari 2600 (lr-stella) + crt-pi.glslp shader or similar

    16
    0 Votes
    16 Posts
    2k Views
    dankcushionsD

    @alturis said in Atari 2600 (lr-stella) + crt-pi.glslp shader or similar:

    @clyde said in Atari 2600 (lr-stella) + crt-pi.glslp shader or similar:

    @alturis Have you by any chance saved a game override in addition to the core config? See Config Hierarchy.

    Nope. My atari2600 roms folder has no .cfg files in it at all. I have even installed locate, updated the db, and searched for al cases of atari2600 and there are no other .cfg files with that name in it other than the one I expect.

    game overrides are not stored in rom folder. they would be in (from memory) /opt/retropie/configs/all/retroarch/config/ (somewhere in here)

  • Getting weird code when starting up Retropie

    17
    0 Votes
    17 Posts
    3k Views
    PokeEngineerP

    @Arie, @XboxWin

    That pop-up format message seems to be a new thing in the latest Windows 10 update.
    It's a bit annoying for me when every time I flash an image, I have to close it out.

  • Daphne Input Config Issue

    1
    0 Votes
    1 Posts
    611 Views
    No one has replied
  • Making PSX roms take less space

    8
    0 Votes
    8 Posts
    11k Views
    X

    @nicky_s14 did you read that

  • My ibuffalo’s controls are messed up on retropie

    1
    -1 Votes
    1 Posts
    413 Views
    No one has replied
  • 0 Votes
    5 Posts
    4k Views
    D

    I had no trouble to connect both x-Box one s controller via Bluetooth (pi 3b - disable ertm and updated retropie and the both controllers via my Xbox one). I conectet the first one and after it was done I connected the other one. But I have trouble to configure them in the retroarch GUI. Does the controllers work in retroarch gui for you?

  • Retroarch Key Binding - Lost Back Key

    3
    0 Votes
    3 Posts
    1k Views
    ClydeC

    @baviaannl The keybindings are stored in different files depending on how you saved them: globally, per core, per game, hardcoded, or as a remapping. See the docs about controllers for details.

    Since remapping shouldn't alter the retroarch menu keys, I think you've saved your keys hardcoded in one of the possible files called retroarch.cfg in the directories /opt/retropie/configs/all/ (global) or /opt/retropie/configs/neogeo/ (neogeo core). In these directories, there should also be files called retroarch.cfg.rp-dist with the default settings. To reset your settings, replace the file retroarch.cfg with the file retroarch.cfg.rp-dist in the same directory. This can be done from Retropie's command console that you land in if you quit Emulation Station without reboot or shutdown:

    # make a backup copy of your global settings cp /opt/retropie/configs/all/retroarch.cfg /opt/retropie/configs/all/retroarch.cfg.backup # replace current global settings with the defaults cp /opt/retropie/configs/all/retroarch.cfg.rp-dist /opt/retropie/configs/all/retroarch.cfg

    For your neogeo core settings, replace all with neogeo in both command lines. (Four times all, two on each line. The lines beginning with # are just comments.)

  • Drastic input problems

    7

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.