Jump to content
LaunchBox Community Forums

coliver33

Members
  • Posts

    44
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

coliver33's Achievements

32-Bit GPU

32-Bit GPU (5/7)

1

Reputation

    @kloug666 This is exceptional work -- thank you so much for putting in the effort to keep this updated. I'm following this thread and getting notified of updates(!) some questions for you as I decompress all of this: - balonfgt: should it be the 5.9 or 6.6 version -- it looks like 6.6 might be a step backwards (6.6 loses the nameplate on the upper right) - dkongpe: 6 or 10 version for empirestate.png? 10 takes it from white to an off-pinkish - dkongx - same question -- should all of these empirestate.png's be white, like dkong's is? aside from these, I think I'm tracking on all of your various updates --
  1. @Warped Polygon I am trying to set up Launchbox playlists that will match your game designations on the controller mappings images you have created. (e.g. Hyper Neo Geo 64, as well as the more standard playlists like Midway Classics). Wondering if you have a spreadsheet of all the games you processed, which includes the designation you gave each game(?) (Is there any easier way of figuring this out without having to go image by image, seeing which bucket each game should go into.). Ex: znpwfv is called out in your controller mapping image as being Sega ST-V, but in your Arcade XML file there is no mention of ST-V (just Sega as publisher and Sega AM2 as developer -- but no mention of the hardware platform). Just trying to figure out how to mass-determine this linkage.
  2. So how do you handle the multiple command line differences (flop vs cass)
  3. Also - for the electron I assume you had to create separate LB platforms for floppy and cassette? How did you map things in BigBox for electron?
  4. @ci2own curious which software you use to annotate those bezels
  5. @ci2own So now I'm to the point where I have bunches of the swlist platforms working. Next step is to now try to automate things via autoboot commands. I wanted to see if you have any general guidance on how to pass those autoboot parameters from LB -- and if you happen to have any resources that show typical autoboot commands for the various platforms. Let me know and thank you!
  6. @ci2own Have you been able to get Boulder Dash to load? There are 4 ROMs in the softlist for it, but I haven't been able to follow the above instructions and have any of them load. Rest of the ROMs in the set all load up fine.
  7. @ci2own -rom1 did it for Pegasus. Frustrating part is, I checked the .xml for pegasus_cart and assumed -cart. How were you able to figure out that it was -rom1?
  8. @ci2own @sundogak -- One platform missing from the MAME SW List Instructions.txt file above is the Aamber Pegasus -- which loads just fine for me in the MAME RA core, but does not load from LB via: -f "pegasus -cart \"%romfile%\"" When I load within the core i'm presented with a BIOS selection menu, but can't see which -bios command line option to specify to pick one. Wanted to see if either of you have managed to get this platform to load from LB. Looks like this one is just a bit of an outlier...
  9. @sundogak Curious if you've been able to get any softlists working for the Atom other than the floppies. I have the floppies working, but it seems like for whatever reason the cassette list (atom_cass) games won't load -- even when I physically play the "tape" from within MAME and try to load them...
  10. @sundogak Well here's the good news -- I reverted back to %romfile%, removed that second space from the pathname, and it's working. So I guess for future ref, LB can handle things like spaces, (, ), etc. in the path -- but just can't handle 2 spaces.
  11. @sundogakWell................................. THAT DID IT. Thank you so much!! 🙏🙏🙏 I used romefilename -- worked perfectly. No other changes made.
×
×
  • Create New...