JoeViking245

odyssey2.zip is the main rom file for the Odyssey 2 Console machine. It does not store the game (or at least it's not supposed to). When you click Odyssey 2 in MAME, it pulls the list of all the odyssey 2 games from the file located in ../Mame/hash/odyssey2.xml. I assume you have "odyssey2.zip" located in your ../Mame/roms folder. Where do you have "3rcsocpt.zip" located on your computer? That's the file you need to be pointing to in the Edit Game.Also, where ever that file is located, you need to make sure that path is listed in your mame.ini file under rompath.

This needs to be pointing to the game rom file (i.e. deathrac.zip) to start a game. Or in your example "Speedway + Spin-out + Crypto-logic (USA, Europe).zip" Thing is though, that's not a normal MAME naming convention. But you said it loaded directly though MAME, it should load through LB.

You'll want to first import the individual games (roms) into LaunchBox. Then in Manage Emulators -- MAME -- under Associated Platforms, for the Odyssey 2 Platform, set the Default Command-Line Parameters to odyssey2 -cart The easiest way I've found to import the MAME software lists (i.e. Odyssey 2) and their games is using the Software List Import plugin. It should also setup the MAME emulator automatically with the command-line above. https://forums.launchbox-app.com/files/file/2080-mame-software-lists-import-tool-plugin/

Glad it's working for you now. I had actually removed a couple /n's when posting. Guess I should have left them in there. ?

Because you need to enter the disk name after the "load" command, I think your only options are: Create and ini file for MAME for each individual game and edit the autoboot_command line. Easier (though not necessarily easy).... create a custom command line for each game in LaunchBox I don't have "avenger" in my arsenal, so I used "hiresinv.zip" instead. Here's the custom command line I was able to make work. abc80 -skip_gameinfo -autoboot_delay "3" -autoboot_command "loadhiresinv\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nrun\n" -flop1 Notes: The rom file name inserted after "load" does not need to be in quotes (nor a space after "load"). The \n simulates the Enter key. A whole bunch of them in a row sort of acts as a 'pause' before sending run and Enter. Needed to bump the autoboot_delay to "3", otherwise the "l" in "load" didn't get sent. (at least on my machine) To enter this in, go to Edit Game, click the Emulation tab, check "Use Custom Command-Line Parameters" and enter in the line above (changing "hiresinv" to whatever rom you're loading).

abc80 is not specifically on the list, but you can get an idea of how to set up your command line here...

Not sure if PD has a merged set of the softlists. Here's 0.220 split setBut with the torrent, you can un-check all the others (if you'd like) and just download abc80_xxx real quick-like.

@monkneys This plugin as written is for everyone. Not just Premium users. When you click Tools and then hover the mouse over "Import MAME Software Lists", does its' background color change to blue (just like it does with all the other menu items)? What version of LaunchBox are you using? Did you download the latest version (2.0) of the plugin? (this may be a stretch, but...) When you click "Import MAME Software Lists v2.0", the plugin window may have opened up in the background or possibly on a 2nd monitor. Hover the mouse over the LaunchBox icon in the taskbar. Does it show 2 instances of LaunchBox, 1 being the Import tool?

The custom command line is going to have whatever you need entered between the emulator executable_name and the rom_file_name. -L "cores\mame_libretro.dll" electron -exp romboxp -rp "L:\LaunchBox\Games\Acorn Electron" -cart1 LB will put in retroarch in front of the above line and the rom name at the end when launched. The rom name will go in based on the check boxes you have in the emulator settings. i.e. "Don't use quotes..." and "Use file name only....". Also, you shouldn't need to make literal (\) the quotes like you have for the rom_Path (-rp) above. That worked perfect for egghead. TY! A note on rom paths for SoftLists: (at least for stand alone MAME) For the anal retentive, OCD type folk out there, this may put them out of their comfort zone.... But..... if you put your softlist roms in folders the same name as their hash file xml names... all under one directory, you only need to add that one directory to the rompath in mame.ini. So for example, I created a directory under mame called "software". D:\mame\software\ So in my mame.ini, I have rompath roms;software No more. No less. Then under "software", it looks likeYou can probably put any corresponding bios/device files in the respective softlist folder, but as some of them share these files (like the apple2 variants) I put them inside the "software" folder itself. In this manner, you won't need to add -rp (unless RetroArch want to to 'different') to the command line. Also, in the LB emulator settings, you can check both "Don't use quotes..." and "Use file name only...." boxes without issue. Credit goes to @sundogak for this tidbit (at least this is where I learned about it ).

