[theroamer]

I posted in your thread as well. (my guess is it got downvoted because of the title) Retropie is constantly evolving and there are always little issues like this. I’m sure this one will get figured out. Not a reason not to buy this controller as it’s pretty sweet otherwise.

[quote=121746]I’m also having this issue, along with many more. I posted this issue on Reddit but got down voted.

https://www.reddit.com/r/RetroPie/comments/4c29pr/do_not_buy_the_8bitdo_nes30_pro_controller_for/

BTW, you know you’re in Joystick mode because you’ll see “Joystick” in “8Bitdo NES30 Pro Joystick”. If you we’re in Joystick mode, the name wouldn’t have “Joystick” in it.

[/quote]

[theroamer]

yeah, I’ve tried both keyboard mode and joystick and same issue. The dpad does seem to work though. It leads me to believe that retroarch is pulling the bindings from some other config file rather than the one in /opt/retropie/configs/all/retroarch-joypads since changing settings in there seems to make no difference.

FWIW I’m also on the latest version of the 8bitdo firmware 1.69

[theroamer]

Tried that and it didn’t seem to change anything. I set it up originally with start + R1 so I think it already was in joystick mode. Any way to tell for sure?

[theroamer]

Hi, thanks for the update! Got a question on a few issues I’m having.

1. nes and mame are in tiny windows instead of full screen. I checked in /opt/retropie/configs/all/retroarch.cfg and it looks like it’s set to 1280×720 so I’m not sure why this is happening. Changing it doesn’t seem to have any effect. Any ideas?

2. None of my advmame roms seem to work, they all say missing files. They all work flawlessly in the standard retropie install but in your image, none seem to work.

Thanks again for this, hoping I can get these 2 issues fixed and move over to your image permanently.

[theroamer]

Thanks so much for putting this together, it’s exactly what I’ve been looking for.

I am having one issue though I’m hoping there’s a fix for. I switched skins to the default in kodi just to see what it looked like, I then switched back to the aeon theme and everything looked correct. After I launched Retropie from the menu and went back to Kodi, the Aeon skin looks like it has reverted to default settings and there is no menu item to launch Kodi, is there any fix for this short of re installing the image?

Thanks!

[theroamer]

Well, after trying everything I could think of, I went out and bought a pi 2 and swapped it with the B+. All the problems I had are gone and I can keep the wifi and bluetooth plugged in without performance problems.

Thanks for the replies.

[theroamer]

Using an iBuffalo classic with the SNES layout. I’ll unplug and see if it’s still happening.

[theroamer]

[quote=101181]Not sure how much this affects things but Wicd-curses while convenient for configuring wifi can affect processing with overclocked pi’s. Other than that I don’t know. Have you tried switching the default emulators?

[/quote]

My pi isn’t overclocked and I’m using the standard emulators.
Mame runs fine but Atari 2600 and NES both have this glitch.

I’ll look into switching default emulators and see if that helps, however, I’m using the default emulators on the older retropie image and everything runs smoothly.

[theroamer]

Update:

I got a new power supply and the rainbow square did indeed go away, however, I’m still getting sound and video lag every 4-5 seconds when in both nes and atari. I pulled my wifi and bluetooth dongles and rebooted. After that the lag is better, but I still get a similar, shorter lag every few seconds.

I don’t get this lag at all in the older version of the retropie image, just in 3.0 beta 4. I’m using the same roms. Boot to the old retropie, flawless play, new retropie, intermittent lag.

Any other ideas what could be the issue?

[theroamer]

I am getting the rainbow square. I’ll try ordering a new power supply and see if that helps. Thanks!

[theroamer]

I should add I’m running it on a B+

also, I don’t seem to have the stutter problem in MAME, only the game systems I listed. I tried adding the following to /opt/retropie/configs/all/retroarch.cfg

audio_out_rate = 44100
audio_driver = sdl

but that doesn’t seem to do anything.

[theroamer]

This guide worked for me.

https://github.com/retropie/RetroPie-Setup/wiki/Setting-up-a-PS3-controller

[theroamer]

Are your nes/snes roms zipped? If so they need to be unzipped and the .nes / .smc files should go in ~/RetroPie/roms/nes and ~/RetroPie/roms/snes

For the mame controller issue, try loading a rom, hitting tab, then configuring your controller from the menu.

[theroamer]

Sweet, that worked. Thanks!

[theroamer]

Looks like I fixed it. I guess the controller binds are different for bluetooth.

Added the following to
/opt/retropie/configs/nes/retroarch.cfg

input_device = “Sony Computer Entertainment Wireless Controller”
input_driver = “udev”
input_enable_hotkey_btn = “0″
input_b_btn = “14”
input_y_btn = “15”
input_select_btn = “0”
input_start_btn = “3”
input_up_btn = “4”
input_down_btn = “6”
input_left_btn = “7”
input_right_btn = “5”
input_a_btn = “13”
input_exit_emulator_btn = “3”
input_menu_toggle_btn = “12”

all the buttons now work in nes, and I can exit games by hitting select+start or bring up the retroarch menu with select+triangle

[theroamer]

I’m using a ps3 controller. Works great plugged in via usb. Works in mame over bluetooth but I have yet to get nes/snes to recognize it over bt.

[Author]

Posts