[Floob]

Try removing the comment from these lines

input_shader_next = nul
input_shader_prev = nul

I can help you get the joypad working properly once this is fixed.

[Floob]

Sorry, I forgot you said you had set your controller to connect in keyboard mode. Is there a reason you dont want it acting as a joypad?
To remove confusion I’d get rid of the joypad controller file, then you know its not conflicting (although I’d use the joypad in a joypad mode really).

Does it still change the shader when you press select on its own?
Can you attach or put on pastebin your updated retroarch.cfg?

Are these lines in it?

input_shader_next = nul
input_shader_prev = nul

[Floob]

Is it still changing the shader when you press select?

Have you got your controller file?
/opt/retropie/configs/all/rectroarch-joypads/

[Floob]

Try setting the value to “nul” rather than commenting it out, like:
input_shader_prev = nul

You also seem to have this set twice?
input_enable_hotkey

[Floob]

1. You’re not doing it wrong, the 56MB partition is all you can see in windows filesystem.
You can access the rest of it like this:
https://github.com/retropie/retropie-setup/wiki/Transferring-Roms
https://github.com/retropie/retropie-setup/wiki/ssh

2. The above methods will help you navigate, but you can set splashscreens using the retropie setup menu script:
https://github.com/retropie/retropie-setup/wiki/splashscreen

3. Question 1 will help you navigate

4.

5. This may help:

6. Check out the wiki, plus I like to apply overlays:

[Floob]

Heres an older thread on the subject:

GameBoy Shaders?

[Floob]

Have you confirmed the romset is correct?
https://github.com/RetroPie/RetroPie-setup/wiki/Managing-ROMs

[Floob]

Here are some different ways of applying visual effects to RetroPie

[Floob]

@scolson1 That sounds like you havent added the udev rule correctly. See the wiki for info.
https://github.com/retropie/retropie-setup/wiki/Setting-up-a-Bluetooth-controller

[Floob]

@abs7 – No one should do it.

@hobbswon Try turning the controller on at different points in the boot up cycle. Make sure the pair hasnt been lost – this can happen if you hold select for 3 seconds. If you did as per the wiki/video it should have added the auto connect rule.
Can you confirm which retropie version you are running – was it from an image?

[Floob]

Bear in mind there is a difference between pairing and connecting. You only need to pair once, unless you hold the select button down for more than 3 seconds to remove the pair.

To reconnect, turn the controller on just as the RetroPie splashscreen appears, the FC30 Pro its just power on for joystick mode, the SFC30 is hold Start+R. Its connected when the led is solid blue.

If emulation station doesnt see it, and it is connected (solid blue) it sounds like your udev rule isnt quite right. Can you post it here?

[Floob]

@hobbswon Thats a different issue, please open a new thread for that one.

@jiepiewie When you re-added it did it connect (solid blue LED)? Which version of RetroPie are you using? Is it from an image? What start up mode are you using on the FC30?

[Floob]

@jiepiewie Try using the bluetooth menu items to de-register the controller and try again. Make sure you havent lost the pairing by accidently holding the select button for 3 seconds – this wipes the pairing.

@abs7 No, that shouldnt need a udev rule. It should just work.

[Floob]

If you are trying to get your bluetooth controller working with RetroPie, please check the Wiki. The process there will auto reconnect on startup.

https://github.com/retropie/retropie-setup/wiki/Setting-up-a-Bluetooth-controller

[Floob]

Glad its working, but for reference no changes to the retroarch.cfg are needed. It has a default setting to autoload the controller configs in /opt/retropie/configs/all/retroarch-joypads which is where ES should generate your clean controller file for you.

Here is a bit of info on how it works

[Floob]

@jiepiewie If the blue lights are flashing it hasnt re-connected. Did it connect ok when you used the bluetooth menu earlier?
Try turning on the controller just as the RetroPie splashscreen appears.

[Floob]

@nbk7

If you want to force a connection you can try this script – make it executable and put it in /etc/init.d/

#!/bin/bash
sudo bluetoothctl << EOF
power on
connect [MAC Address]
exit
EOF

For others reading this, dont do this as the retropie bluetooth menu covers most situations doing this on its own.

[Floob]

But your file has manual edit in, for example your name is in there and other comments.

Which version of RetroPie are you using? Was it from an image?

You may need this line in your retroarch.cfg
input_enable_hotkey = nul

but I would revert your retroarch.cfg back to default until you get it working.
That controller config still looks odd though, I’ve never seen ES generate one like that.
I would delete it and regenerate it with ES.

[Floob]

The button codes for that should be

input_b_btn = "12"
input_y_btn = "15"
input_select_btn = "21"
input_start_btn = "22"
input_a_btn = "11"
input_x_btn = "14"
input_l_btn = "17"
input_r_btn = "18"
input_l2_btn = "19"
input_r2_btn = "20"
input_l3_btn = "24"
input_r3_btn = "25"

Your file doesnt look like it was generated by EmulationStation? It will generate the correct hotkeys for you.