@SiriusVI Try changing the file extension to .lua so that it knows it's a Lua script. apple2_cass_autoboot.lua Not sure if that'd work, but 1 sure way of finding out.

Glad it worked!!! "Game on!" as they say.

Windows/PC games are kind of their own animal so are not really handled like emulators. As in, they don't emulate, the just play. So with that, they innately handle their own Pause and Exit. Using an AHK script to exit a Windows game is pretty much never a good idea. Use the games menu's to 'Exit To Windows'. You can disable the LaunchBox Pause feature for those games so as to not conflict with the game itself. The screen setup is also handled by the individual games themselves. I would think that when you launch one of these games and if the screen/window is all wonky, that if you move/size it to where it's suppose to be (where you want it to be) and then exit the game (though its' menus ), it should remember that setup net time you start.

For Windows game like SOR4, go into the Input Settings then assign the "keyboard" bindings. Up/Down/Left/Right should already be assigned accordingly to the joystick (actually the other way around as the the Joy Up is (should be) assigned to the up arrow key.... etc.). Looking at https://www.pcgamingwiki.com/wiki/Streets_of_Rage_4#Input_settings, by default, Jump is assigned to "SpaceBar" which if 'so-far-so-good' should be your Button_3. However Attack is "D" which (probably) none of your cab buttons are assigned to. Arrow (or Joy) Down to Attack, press Enter, then press Button_1 (which should be assigned to "Ctrl" [maybe ] ) ... or which ever button you want. ...and so on. Any chance Coin is the "5" key and Start is the "1" key? Ultimarc shows that the default for "Enter" is Start + Joy_Left. (aka "1" + "Left_Arrow") which to me seems odd. But I suppose I'm just used to how my cab was setup. Regardless, I'm sure you have "Enter" configured in there somewhere. You'll be able to see exactly where using the WinIPAC utility program. Here's mine: I'm curious to see what you find.

Need to know what your encoder is. You can either find it in the specs that came with the cab you got, ask the person/company who built it, or follow the wires from the buttons to it. Though there's a chance that whoever built it already set those up. However you exit a MAME game will (should) = Escape.

Setup a modifier button. For my cab that uses the Mini-PAC encoder, Player_1_Start button is the modifier. So simultaneously pressing Player_1_Start and Player_1_Coin sends Enter. Pressing Player_1_Start and Pause buttons sends Escape.

No. Outside of Arcade (MAME), I think you're pretty much on your own. I know there's a Theme (or 2?) out there that have added generic controller [image] information for at least a Pause Theme (possibly Startup also?). I used CPWizard to create the layouts for all the Arcade games. And for the other systems made generic images [PhotoShop] that correspond to my cab. From there, I customized the respective Themes to show them. Startup: Pause: BigBox - Platform view:

