Forum Replies Created

Viewing 35 posts - 141 through 175 (of 206 total)
  • Author
    Posts
  • in reply to: MAME samples #87232
    Roo
    Participant

    no, sorry but that’s incorrect

    leave the samples zipped (the names of the sample zips should match the names of the game rom zip files) and they go in /home/pi/RetroPie/roms/mame-samples

    you can get the correct samples here http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,5,2511

    artwork goes in /home/pi/RetroPie/roms/mame-artwork

    get it from http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,5,2512

    roms go in /home/pi/RetroPie/roms/mame

    source: MAME4ALL’s documentation

    https://code.google.com/p/mame4all-pi/

    in reply to: Hide text while loading games #87231
    Roo
    Participant
    in reply to: Retro TV for the NES #86759
    Roo
    Participant

    Well done sir!

    in reply to: Fresh install getting horiz lines #86755
    Roo
    Participant

    I don’t have an immediate answer for you, all I can do is help troubleshoot it down to where the problem is :)

    How are you getting video from the Pi? HDMI or composite? It looks too sharp to be composite, so I assume HDMI. Do you have any adapters or is it going straight to an HDMI display? Can you try a different display?

    in reply to: Fresh install getting horiz lines #86753
    Roo
    Participant

    how did you install RetroPie? I would recommend you try the SD card image v2.4.2 beta and see if it still happens

    in reply to: Fixing ROMs that have errors #86595
    Roo
    Participant

    [quote=86384]When it says existing ROMs, does that refer to the original ROMs or to the ROMs that were created in the Mame4All folder?[/quote]

    Your source roms.

    * Load the FBA dat into a new clrmamepro profile, or just load the profile you made earlier if you already did that step
    * Go to settings and verify you have the path set to where you want your new FBA roms to go. This should be a new, empty directory – you will rebuild into this directory. In my tutorial, I used C:\RetroPieRoms\PiFBA
    * Click on the rebuilder button of clrmamepro. The destination should be filled in with the path you defined in Settings (i.e. C:\RetroPieRoms\PiFBA). The source would be wherever you have your MAME / FBA roms. MAME and FBA use (basically) the same roms, so you can start rebuilding by pointing the source to your same MAME roms you used to rebuild the MAME set earlier in the tutorial
    * You can rebuild again, picking a different source each time. If you have multiple locations where clrmamepro may be able to find matching roms to rebuild your FBA rom set, just rebuild with each of those source paths

    Hope the helps explain. Let me know how it goes!

    in reply to: Doubts about save, on / off, tutorial #86594
    Roo
    Participant

    If you are used to using these same emulators on different platforms, then yes, they work the same. Every emulator has it’s own hot keys for save state and load state, you just have to google what the special keys are for that particular emulator.

    For a nice on/off switch, check out https://mausberry-circuits.myshopify.com/

    Floob has some great tutorial videos you may want to check out:

    in reply to: Raspberry-pi 2 compatibility #86584
    Roo
    Participant

    How is Mortal Kombat in MAME4ALL? On a B+ it is playable but the sound glitches out.

    in reply to: Raspberry-pi 2 compatibility #86538
    Roo
    Participant

    [quote=86513]The new pi looks nice, but a little bit of a shame that the cpu is only clocked at 900mhz by default, and that the ethernet is still 100mbit. But still a big improvement – will be interesting to see how much overclocking can be done.
    I’m somewhat tempted to get an odroid-c1, which has 4×1.5ghz and gigabit ethernet. Sells at $35 but seems to translate to close to £35 once it gets to the uk which is a shame.
    [/quote]

    I’m not trying to start a fight:) But to each there own. I love the RetroPie project, but I love the Pi Foundation’s goals even more. I think the charitable, education-centric basis of the Pi is why there’s so much support. Otherwise, we have been able to buy more powerful, not much bigger MicroATX boards from any number of corporations for years.

    I can see why they went with the specs they did and frankly, I think it’s amazing they are still hitting the same $35 price point. What I think is a shame is the obvious influence (interference?) from Microsoft who seem to think that they need to get in on this. There’s some kind of Marketing agreement in place (obviously) but I don’t know if it’s more than that – MS pushing money into the foundation maybe? I hope it doesn’t pervert this project into something more commercial.

    And no, I don’t have any tin foil hats nor do I have a MS bashing agenda. My main desktop PC is Windows 8.1 and I love it. My main portable is a MacBook Air and I love that.

    The Pi is different and I’d like it to stay that way.

    in reply to: Raspberry-pi 2 compatibility #86537
    Roo
    Participant

    [quote=86488]Cortex-A7 is a 32bit core. Libretrocores can almost profit from more cores because audio and video run in own threads. There could be a slight performance boost if everything is compiled with -fpu=neon and -mcpu=cortex-a7.[/quote]

    What are your thoughts on RetroArch shaders? Will multicore environment help there?

    in reply to: Managing ROMs with clrmamepro #86290
    Roo
    Participant

    [quote=86214]Hi Roo,
    Thanks very much for your help. I think I’m slowly getting to grips with scanning and rebuilding now. clrmamepro certainly has a lot of options![/quote]

    It does! But it’s not CMP’s fault. All these different emulators do things a little differently from each other and CMP just gives you options to deal with that :)

    [quote=86214]So is it the case, that the dat file will contain the precise information about the relevant roms (filesize, anme and crc check) and sets, so when you build it will rip out any matching roms from your sources and recreate/rebuild valid ones itself, so a lot of the hard work / important data is held in the dat file?[/quote]

    Yes, that is exactly how a dat file works. I wouldn’t say “rip out”. With default CMP settings, your source files are not destroyed in the process of rebuilding. Here’s an example section of a MAME dat file, it’s pretty easy to see how it works:

    ‘ <game name=”dkong”>
    <description>Donkey Kong (US set 1)</description>
    <year>1981</year>
    <manufacturer>Nintendo of America</manufacturer>
    <rom name=”c_5at_g.bin” size=”4096″ crc=”b9005ac0″ sha1=”3fe3599f6fa7c496f782053ddf7bacb453d197c4″/>
    <rom name=”c_5bt_g.bin” size=”4096″ crc=”1c97d324″ sha1=”c7966261f3a1d3296927e0b6ee1c58039fc53c1f”/>
    <rom name=”c_5ct_g.bin” size=”4096″ crc=”5ec461ec” sha1=”acb11a8fbdbb3ab46068385fe465f681e3c824bd”/>
    <rom name=”c_5et_g.bin” size=”4096″ crc=”ba70b88b” sha1=”d76ebecfea1af098d843ee7e578e480cd658ac1a”/>
    <rom name=”c-2j.bpr” size=”256″ crc=”d6412358″ sha1=”f9c872da2fe8e800574ae3bf483fb3ccacc92eb3″/>
    <rom name=”c-2k.bpr” size=”256″ crc=”e273ede5″ sha1=”b50ec9e1837c00c20fb2a4369ec7dd0358321127″/>
    <rom name=”l_4m_b.bin” size=”2048″ crc=”59f8054d” sha1=”793dba9bf5a5fe76328acdfb90815c243d2a65f1″/>
    <rom name=”l_4n_b.bin” size=”2048″ crc=”672e4714″ sha1=”92e5d379f4838ac1fa44d448ce7d142dae42102f”/>
    <rom name=”l_4r_b.bin” size=”2048″ crc=”feaa59ee” sha1=”ecf95db5a20098804fc8bd59232c66e2e0ed3db4″/>
    <rom name=”l_4s_b.bin” size=”2048″ crc=”20f2ef7e” sha1=”3bc482a38bf579033f50082748ee95205b0f673d”/>
    <rom name=”s_3i_b.bin” size=”2048″ crc=”45a4ed06″ sha1=”144d24464c1f9f01894eb12f846952290e6e32ef”/>
    <rom name=”s_3j_b.bin” size=”2048″ crc=”4743fe92″ sha1=”6c82b57637c0212a580591397e6a5a1718f19fd2″/>
    <rom name=”v_3pt.bin” size=”2048″ crc=”15e9c5e9″ sha1=”976eb1e18c74018193a35aa86cff482ebfc5cc4e”/>
    <rom name=”v_5h_b.bin” size=”2048″ crc=”12c8c95d” sha1=”a57ff5a231c45252a63b354137c920a1379b70a3″/>
    <rom name=”v-5e.bpr” size=”256″ crc=”b869b8f5″ sha1=”c2bdccbf2654b64ea55cd589fd21323a9178a660″/>
    </game>’

    Just a small note, when you create a dat file from a MAME executable, CMP doesn’t actually make a dat file you can go look at, it just caches the same data.

    [quote=86214]So potentially you could build a full romset against a given version even if you never had any of those roms to begin with?[/quote]

    You have to have the roms somewhere, CMP can’t create the roms from nothing. But yes, if you have a full set of MAME v0.157 and you rebuild into MAME v0.138, you’re going to be pretty close to a full rom set. Over at pleasuredome, two popular MAME sets are the current version and the “rollback roms”. With these two, you should be able to rebuild any previous MAME version’s roms. That’s what I keep on my hard drive.

    [quote=86214]And with RetroPie, the FBA dat file is 0.2.96.71, and this appears to have 684 games, so that would be the maximum amount of verified games that will run on it? And that also implies that the fba binary would be most happy with this set as thats the dat file that came packaged with it?[/quote]

    Yes and yes. Whoever made that dat named it “working roms”, I have no reason to doubt their accuracy :)

    [quote=86214]Should I worry my neogeo.zip never seems to find the correct sized 000-lo.lo rom in it?[/quote]

    You can try a scan with the “fix size” checkbox selected. Again, CMP can’t create data from nothing. But if your current rom is too big (but the real data is in there somewhere) CMP can fix that. Or if your current rom is too small, and CMP just needs to pad it out with zeros, it can do that too.

    in reply to: Managing ROMs with clrmamepro #86077
    Roo
    Participant

    [quote=86072]Hi Roo,

    I think I’ve got a MAME 0.138 set, what is the best way to confirm this?
    Would it be (if I download the windows exe of mame 0.138):
    mame -verifyroms * >verify.txt

    Or is there an easier way?
    [/quote]

    Yes – you need the Windows MAME v0.138 executable, which you can get from http://mamedev.org/oldrel.html

    Extract it on the same computer where you have clrmamepro installed.

    * Launch clrmamepro
    * Click Profiler
    * Click Create…
    * Filename points to MAME v0.138 executable – i.e. MAME.EXE
    * Description would be something like “MAME v0.138”
    * Emulator is MAME
    * Click Create Profile

    Load the profile and Clrmamepro will build a DAT file from the MAME executable (by running MAME.EXE -listxml). When clrmamepro asks you questions, answer No to “use software lists” and answer “Yes to All” or “OK to All” to everything else.

    You can now use this profile to scan your ROM folder, just define a ROM path in Settings. If you have problems here, you can follow the wiki page instructions. It’s all the same process, you just got the DAT file from a different source.

    Yes, you can also use the MAME -verifyroms switch, but I think that’s a pain. You’d have to pipe that out and try to parse through the results manually.

    in reply to: Managing ROMs with clrmamepro #86075
    Roo
    Participant

    [quote=86052]So i’ve followed these fine instructions by the letter with varth.zip, it didn’t work out as expected, the game still isn’t running.

    I noticed clrmamepro even removed some files, the zip ended up even smaller than before.
    [/quote]

    MAME ROMs change over time. Maybe better dumps are made, or maybe they decide a ROM really isn’t a ROM, and is a logic chip instead. For whatever reason, MAME v0.37b5 varth.zip may be nothing like MAME v0.157 varth.zip.

    Clrmamepro found all the ROMs in your source path that matched the v0.37b5 dat file and rebuilt the best version of varth.zip it could find. Which doesn’t mean it is complete. That’s where the Scanner function of clrmamepro comes in. You can also use MAME to verify a ROM, which may be easier if you are just trying to validate one ROM. The command would be like this:

    
    cd /opt/retropie/emulators/mame4all
    ./mame -verifyroms varth
    

    But you would have to copy the ROM you want to verify to /opt/retropie/emulators/mame4all/roms to use this command. It seems MAME4ALL is hard coded to look in the roms subfolder – it doesn’t use the path in mame.cfg file when using the -verifyroms switch.

    [quote=86052]
    Do i required multiple, different sets of the same game, so clrmamepro can rebuild them into one working romset?

    Or is it something else i haven’t thought of?
    [/quote]

    Yes, you may have to rebuild from multiple locations to get a complete working ROM. For example, I have two locations I rebuilt my 0.37b5 ROM set from: MAME v0.157 and MAME rollback ROMS.

    in reply to: IPAC2 Issues in Emulation Station #85962
    Roo
    Participant

    I can’t say specifically about the iPac 2, but my iPac Mini is working perfectly to control ES, MAME, NES, SNES, GBA and Sega Genesis in RetroPie 2.4.2 SD card image. They all run the same keyboard encoder, no?

    What problem are you having exactly? Can you hold down one of your pushbuttons to start the ES config? Have you tried unplugging all other keyboards and USB devices to test?

    Maybe a firmware upgrade? http://www.ultimarc.com/fwupgrade.html

    in reply to: Anyone have a working n64 / Mame fix? #85841
    Roo
    Participant

    :)

    Curious – why do you want to introduce frame skipping? Wouldn’t that make the games play worse?

    in reply to: Does mame4all let you exit the emulator? #85802
    Roo
    Participant

    I’m not in front of my Pi, but I believe you change that in the mame.cfg file – check there.

    in reply to: Help Please with new install #85801
    Roo
    Participant

    Try a different power supply, try a different SD card. If there’s no change it might be your Pi – try booting it with plain Raspbian.

    in reply to: RetropieImage problem #85800
    Roo
    Participant

    Try right clicking and running Win32 Disk Imager as Administrator.

    Roo
    Participant

    Well done, sir. Got it up and running, easy to follow instructions. Thanks!

    in reply to: Is MAME just dodgy or is it my setup? #85764
    Roo
    Participant

    As far as DKongJr goes, it sounds (no pun intended) like you’re missing the sample set.

    http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,5,2511

    place them in

    /home/pi/RetroPie/roms/mame-samples

    in reply to: MAME4all setup #85763
    Roo
    Participant

    I’m not sure how to reconfigure an older installation of RetroPie… I’ve seen some older threads about switching to MAME4ALL on earlier versions. Maybe check those out.

    But I would encourage you to upgrade to v2.4.2 Beta. MAME4ALL is the default in the newer SD card image versions.

    in reply to: How do I run DOS roms natively in RetroPie? #85761
    Roo
    Participant

    You can’t run them natively. You run them through DOSBox.

    Launch DOSBox and mount your dos folder. For example

    mount c /home/pi/RetroPie/roms/dos

    You can also add the mount command to the DOSBox config file located at /home/pi/.dosbox/dosbox-SVN.conf. You add the command to the end of the file, in the [autoexec] section. If there’s just one game you want to play, you can have the autoexec launch that game. Otherwise, you’re gonna have to whip out a keyboard. It is DOS after all :)

    Here’s some more info:
    http://www.codingepiphany.com/2013/03/30/raspberry-pi-retro-gaming-mania-part-2-dosbox/

    in reply to: How to map a arcade style joystick to retro-pi #85759
    Roo
    Participant

    You connect the positive pin and the common ground to the (normally open) switch. When it is closed, the Pi will see that the circuit was shorted and register the input.

    Does that answer your question?

    in reply to: Anyone have a working n64 / Mame fix? #85758
    Roo
    Participant

    Oh Donkey Kong works, I just had my best game ever last night playing DK on my Pi. No, I didn’t break 100k :( but I’m getting close!

    It just uses some older ROMs in the zip that the newer MAME’s DK zip doesn’t have.

    in reply to: Anyone have a working n64 / Mame fix? #85754
    Roo
    Participant

    I would love to be corrected here, but I’m pretty sure no one gets N64 running at full speed on the Pi. It’s just not quite powerful enough.

    For MAME roms, you don’t have the version that [b]this[/b] MAME needs. Google MAME v0.37b5 ROMs.

    in reply to: cleaning rom set of clones #85746
    Roo
    Participant

    It would have to right? But if it’d make a noticeable difference or not is another story :) Give it a shot!

    Roo
    Participant

    I would look at power issues first. Which Pi do you have? What are you using for a power supply? How many amps?

    in reply to: Retroarch.cfg Working Settings #85650
    Roo
    Participant

    I’m not sure I understand. My RetroPie v2.4.2 install works out of the box for NES, SNES and GBA (haven’t tested the others, I assume they work too).

    Are we referring to the same thing? I believe you are talking about in-game saves. If I load Legend of Zelda, it has my saved game from last time I played, same as the original hardware would have done. These are stored as *.srm files, I believe in the same folder as the ROM by default.

    Or are you referring to RetroArch F2/F4 saves? If so, this might be of help:

    How to save games in RetroPie / RetroArch

    in reply to: cleaning rom set of clones #85648
    Roo
    Participant

    Whatever works for you is cool, but just FYI, from the wiki I linked to:

    The switch --gamelist-only can be used to skip automatic searching, and only display games defined in the system's gamelist.xml

    in reply to: Everything was good…and now… #85632
    Roo
    Participant

    Those files are incomplete. If you’re going to log it from the Pi, try cat /opt/retropie/configs/all/retroarch.cfg instead of nano

    in reply to: PiSNES Shaders? #85621
    Roo
    Participant

    Only RetroArch cores have shaders. That’d be PocketSNES

    in reply to: GB and GBC Emulators are not working. #85619
    Roo
    Participant

    Yeah what Floob says. It sounds like you compiled RetroPie yourself. If you use the SD card image it’s much more noobie friendly. Also, since it’s an image of the whole OS, there’s lot’s of little tweaks included that you don’t get when you install RetroPie on top of Rasbian. Like a modest overclock that really is needed to run the included emulators.

    Bonus – it won’t take nearly as long as building RetroPie from sources :)

    in reply to: GBA emulator (GPSP) separate from RetroArch? #85617
    Roo
    Participant

    You should do a video showing how it looks to enable scanlines on the Pi at different resolutions using the XRGB-Mini :)

    [quote=85612]Thinking about it, how does the sound get carried through the HDMI to VGA cable?[/quote]

    HDMI carries video and audio. If you look at the adapter I bought, it has an audio jack. So it’s really an “HDMI to VGA/audio adapter”.

    If you use this adapter, make sure you feed it separate power (via the micro USB port on the adapter). From what I understand you can damage the Pi trying to pull the 5VDC from the Pi’s HDMI port.

    in reply to: GBA emulator (GPSP) separate from RetroArch? #85604
    Roo
    Participant

    That

    [quote=85602]Would they work like:
    Pi – HDMI to VGA – Scanline Gen – VGA to HDMI – HD TV
    [/quote]

    That might work but it does seem kind of crazy huh?

    [quote=85602]
    I do have an XRGB mini but cant really bung that in with each Pi setup I do.
    [/quote]

    From my quick research, this XRGB-Mini is the way to go if your source and display are HDMI and you want to add scanlines. I don’t have one myself, so you tell me :) Have you tried it? Does it work well?

    in reply to: cleaning rom set of clones #85600
    Roo
    Participant

    [quote=85595]Doesn’t MAME need some clones to function properly? It seems like it’d work better if you tell MAME one folder for toms and ES a different one then put a text file for each non clone game in the es rom folder and tell es that roms are *.TXT. Then it maintains dependencies (like needing Puck-Man for Pac-Man) but only shows one (Pac-Man but not Puck-Man.)[/quote]

    No – clones require parents not the other way around. You can delete all clones and everything will still play. Of course you’ll be playing puckman not pacman – not all parents are the US version. Puckman is the parent in this case.

    Don’t forget that some ROMs require BIOS files.

    I think a better solution than trying to “trick” ES would be to edit the gamelist.xml file.

    https://github.com/Aloshi/EmulationStation/blob/master/GAMELISTS.md

Viewing 35 posts - 141 through 175 (of 206 total)