[Floob]

Wiki now updated with guide:
https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller

Video here:

[Floob]

Great, that sounds solved then. You can see me setting the analogues to work here:

[Floob]

The analog sticks work if you configure them in the RGUI, so thats a separate issue really.
Delete all the config files in that controller directory and just create a new one in ES, then post that one in Pastebin, and let us know what button mapping does or doesnt work.
To be honest I dont know why the other one wouldnt work for you, as they are the codes for a FC30 Pro starting in just power mode.

[Floob]

Can you remove the 8BitdoFC30Pro.bak just to make sure its not being read (Although I think only .cfg would be read)?
And can you describe what (or what doesnt) happen when you try playing a game with the FC30 Pro – which game are you trying?

[Floob]

@hobbswon Yes, I skipped the L2 and R2 when I set mine, so that difference shouldn’t matter. Is there only one file in /opt/retropie/configs/all/retroarch-joypads ?

When you say the settings “totally screw my controls” what do you mean? None of them respond? Are you turning the FC30 Pro on just with the Power button as opposed to any button combo?

@pausuri – No, but you can find it here. Just turn the SFC30 on with Start+R
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/8Bitdo-SFC30-GamePad-Bluetooth-Mode(START%2BR).cfg

I’d just rip out the relevant codes and edit your existing file rather than use that file.

[Floob]

@hobbswon – ok cool, so the bluetooth side is sorted its just the mapping then.
If you paste your current controller file to pastebin.com I’ll take a look at the contents.
Although this one should work for the FC30 Pro – is that the exact model you have?
http://pastebin.com/raw/7fGSx8Dd

[Floob]

If its the FC30 Pro, use just the power to turn it on rather than a combo, and you should get a single blue flash pattern.
Then if you follow the Wiki exactly, can you confirm the first step that doesnt do as it describes?

Bear in mind you can (if needed) override your locally generated retroarch file manually with different buttons. The correct mappings are shown here:
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/8Bitdo-FC30-Pro-GamePad-Bluetooth-Mode(POWER)-Mode(POWER%2BR1).cfg

Your local file will be in /opt/retropie/configs/all/retroarch-joypads/

I’ll upload a guide for the Jessie build later.

[Floob]

@hobbswon To confirm – you are using a clean 3.3 Wheezy image (not Jessie) and expanded the FS etc..?

If so, does the wiki guide work for you, as currently that connects in a slightly different way which isnt using the inbuilt bluetooth menu option.
Can you give that a go with the FC30 Pro, as thats the controller I based the guide on.

@abs7 – I have it working on Jessie now, and yes the Wiki is currently based on the previous image, but I’ll update it soon.
I’m keen to try to test a few more things first so that I can use the retropie bluetooth menu rather than a workaround which is what I have now.

[Floob]

@LodanZark That would be great if they were all in one package. If you want I’m more than happy to add them to the video manager tool I manage if you want others to apply them without having to manually edit files:
https://github.com/biscuits99/rp-video-manager

[Floob]

Can you confirm if you are on Wheezy or Jessie? Was it from an image, or have you upgraded the script and binaries?
I’ll give it a go on JEssie 3.4 at the weekend.

[Floob]

This shows you how to remove the RetroPie config menu if that helps:

[Floob]

If it helps I’ll run through the FC30 Pro and SFC30 this weekend with the new build.

@hobbswon Its worth checking out the 8bitdo site to make sure you are on the latest firmware and also check the startup combos as some of the controllers work slightly differently. Most should work simply with the Start button, although the SFC30 certainly seems to like Start+R.

I dont have an FC30 or NES Pro, but for ref here are the startup button configs:
http://www.fc30.com/download/Manual/FC30-Bluetooth-GamePad-Manual-ENG-v1.0.pdf
http://download.8bitdo.com/Manual/NES30_Pro_Manual_ENG_v1.0.pdf

[Floob]

[quote=109812]
Quick question… why isn’t the atari 2600 overlay supported in the tool?
[/quote]

I have linked in other users settings into the tool, so its just that no-one has applied one yet. But if you use the No TV border option and take a look at the retroarch.cfg it produces, you can apply that to the atari one. Or you can put a request/issue in on the github page for it and I’ll see what I can do:
https://github.com/biscuits99/rp-video-manager

[Floob]

Yes, shaders can be great, I’ve rolled davejs into the video manager. Althogh I’ve only applied it there to systems that you would use a CRT with.

[Floob]

When you scrape you can retype the name of the game if it doesnt find it first time, I tend to do that.

[Floob]

Yes, you can do any of the Retroarch based ones.
You can put this in the system based retroarch file – although it only applies the overlay – I’d need to know which system to change aspect ratio etc..

input_overlay = /opt/retropie/emulators/retroarch/overlays/1080p_4-3/Scanlines_4x_1080p_Borderless.cfg
input_overlay_enable = true
input_overlay_opacity = 1.000000
input_overlay_scale = "1.000000"

[Author]

Posts