[petrockblog]

I have built it yeh – you will need to re-enable the swap I guess.

[petrockblog]

[quote=101478]Sorry for the delayed response. I’ve had some other things on my mind lately…

I finally took the time to test the ControlBlock with the new ControlBlockService and it all seems to work now!

Thanks for the fix Florian!

[/quote]

Glad to hear that!

[petrockblog]

I have not seen that behavior yet, interesting. Does this also happen with the ControlBlock connected, but without any connections to buttons and joystick(s)?

[petrockblog]

If you are running RetroPie version 3 Beta 4, I would suggest to update the RetroPie setup script and do a full binaries (re-)installation with the RetroPie-Setup Script. I know that there are some issues in that beta version.

Alternatively, you could provide me the SD-card image and I would directly take a look at that.

[petrockblog]

First time, I am facing this problem. Could you describe your setup a little bit more? Just trying to get an idea for the cause of this error …

If you have the possibility you could provide an image of your RetroPie sd card (e.g., at Google drive or Dropbox) and I could have a detailed look at it myself.

[petrockblog]

Already marked as solved. Could you describe your solution here briefly?

[petrockblog]

im working on some changes in the next day or two that should improve this for the next beta, but for now you can try the hotkey option in the supplementary menu and disable the hotkey button or something or change it to something else. That may well sort it.

[petrockblog]

or do you mean you want to modify the launch script ?

[petrockblog]

what do you want to change ? I should think the kodi config folder is the same as on any linux in ~/.kodi

[petrockblog]

not sure anyone has ported it to the rpi yet.

[petrockblog]

You can also just do a full binary install, which will then download rpi2 optimised emulators (It detects which rpi it’s running on).

[petrockblog]

you could create subfolders inside the c64 folder – there are no theme graphics for vic / plus4 either currently. I’d consider adding more folders if other users thought it would be useful (but still keep it so they can all be launched from the c64 folder too).

[petrockblog]

you can browse windows network shares from cinnamon – just use nautilus or so. There should be plenty of information on this on the web.

[petrockblog]

It is shared by default – if you give me details of desktop & os I can advise how to access the share.

[petrockblog]

you could try editing this manually – removing

input_l2_axis = "+2"
input_r2_axis = "+5"
input_r_x_plus_axis = "-4"
input_r_x_minus_axis = "-4"
input_r_y_plus_axis = "-4"
input_r_y_minus_axis = "-4"

and see if that helps – or cut it down even more with just directions and ab xy –

also please post /opt/retropie/configs/all/retroarch.cfg

[petrockblog]

please post the contents of the file(s) in in /opt/retropie/configs/all/retroarch-joypads (this folder is accesssible over samba/windows file sharing)

Then remove them, and go to retropie-setup in emulationstation and go to supplementary menu, and run the retroarch input configuration option. Configure your joypad there, and then test if the controller works in emulation. Please also post me a copy of that controller config – which should be in the same location as above.

please use a pastebin site for posting the configs.

[petrockblog]

the controller issue is something else I think – the OP shoudl also try another controller out – strange it suddenly stopped working, so maybe something unrelated to retropie.

[petrockblog]

try doing a full binary install then – in case you had an older retroarch / emulationstation script that used the old controller location or something (which it shouldn’t since you updated recently).

I cant help without more details / logs etc – does retroarch show your controller when you unplug / plug it in during emulation ?

[petrockblog]

The original issue was a bug in recent retroarch which is now fixed. re-installing retroarch from menu 5 should resolve it.

[petrockblog]

Fixed – it was an upstream retroarch issue with commandline parsing. If you re-install retroarch from menu 5 in retropie-setup it should sort it.

[petrockblog]

Follow progress here – https://github.com/RetroPie/RetroPie-Setup/issues/890

[petrockblog]

can confirm – ill debug and put up a new binary.

[petrockblog]

I recently rebuilt all binaries I’ll check if retroarch is broken again or something.

[petrockblog]

If you can’t set up ssh I can’t really advise further. Why not ?

[petrockblog]

You dont use startx to load emulationstation you just type emulationstation.

you need to reboot if adjusting config.txt, but I can’t advise further other than what is on that page and other threads on the forum with ideas. usuaully hdmi_drive sorts it if using dmt mode and you want sound over hdmi.

[petrockblog]

I dont know if I can help fix it without reproducing the problem – and I would need the controller for that.

the above doesn’t seem to make much sense as restarting emulationstation is the same as quitting it and reloading. I still suspect its a timing thing.

you could editing /usr/bin/emulationstation (sudo nano /usr/bin/emulationstation) and add “sleep 10” around the second line and see if that helps ?

[petrockblog]

you can ssh in or press f4 to quit emulationstation. details about ssh are on the wiki

[petrockblog]

Nice :) please do – always interesting to see projects – even better do a video ;-)

[petrockblog]

it would also help if you could try with a wired controller, so we know if it’s specific to this device. I have a feeling it’s due to ES starting before the controller is fully “configured” (the test above exsiting/restarting will help to determine that)

[petrockblog]

very odd – I’ll try and reproduce, but I have no idea currently why it might do that. I can only think that at the point of ES loading it doesn’t see the controller for whatever reason. If when it asks for controller configuration again, try pressing f4 to quit (and then a keyboard button to drop to terminal), then unplug and plug controller back in, wait some moments, and reload emulationstation (by typing emulationstation) – does it still ask ? is this consistent or not ?

[petrockblog]

having said that, you have an emulationstation input configuration present so it should be using that (and recognizing that is the config for your currently plugged in joypad).

please update retropie-setup script, then re-install emulationstation from binary (menu 5 in retropie-setup), and reboot. emulationstation should ask for controls to be configure again – please do that and then repost the above files.

[petrockblog]

you will need to update the retropie-setup script first, before running the full binary install. you are probably missing the scripts the new emulationstation needs

[petrockblog]

Please start with a 3.0beta4 image – Far too much as changed since 2.6 to guarantee an automatic upgrade. Did you update the script before you updated the binaries ? You can’t just update the binaries on 2.6 as some of the binaries as set up for working with the latest script.

[petrockblog]

Also please post the contents of

~/.emulationstation/es_input.cfg
~/.emulationstation/es_input.cfg.bak
~/.emulationstation/es_temporaryinput.cfg

(via site like pastebin or similar)

[petrockblog]

Did you install from the last image (3.0 beta4), or update from an older version ? Have you done a full binary install if you have updated the script recently ?

[Author]

Posts