Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • in reply to: DosBox help please #109229
    luckylocky
    Participant

    all good its solved. I reinstalled binaries which put the startdosbox Which i had deleted) back in emulator folder. it worked when i clicked on gtf then :)

    cheers for help

    in reply to: DosBox help please #109225
    luckylocky
    Participant

    Thanks ronoh55 that worked! you the man. So i was able to play my game gtf (good to firm) in the dosbox emulator. But i am still stuck how to launch it from ES. I have followed the instructions

    run the following commands.

    cd ~/RetroPie/roms/pc
    sudo nano gtf.sh

    Copy and paste the code below.

    #!/bin/bash
    /opt/retropie/emulators/dosbox/bin/dosbox -c “mount c /home/pi/RetroPie/roms/pc” -c “c:” -c “cd gtf” -c “GTF.EXE” -c “exit”

    Save and exit. Next make the gtf.sh executable so it can be launched from emulationstation.

    sudo chmod +x wolf3d.sh

    when i type this last line ^ and press enter is it suppose to say anything? mine just goes to the next line ready to type command again.

    so the GTF folder now shows up in my IBM folder but when i try ;aunch i get an error that is the usual oe when roms dont work. im so close :) at least i can play it but pain in the but having to mount everytime. This would be so awesome if I could get launching from ES.
    Thanks for any help

    in reply to: Mupen64Plus Issues #109136
    luckylocky
    Participant

    I had Mariokart working perfectly with retropie 3 but once i upgraded to 3.1 no matter which emulator i boot in too the menu screens writing is distorted. the game still plays fine if you manage to navigate the blurry menu. has anyone got mario kart running with retropie 3.1? need help

    in reply to: Autofire on the axis #108683
    luckylocky
    Participant

    Awesome you figured it out, I thought it should be working seems that’s how I did mine. I looked at your code but didn’t spot the mistake :/ feederchain is the man. Now the fun of trying to get all your Roms to work.

    No divorce now ;)

    in reply to: Autofire on the axis #108675
    luckylocky
    Participant

    Sorry ttown im new too, just got it working from this forum, i didnt do the kernal just the cmd line think and it worked, just one space and then type it. after shutdown and boot i could configure both sides of my controllers. Sorry hopefully someone else can help with the more technical stuff

    in reply to: Autofire on the axis #108664
    luckylocky
    Participant

    Hey Ttown209 it worked for me, I see you copied the line eaxctly i had to change it to my vendor/product code. are you sure your vendor/product code is the same as feederchains? mine was different i followed this post below to find my vendor/product code

    OK… so monchote…. you sparked something in my brain with your talk of quirks. Or at least that patch you referenced.

    While I has dealing with this months ago I remembered reading something about adding a quirk on boot. But I didn’t get it to work. Looking back now, it’s because I didn’t know what I was really doing then.

    Anyway… So I figured out my vendor/product ids 1292/4745.

    Which is when the spark happened. So you are allowed to add the following to the end of /boot/cmdline.txt

    usbhid.quirks=0x1292:0x4745:0x040

    The first two numbers are my vendor/product. The third is the quirk. Found here http://lxr.free-electrons.com/source/include/linux/hid.h#L313

    So the 40 is for multi input.

    So with my kernel and this above. I was seeing two controllers and they both worked.

    You can find the vendor/product using
    lsusb

    returned this for me
    Bus 001 Device 005: ID 1292:4745 Innomedia

    So the next logical step was to try and use HID_QUIRK_NOGET with a virgin kernel and see if the directionals work. Replaced the 40 with the 8.

    Unfortunately that didn’t work for me.

    Hopefully for you compiling in the quirk will help.

    in reply to: Autofire on the axis #108137
    luckylocky
    Participant

    Hey it worked for me, did you look up your own vender product numbers? If u did it correctly it will work, it did for me. I didn’t need to download the kernels, just followed the instructions from above posts for cmdline

    in reply to: Autofire on the axis #107585
    luckylocky
    Participant

    All good, changed the wiring, it’s all working great now, appreciate your help and quick replies! Cheers

    I’ll have to keep searching for others with n64 problems. Update 3.1 is not old enough yet

    in reply to: Autofire on the axis #107575
    luckylocky
    Participant

    I wired it up like this, so guess I assume player 1 was left. Guess I better change them over grrr
    Cheers feederchain

    Anyone have any help about my n64 problems?

    in reply to: Autofire on the axis #107574
    luckylocky
    Participant

    Bugger, well I’m
    Hopeless with any Linux stuff. I wired it exactly how instructions on xin mode told me, massive pain in the but to change all the wires over :(

    in reply to: Autofire on the axis #107568
    luckylocky
    Participant

    Looks like button mapping index is swapped. I did a jstest and player 1 was js1 and player 2 was js0. So how do I swap them?

    Appreciate the help, my family all arrive in 2 days so would be awesome to have fixed and running properly :)

    Also struggling with n64 emulator the first one runs blurring in menu’s but races fine except joystick doesn’t work? Guessing cause in uses analog controls n not dpad which my joysticks assigned too, other 2 emulations don’t boot (they use to in retropie 3.0) so I installed the experimental ones n they run fine but no buttons work in game :(

    in reply to: Autofire on the axis #107499
    luckylocky
    Participant

    All I did is your cmdline.txt then booted up retropie and held button on arcade left side. N mapped it, then held button on right side n mapped it. I notice when I held button left side said player pad 3 n right side said player pad 2. I did have a PS3 controller plugged n which was pad 1. Xin mo is wired up correctly so not sure why it is swapped. Maybe I held down left side first so it recognized it as pad 2? Could it be that simple?

    in reply to: Autofire on the axis #107488
    luckylocky
    Participant

    Hi
    I too have just signed up to say thankyou. I have just set up retropie 3.1 and can report the cmdline.txt edit worked! I am a complete noob but managed to follow instructions. 1 problem though, my reroepie decree my left side of arcade controls as player 2 and right side as player 1 (reversed) anyway I can fix this. It’s probably something simple but like I said I’m a noob. Feederchain any ideas?

Viewing 13 posts - 1 through 13 (of 13 total)