Jump to content
LaunchBox Community Forums

Headrush69

Members
  • Posts

    1,367
  • Joined

  • Last visited

Everything posted by Headrush69

  1. Opps, you are correct. I was looking at my macci driver and not my apple2gs. 🙁
  2. You also don't want the Don't use quotes option enabled. Are you using MAME for just Apple2GS or other systems as well? If more than one platform, you probably want those command line options in the associated platforms section, not as the default for the entire MAME emulator. Also, I don't think you need the -sl7 cffa2 option with Apple2GS, just AppleII.
  3. You have the option to use filename only enabled, so you are passing MAME just the filename so it doesn't know where the file is. You use that option if you are using software lists. (The tutorial above) MAME uses the filename only, to look in a hash file for the exact filenames it needs and it loads them from the software directory. There are pluses and minuses to both approaches, but settings are different. I prefer non software lists as I can use any disk or hard drive image I want or have created, not just ones in the hash file.
  4. If you can open a command prompt or a powershell window, type cd and then a space, than drag your Mame folder from Windows Explorer into this window. Hit Enter. Now you can manually run your command above adding the verbose option (-v) and you should see immediately why MAME is failing to run. So your command to type would be: replacing File of course.
  5. Files like those for the apple2e (bios and device files are what those are) can go in any folder, MAME just needs to know that folder. That is set in the mame.ini file manually or by using the MAME UI. By default, MAME looks in the roms folder in the MAME directory, so you can put them there. The actual disk images can be placed anywhere and LB will pass the path to MAME when launched. If you want to use software lists, you have to follow the tutorial posted earlier as it is more strict about disk images and where they are placed.
  6. MAME can use them in 7z format,
  7. If you're talking using MAME, these are the files required. These are the individual files, which are normally found in the following files: apple2e.zip, a2diskiing.zip, d2fdc.zip, votrax.zip that are in a MAME romset.
  8. MAME is very flexible, so don't have to use software lists. In the example I gave you, it's very simple, The parameter apple2e is telling MAME the machine to emulate, the -flop1 is telling MAME we are giving you a disk image to use in disk drive 1. That's it. Yes you will need BIOS files, but you'll likely need those with any apple2 emulator, not just MAME. If you don't have a mame.ini file, just run MAME without any options (double clicking in Windows Explorer will work), pick Configure Options and then Save Configuration. You will now have a mame.ini I'm sure there are lots of tutorials, but I don't have a link to one I know for sure is good and up to date. There isn't really much you need to configure in MAME in most cases to just get roms running. Setting the path to your roms and having a matching romset is the major thing. Within that MAME UI you can set a lot of the mame.ini options. Just remember to save the configuration after making changes. Edit: To change disks in MAME just hit tab to bring up the UI and go to File Manager. Should be fairly straight forward to navigate and pick the next disk you want to add to any disk drive.
  9. Yes. Something like Some will support 2 disk drives so: Other times you will have to use MAME's in game interface to change disks. Yes.
  10. Yes I remember our discussion. There were some joystick fixes since then in MAME but some issues remain in some games. (like gauntlet) Checking that post, seems the issue as reported by Torquemurder, isn't a bug in MAME per sa but MAME needs to implement analog trim adjustments to work around programming issues in some games. Not sure that's the kind of thing MAME would add, as the core emulation works as it should. He did mention that in GSPort/KEGS he added a patch to manually adjust trim values. No idea how AppleWin handles the issue or if it does. Edit: I read online someone using a LUA script to read and set values for a game control in MAME, I wonder if something like this could be done to "adjust" analog values in the apple2 driver to act like a trim adjustment. I haven't looked into LUA scripting in MAME myself, but maybe a possibility?
  11. MESS was merged with MAME a while back and since then it has continued to get many updates to the apple2 subsystem. It's support for various peripherals is quite extensive. I use it exclusively for my Apple2e and Apple2gs emulation. AppleWin is also an option. Try both and see which you prefer. Some people don't like MAME and find it difficult. I don't and it works great in LB for me. A good write up is here.
  12. I notice in your log file Xemu is running as 128Mb (not the normal 64MB) I'm not sure this is the answer to why it's running slow, but maybe try setting to the standard 64MB of a XBOX.
  13. Instead of just deleting the nvram file, once configured as you like in game make a copy of it. (swtrilgy.backup.nv) In your script, using whichever method you want, (BAT, AHK, etc), delete the old nvram and copy the backup version with the correct name, swtrilgy.nv This is the AHK script I used The 1 option at the ends, overwrites the files so I don't need to delete first. I compile this script to an exe and add as an additional app for swtrilgy and have it run before supermodel3 emu.
  14. I've always updated FS-UAE like that and never had any issues if that helps.
  15. Yes. Which UI mode are you using? Should be under Options in the Quick menu after you start a game.
  16. If you look in the Retroarch quick menu under options after starting a game you will see the option to enable service buttons. You will have to look under Controls in the Quick menu to see what yours are set at. (you can change them) One thing to note, when you get into service mode, the first screen is options for the base Sega Naomi cabinet options. (These machines could change cartridges and run different games) In that menu you should see an option called Game Test Mode, this will led you to the specific settings for the current game.
  17. In the flycast core options are you using the HLE BIOS? If you are using a real BIOS and that is disabled you should get the startup swirl and sounds.
  18. That was a very detailed and well explained post JoeViking245. I knew all that though. I missed the small post where ci2own mentioned he was using software lists, hence my confusion and why I suggested a work around. So yes you are using software lists. I use this method for Mattel Intellivision so I can use game specific artwork for the controller overlays.
  19. This is very interesting. Are you 100% sure MAME isn't loading in software list mode? Since you're loading with just the rom name, that would mean your pegasus roms are all in your default roms directory based on your screenshot. (which doesn't seem practical) Also, that would mean MAME would be using artwork in software list mode when passing a rom file directly, which would seem inconsistent. I'm not suggesting your wrong, just curious. Going to test myself some more.
  20. I have it both ways, included in all games and broken down by system. In LB, clicking just Arcade shows all games, but BB doesn't, so that's why I also have the All Games playlist. I do this as I know different arcade boards, but most people using my cabinet just know they are arcade titles and will look in there. Same here but I do NOT use the full set with LB or BB. Yes that is an option. It really depends how you want to organize your roms. For the most part, the only real reason I separate some systems like Sega Naomi, Sammy Atomiswave, is because most of them use an emulator other than MAME. It's easier to work on them. I have a text file that lists all the MAME roms I want. You can see from the screenshot posted earlier, I load that text file and select include BIOS and include devices and I create a non-merged MAME set of just the games I want that are self contained. Each MAME release, it's as simple as reloading that file in CLRMamePro and it will correct any any changes needed. (There are a few very times when this can break but simply looking at the set information and correcting and updating the text file fixes the issue) Below is a sample from my game text file. You'll might notice I have things like a USA version of Title Fight, and 2 player versions of the Teenage Mutant Ninja Turtle games, instead of the default 4 player. So when I update MAME, I always get these versions. I don't know if it's changed in the LB Full Mame Import tool, but previously it didn't remember if you had set different defaults for roms with multiple versions.
  21. Anyone else seeing this behaviour? Same emulator with different cores with empty custom command lines, and LB considers them duplicate entries?
  22. I use Retroarch flycast core for this game, but by chance could it be setting in the game service menu to change the cabinet type?
  23. Instead of naming the layout file name based on the rom, can you try it using default.lay instead? (just a test) OK I think I found the issue. The override feature does work, but only if it's another artwork that MAME knows, and hence why it worked for me and not you. MAME, doesn't know the rom tank, so that override will not work. I just testing using a random one, galaga, and it worked OK. There are a couple "workarounds" I can think of. Set up a directory folder with a folder for every pegasus rom you have. Inside each folder have a pegasus.zip artwork with the appropriate files for each game. For you command line options, use the -artpath option to set the correct folder to use. Exact technique will depend on whether you pass roms directly or use software lists. Other option that is probably easier, is just create a small AHK program that runs before MAME and copies the game specific artwork over the default pegasus artwork.
  24. You may want to download ClrMamePRo and using it you can go into the set information and see all the systems MAME supports. There are lots and many that don't work with MAME yet. Attached is a sample. Outside of Neo-Geo, a lot of the more popular other systems are usually better supported by other emulators. There are some scripts on the forums to grab the roms for those systems from your MAME set and place in a different folder. From here there are several options on how you want to important them. You can import has separate platforms. You can import them as Arcade platform but set to use a different emulator. Afterward you can use auto-populated playlist to create those systems for you. (Using Platform category view) Here is my set up, all arcade roms in Arcade platform, but playlists that are auto populated for specific systems.
  25. If you have access to these machines already, your best bet is to install and try a few of the more demanding emulators and try a rom or two and see how hard you can push it. The issue is there is not a simple answer as each emulator and system is and can be quite different. For MAME, single core CPU speed is most important. My 2 core i3 @ 3900Mhz played many games better than my 4 core i5-6600K @ 3500Mhz using the same video card. For games that upscale or offload to the GPU (like PS2), obviously a dedicated GPU will be dramatically better than an integrated GPU. Only you can decide what shaders you might use, how much you want to upscale and what is acceptable performance wise. Maybe as a baseline, you could tell us what 2 platforms are your most important to emulate. I don't have much experience using portables for emulation but others might be able to tell you what is realistic for those specs.
×
×
  • Create New...