Controller Issues (Strange Behavior)

Floob

@veracode
It might be worth starting the game in verbose mode, and then pasting the output to pastebin.

https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging

veracode

I took look through it but don't really know what to look for and don't see anything extremely obvious to me

Floob

@veracode
Ah, sorry I didnt realise it was that type of controller. I'm afraid the closest I have to this is where I map keyboard keys to the controller, but I dont have experience with the dragonrise.
Does this help?
https://retropie.org.uk/forum/topic/9259/so-close-dragonrise-arcade-sticks-and-button-sets-joystick-on-a-player-reverses

https://retropie.org.uk/forum/topic/26386/dragonrise-usb-issues

mitu

Can you also post the contents of $HOME/.emulationstation/es_input.cfg ? I suspect there's a controller name mis-match.

veracode

@Floob
i did read through those before making a new post.
i tried to follow the fixes mentioned in those topics but i dont have those issues.

the first topic you linked SO CLOSE! the controllers are working but mapped incorrectly from what i gathered. but i can't get them to work at all outside of menu navigation and n64

i believe the second Dragonrise USB issues has to do with the autoconfig not applying and creating the files that should be in /opt/retropie/configs/all/retroarch/autoconfig as we discussed earlier. but in my case they are created and are there.

veracode

@mitu

for me this info was located in
/opt/retropie/configs/all/emulationstation

<?xml version="1.0"?>
<inputList>
  <inputAction type="onfinish">
    <command>/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh</command>
  </inputAction>
  <inputConfig type="joystick" deviceName="DragonRise inc. Generic USB Joystick" deviceGUID="03000000790000000600000010010000">
    <input name="left" type="axis" id="0" value="-1"/>
    <input name="right" type="axis" id="0" value="1"/>
    <input name="down" type="axis" id="1" value="1"/>
    <input name="y" type="button" id="3" value="1"/>
    <input name="x" type="button" id="7" value="1"/>
    <input name="b" type="button" id="2" value="1"/>
    <input name="a" type="button" id="4" value="1"/>
    <input name="up" type="axis" id="1" value="-1"/>
    <input name="select" type="button" id="0" value="1"/>
    <input name="start" type="button" id="5" value="1"/>
  </inputConfig>
</inputList>

mitu

Hm, there's no name mismatch.
Can you add to /opt/retropie/configs/all/retroarch/autoconfig/DragonRise inc. Generic USB Joystick.cfg:

input_vendor_id = "121"
input_product_id = "6"

and start again the emulator, to see if the gamepad is recognized ?

veracode

@mitu
ALMOST IN LITERAL TEARS!
Where do I send the beer or coffee?!?!

IT WORKED!!!

Where did that bit of info come from? im looking back through everything ive shared so far and dont see mentions of vendor or product ID

mitu

@veracode said in Controller Issues (Strange Behavior):

Where did that bit of info come from?

Your 1st post:

.. after trying to load a rom in nes i get the message "DragonRise Inc. Generic USB Joystick (121/6) not configured." ..

and this auto profile.

EDIT: I still think there's a name mis-match, the profile from the libretro repo has some spaces at the end, I think they're trimmed by EmulationStation, while RetroArch expects a name with the space at the end.

veracode

@mitu @Floob

Thank you both for all your help
it was something so simple that was looked over.

chicoputo

I want to thank all three of you! I spent hours trying to figure out why I was having this issue trying so many different things. My setup is nearly identical to @veracode . I was about to ditch the Ubuntu PC and buy a Raspberry Pi.

Thanks to @veracode for asking the question and @Floob and @mitu for getting him (and me) to the solution!

I'll likely donate to this project. Cheers!

veracode

@chicoputo cool to see this helped someone else, somthing additional that might be be helpful.

if you re-map the controls you need to reapply the fix.

not sure what but somthing happens that causes it to default back to error state