I think you'd be best to just the one standard IPac config and then configure each emulator (system) from that. I'm not sure about Steam, but I'd think you'd be able to do that 'internally' as well (i.e. a per game config [as needed] from withing the games' config itself).

The best way is to use mame64.exe itself. At the DOS (err.... "Command") Prompt, type: mame64 -listmedia electron This will also be handy for all your future endeavors. The odd thing here though is that it didn't show carts. SYSTEM MEDIA NAME (brief) IMAGE FILE EXTENSIONS SUPPORTED ---------------- --------------------------- ------------------------------- electron cassette (cass) .wav .csw .uef floppydisk (flop) .ssd .bbc .img .dsd .adf .ads .adm .adl .d77 .d88 .1dd .dfi .hfe .imd .ipf .mfi .mfm .td0 .cqm .cqi .dsk An online resource (but older... rev. 1.74) is here https://pastebin.com/18W3EbD0 Which does show carts, but not floppies. It's also (in this case) not complete (up-to-date). But it is handy for a 'quick find'. electron cassette (cass) .wav .uef cartridge (cart) .bin And to really foul things up, its' cart shows .bin, and my current SWL electron_cart are all .rom (inside the zips). Another (previously mentioned) online resource that stays current is Arcade Database (http://adb.arcadeitalia.net/?mame=electron). Scroll to the bottom and expand Media Options (but again, no carts as it pulls straight from MAME). This site holds a lot of other good/necessary info/details. (i.e. scroll up a little and expand Show MAME Required Files.)

If you go to Tools, Options, Images and select Background Priorities, you can check which ones you want to see and then using Up and Down you can move the selected image type... well... Up or Down.

Not me. Haven't learned Lua (yet). But in looking just a little, I'm not sure if that will work. Mainly because of how this is worded { OPTION_AUTOBOOT_SCRIPT ";script", nullptr, OPTION_STRING, "lua script to execute after machine boot" } ..the caveat being "...after machine boot." Though I suppose you might be able to boot base-line, then have lua examine the rom file (your if/then) then have it send keystrokes to MAME accordingly (to switch bios and whatever else). But again, I don't know what all's possible between Lua and MAME. But by the time you figure out how to do all that, you may as well have just figured out which Electron floppies need which command and set custom command lines for them individually. AND..... when you DO get these all dialed in with whichever method, I can guarantee you will then only play one, three games max before setting it aside and [almost] never looking back. lol But yes!!... with a sense of accomplishment!

It sounds like it might just be rebuilding it cache. Start LB and let it set [run] for a bit (2 minutes? 5? 10+??). The ram (and processor) consumption should then level out, reduce and be idle. Provided you don't then add/remove a bunch of games/metadata/media, subsequent starts shouldn't be as demanding.

Electron carts (to round things out) electron -exp plus1 -cart1 seds -cart2

I personally have no 'ties' to any of the old computers. My 1st computer was an 80286 that I paid some dude in '87 to build for me. I went a little crazy and upgraded the ram to an insane 4MB and the HDD to 40MB. Even splurged on a Super VGA monitor and video card. Crazy kids anyhow. lol For the software lists, I figured I'd should at least learn it a little since creating the SWL importer plugin. The programming and figuring out 'new' stuff is my kind of fun. For figuring out stuff for MAME SWL's, I mostly use the hash files, MAMEDev Documentation, Arcade Database and Google. And of course tid bits found along the way here in the LB forums. Also out there is the mameGuide.info and MESS User's Manual. But even all that doesn't give a lot of specific computer/console info. So, short story long, Google. For computer roms, they're all from MAME. The console ones I have, I couldn't tell you what 'kind' they are or where they came from. They were mostly already on my cab when I got it about 6+ years ago. I added some [more] early on when starting out, but really had no idea what I was doing. I never bothered to look into TOSEC or no-intro because.. the ones I have all seem to work. So they're probably a pretty well mixed up breed. I look at my game count for some of the 'starter' consoles and they seem pretty thorough (nes-715, snes-269, n64-317, a2600-510 etc). I have no desire for hacks, prototypes or clones. And this count is well than more-than-enough for me.

Nice! Never knew about EXEC. It worked with enthar7, but for egghead I get I am using the MAME SWL dumps. Which just now checking, the xml says it's a 5.25 but in the History database it says it's a 3.5". eh... either way, it doesn't work (for me). No worries. Any other little ditties your holding out on us with? lol

mame64 electron -exp plus3,bios=4 -flop D:\MAME\software\electron_flop\enthar7.zip The "ADFS" are 3.5" floppies and the "DFS" are 5.25". Nice find on the "bios=4"! What rom did you get it to work with this? (enthar7 and egghead didn't work) I doubt you'll be able to get these into one electron.ini file unless you learn how to create an autoboot_script to load.