Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Cave Story.sh and Doom.sh files? #84138
    strelok
    Participant

    [quote=84012]those two should work fine in the new version of retropie.

    One question, i remember doing this with both doomlegacy and openttd, but cant remember how i wrote the files. and dont have them saved anywhere. but i do remeber that it involved the #!/bin/bash/ command

    also did the same to startx so i could have a nice way to get into the system and on the web etc from retropie.

    any ideas on this?
    [/quote]

    They did work fine, the issue only started when i broke the files by trying to change runcommand.sh and somehow they got wiped.

    They definitely started with that but I dunno what else. I tried copying my friend’s Doom.sh after he took a picture of it and sent it to me and i got a whole host of errors when I tried it.

    Is there any way at all I can recover these files? I don’t want to have to wipe my pi and start over.

    in reply to: Cave Story.sh and Doom.sh files? #83573
    strelok
    Participant

    So I discovered that Duke Nukem 3D still works fine, and I got the code from that:

    #!/bin/bash
    /opt/retropie/supplementary/runcommand/runcommand.sh 4 “eduke32 -g %ROM% -gamegrp duke3d.grp”

    I just don’t know how I change this so that it works with Doom and Cave Story, if anyone knew what I could do for this or help in any way I would greatly appreciate it.

    in reply to: Resolution problems with some emulators #82444
    strelok
    Participant

    Anyone have any ideas? Is there a separate file I should change to get those two to work? The others all work fine, but Doom and Cave Story don’t open.

    in reply to: Resolution problems with some emulators #82315
    strelok
    Participant

    Duke 3D now works fine but Cave Story and Doom just present the command line for ~10 seconds as if they’re trying to boot and then return me to the ROM selection screen. Huh.

    in reply to: Resolution problems with some emulators #82297
    strelok
    Participant

    Sorry for the long response time but this was actually perfect – the SNES emulator, which worked perfectly used runcommand.sh 4, while the Game Boy and Game Boy Color emulators used 1. I changed them to match the SNES and everything was perfect!

    The only issue is that when I go into es_systems.cfg, under the Ports header I don’t see the runcommand.sh line. Here’s a screenshot of what it looks like when I do this.

    Is there somewhere else that it’s stored for certain emulators?

    in reply to: Resolution problems with some emulators #82065
    strelok
    Participant

    Huh. That had exactly the opposite effect – now everything appears that small.

    Emulationstation and everything else worked fine so maybe it just has to do with the specific affected cores?

    It may be worth mentioning that everything still looked fine on the other TV.

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