Icade supported? Also, a couple of other problems

RetroArch Apple devices
#1

I recently bought and icade and since I have a jailbroken ipad, decided to give retroarch a try but I’m running into all sorts of issues here:

  1. How do I set the default rom directory? I know there is a path option through the frontend settings but that only seems to affect the rgui.
  2. How do I get my icade to work? I figured retroarch would auto detect the controller, the same way it auto detects my Shield and DS3 with the android version but it doesn’t.
  3. Is there a way to disable the input overlay? Initially there was no overlay. I selected the snes one to test and now I can’t find an option to disable it.
#2

  1. Have you tried manually binding buttons through RGUI (in-game menu)? I don’t have any iDevices, so I’m not sure if this works or not, but it’s the first thing I would try.

  2. Either press ‘start’ on the overlay to set it back to the default value (i.e., no overlay) or choose the ‘immerse’ overlay, which is blank by default, but if you tap the screen, it brings up some handy functions, like savestate, rewind, etc. so you don’t have to map all of that stuff to your gamepad.

#3

1-Retroarch.app>Frontend>Global Core Config>Paths>Content Directory> go to your desire folder then hit [Use this folder]. you should apply this on all config cores you have created for example Retroarch>Frontend>N64 or psx…

2-pair iCade via settings.app>bluetooth>icade connected------- then go to Retroarch.app>frontend>bluetooth input type>iCade then map the buttons, Retroarch.app>Frontend>Global Core Config>inpust>player 1

3-this is two ways to hide the input overlay. 1- tap on little settings icon it will show you quick Menu then tap on little arrow facing down to minimize the window.

    2- tap on the setup menu then go to frontend>global core config>input>Overlay Opacity. make it 0.0 if you to reappear again, just make       Overlay Opacity 0.5.  this apply for all core configs you have create.

by the way any changes you made on any core config, it will create new core config under frontend> Configuration so any changes you make on global core config will not apply on any core config that already have been created.