sundogak

AppleWin is great, particularly if using multiple disks games or trying to do more complicated "computer" type things in an Apple. Swapping and loading disks (side A or side B, Disk 2, Player disks) in AppleWin is just much easier to do. It is also speedier to launch, unless you map the MAME speed throttle. MAME has advantage in that likely most people have it already and for single disk games it works fine. Also brings the support of normal MAME without a bunch of other setup needed (i.e,. shaders, overlays). It isn't you cannot use Mame for multi disks, but the interface to do so is a pain, particularly if going for a "use a controller for everything" model. For MAME: See my settings below. Add the gameio switch as noted below if want joystick compatibility directly in the emulator. I also added phasor sound card (mostly for Ultima) but that is optional since Mockingbird is "built in" with no need for switches. The -flop1 switch tells MAME and LB what drive to load the sofware. This is the setting within LB for MAME and screen snap for associated platforms for MAME emulator. apple2ee -sl4 phasor -gameio joy -flop1 For AppleWin This is my emulator settings in LB: Ultimately for both you will run into issue that there is not a lot of standardization on controls and you will either have to allow for a keyboard or map some keyboard functions to your joystick. For example, many games will ask "Keyboard (K) or Joystick (J)" so you will need to give that input. If fine with using combo keyboard and joystick (i.e., sitting in front of screen) then can get either up and going quickly. MAME you can map controller commands to keyboard, but for AppleWin it is not as all encompassing without using something like Joy2Key.

Echo above and will add some comments based on experience I had dealing with this with a relatives "mess". They had good intentions (sick family member, surprise, believed the "all setup" advert, not a lot of time) but similar to your situation, it was far from plug in and fire up. A couple observations: Most of these folks are using older images and/or Frankenstein setups merged from a bunch of different drives. In most cases I would wonder if they even bothered to fire up the emulators at all because like you found, most were broken. In many cases, simple issues were the problem, but only if you dug down in to the guts and knew enough where to check (i.e., path problem, out of date rom, corrupt files since they are duping dupes of dupes). Basically, takes longer to trouble shoot that nuke and start over. Most sell on "maximum number of games" so they throw a ton of stuff on there and it is overwhelming for the types of users buying these drives. I would argue most people just want the top 20 or so consoles and some MAME "top 200" type deals and that is it. Launchbox was "new" to many of these type systems where they had been using HyperSpin in most cases. So again, they just bolted on LB (non-license free version) and cobbled it together but the links to game files and media were all whacked out because they had used mixture of Hyperspin setup and hadn't bothered to import into LB (or at least copy a working setup that had done it). LaunchBox (LB) was basically non-usable since it wasn't ever setup correctly. A bunch of other things I can go on and on. So how to "Fix" it? Well, sadly not so easy. But I have the following suggestions with the main one being don't try to mess with the original drive and figure out what is "wrong": Get a new blank drive (similar size to what you got) and install these three items: Install LB (recommend buy license, worth the money in end but free is fine to start off). Install Retroarch (RA is free) intimidating at first if you are not used to it but the advantage is that MOST consoles will work with it and once you get used to working with it new consoles/emulators are the same basic steps (with some exceptions of course). Download "core" (emulator for RA), copy over ROMs to "new" drive, point LB to ROM directory and import/scrape. LB also has made working with RA relatively easy. Install MAME (free) It can be even MORE intimidating simply because it is an insane amount of systems that MAME emulates so it has tens of thousands of files. In some cases, you likely do have ROMs that are "okay" but just the emulator setups are all messed up. So you can use the purchased drive as rom source and/or media source for things like videos if you have slow internet connection. Otherwise, usually easier to have LB just scrape everything again automatically. Go in stepped approach, don't copy all the stuff on the purchase drive over or will make confusing. Pick a system, set it up in LB. Copy ROMs over. Import. Start with Atari 2600 (even if don't want it long term) because it is easy to setup and the ROMs are small in size so easy to move whole directory from Drive A to B and import into LB. It is also relatively easy to get working in Retroarch. If start off with the complex systems, will get discouraged. Stick with the older consoles and move forward in age, particularly Nintendo NES, Super Nintendo, and Sega Genesis. If you are my age group, those get the biggest "nostalgia" factor anyway and are mature emulation systems with lots of information on how to get setup. Lastly, with consoles like SNES, NES the file formats have been around awhile and even your drive, they are likely not messed up (probably a bunch of zips). Most things you can use Retroarch and MAME for relatively quick and easy setup. Tackle MAME once you are comfortable with RA and LB. MAME: MAME is relatively easy if have LB and just do things the way MAME wants you to (i.e., don't mess with the rom files!). If you know what "mame set" you have that will be helpful (i.e., 218, 219, etc). If you are lucky and have a relatively recent ROM set (in the 200s) on the drive, you can simply copy the whole "ROM" directory into the new drive. Point LB to MAME emulator. Import games into LB. LB allows you to prune on import things you don't want such as "no casino games" and the like so even if you have the 5,000 ROM set LB can simplify and doesn't import them (but you can if want later). LB does the heavy lift of knowing how to do that and don't have to worry about MAME complexity (or at least less so). Main thing with MAME, don't try to cheat the set up to find "pac-man" and just copy that over or you will get frustrated in that it will likely not work. You can pretty much get the "golden" age arcade items running pretty quickly without a lot of understanding of how MAME works. Although RA allows you to run MAME inside it (via a core), I think it is easier initially to get running outside RA for MAME. My preference anyway. After that, moving towards more modern consoles such as PS1 to setup. These can be big files, plus depending on who set the drive up, you could have mishmash of file formats which may or may not work. For these bigger files, I recommend sticking with setting up a few ones you have interest in and get them working first. Basically, anything that had a CD as a game, you can run into more complexity to figure out why not working. Recommend don't tackle PC/Computer (Apple II, Commodore 64) emulation until you feel comfortable with the consoles and arcade setup above even if they threw that all in. Again, they tend to throw a ton of stuff in to make it look cool. Rinse, repeat. I found the first 6 or so consoles all went pretty quick (again up until you hit CD images). Your i3 may start to struggle on more complex systems anyway. With all that, in the end, likely the purchased drive will be placed in a drawer and you won't use it again after you do step wise copying of the ROMs over since you will have replaced with newer/better data. Like Lordmonkus said above, "they lied", and buyer beware. On positive side, the folks here at this site are very helpful, so as you dive in, ask questions and you will get pointed in right direction.

You cannot use Retroarch with the pinball setups. The graphic I had in my message is something I snapped out of my Pause screen setups. The logo is a "NO RA" logo meaning it isn't emulator using RA. Just my cryptic notes to self. The other one that Itchyrobot attached was just an RA mapping for the controller numbers that RA uses. VPX maps the same only it starts at 1 versus zero. He was just using that as a reference point, so can ignore the RA logos/references. Screen snap your controller setup so we can see what is going on. Is your controller working with other emulators? Working with LB? Showing up in windows (I assume)? Also to eliminate possible table issue, open up table that is automatically installed by VPX called Nudge Test and Calibration.vpx (in tables folder). That will allow you to see if your controller is working without the issue of buggy table.

@HutOnChickenLegsI understand the CD and 32X modules, but they already had standalone "platform" rings so that was where had lack of clarity. Anyway, this may be more applicable to your situation.

@GamerMTL As point of reference, my XBOX ONE controller is the non-Bluetooth wireless with a USB dongle. My older 360 controller (also with a USB dongle) worked as well. In theory, the bluetooth version should work, but pinball software each have their oddities to deal with. If doesn't work, then the Joy2Key, Xpadder, or X360ce route are the next options to try as ItchyRobot has done with Joy2Key. I have also seen options to use Steam as the controller overlay for VPX, but I haven't tried it. The controller programs do offer lots of flexibility but they do add another external program layer to manage within LB.

@HutOnChickenLegs Made an assumption.

@HutOnChickenLegsAre you talking like a light gun or some other add-on/peripheral? I also assume you are talking this style:

Yeah, I had messed with Joy2Key at one point to try and make FP and VP map things consistently. I had used to map the triggers (which I have error in figure above, since notes triggers are flippers). I would probably go to a complete Joy2Key setup if you could do additional Apps per emulator rather than game. I know you can edit XMLs, but right now don't have to patience to fiddle with it and keep hoping it will get added as a feature. I had grand ambitions for an arcade cab and a dedicated PB Cab, but life keeps getting in the way of either time/$ to do it and/or space to put it.

@GamerMTL What do you have mapped in Preferences, Configure Key's option box in Visual Pinball? Here is an Xbox One setup I have on one of the desktop machines: Above settings are mapped as shown below on controller (note the triggers are not mappable without a program like Joy2key or Xpadder): Note: @ItchyRobotThe VP controller buttons start at 1 (A Button) and not Zero like Retroarch so the above diagram is off by one for each button.

@Gamer Two were already in the pack made by Viking which is attached in the zip files at beginning of the thread. Here are the other two:

@Bunglezbawb Here are rest. That Global VR logo isn't the greatest quality, but it will have to do until someone has time to retrace it. For Silver Lindbergh, that was never released best I can tell, so no official logo. Redid the yellow one to match others.

Mame site has a lot of information https://docs.mamedev.org/index.html For most part, they will refer to the overlay feature as “artwork” , so use that in search.. Mr Do`s site has information on artwork as well as art lay files https://mrdo.mameworld.info/mame_artwork_faq.php Other information can be found in searching here as well (example Lordmonkus has good thread on HLSL shader settings).

I don't have good logos for these so unless you can provide and/or find logo PNGs for them cannot do much for these 5: Sega Lindbergh Red Sega Lindbergh Silver Sega Lindbergh Red EX Sega ALL.Net MULTI Ver.2 Global VR Rest are below. These were done by others in this thread, although not directly what you want but may be alternatives and/or placeholders for the other Lindbergh's or ES3s.

@GiSWiG Docs for two of MAME cores (2003 and 2010) are buried here: https://docs.libretro.com/ Go to "For Users" and then "Arcade Emulation" and it will have drop down links to the 2003 and 2010 cores. I have yet to find a similar guide on the most current core. I have messed with it and got RA MAME working (relatively easy if just arcade games), but still use standalone MAME as primary, particularly for former MESS related systems and when using overlays.

Image pack media here in first thread. Second thread links to the video snaps for all current tables in FX3. Edit: just noticed you said portrait, so assuming you mean full table overhead view. The videos noted below were landscape view/desktop so not likely what you wanted. Here is link to playfield videos: https://vpinball.com/VPBdownloads/pinball-fx-playfield-videos-audios-flyover-91-tables/ I do have a bunch as well, but not complete up to the newest Williams packs. https://www.gameex.info also has some in their FTP site (/-PinballX-/Media/Pinball FX3/Table Videos), but you have to be paid member to access FTP location.

A somewhat obscure Apple II game that loaded in DB but cannot find a logo for it. This was as large image could find from the box cover. Appreciate any help to prep a proper logo, since my feeble attempts at BG removal didn't look acceptable to load in DB. Thank you.

I assume you are using MAME standalone. Might try going into the Mame Nvram and Sta (save states) folders and removing the file associated with the rom name (or renaming/moving). You may have none or combination of those files depending on your setup but found those can be good places to start if weird things going on. If that doesn't work then may look at the CFG folder and INI folder to see if anything got saved specific to that game name (assuming other files run fine) and temporarily rename to see if fixes issue. If RA core then there could be some other areas to look.

Did you tell LB to not use quotes and not use extensions for the emulator? Might look at your daphne_log.txt in the Daphne folder and see what errors it is indicating as well.

See here for the subsystem flags beyond NeoGeo CD https://github.com/libretro/FBNeo/blob/master/src/burner/libretro/README.md As noted above, for neocd this is the RA entry assuming you don't use the folder naming option and core setting option: --subsystem neocd I have been using both but now use NeoCD core only when moved over to CHD formatted files. NeoCD can open CHD whereas fbneo core cannot (was worked on but not complete).

@james4434 You might also try AutoHotkey to either call antimicro or depending on how your pad works, may be able to do the commands needed directly in AHK. The additional app feature noted by C-beats works great, but the major issue is that it has to be entered for each game/table, and not per emulator (sadly...I hope it gets added somewhere down the road). There are some tools in the download section to copy the additional app commands from one game to all games in system as well as can do manually but it is a pain if you got more than a few items to add (~96 tables in FX3 in my setup). You can also use the AHK feature built into LB ("Running Autohotkey Script), but again sadly FX3 and Future Pinball have issues with AHK run from within LB. Any scripts within the tab will not run the code. But there is way around this by using AHK outside of LB. So I use an AHK script converted to an EXE (comes with the AHK install tools) to launch the appropriate table from Steam as well as set up my XBOX One Guide button so it will exit FX3 when pressed. I also set it to use ALT Esc to exit FX3 from my keyboard I so don't have to go through the three menus in FX3. Here is example of my setup for the emulator in LB calling the AHK EXE script as the "emulator": Here is the script it is calling. You would need to modify what applies to your controller and then use the AHK tool to convert to standalone AHK. You could also call antimicro similarly (so then just get rid of all the text after #IfWinActive). ;AHK.EXE SCRIPT - Pinball FX3 ;Use ALT ESC from keyboard to exit FX3. Also use XBOX Guide Button to exit #SingleInstance, Force Run, "c:\program files (x86)\steam\Steam.exe" -applaunch 442120 -class -table_"%1%" #IfWinActive ahk_exe Pinball FX3.exe SendMode, Input $!Esc:: Process, Close, Pinball FX3.exe ExitApp return $vk07:: Process, Close, Pinball FX3.exe ExitApp return Note that I did this before the Game Controller Mappings in LB were improved over last 6 months as well as the Pause feature addition. For example, a normal FX3 setup will now exit with my controller key combos in LB but unfortunately the Pause Menu still will not trigger. But in my case, it really dispenses with the Guide exit need I had prior. For the moment, I have just left as I have since it is working.

@C-Beats Sent info.

@oblivioncth As you noted later in your comment above, you tell LB to use the folder names for naming versus the "rom" name. With that feature, it imports and scrapes correctly for most of the games. There were a few that I had to manually adjust but for most part LB is pretty good about fuzzy matching.

@oblivioncthOne other option is to move to pointer text files named so ScummVM knows what game to launch. This allows you to dispense with any launcher type setups since you are directly using ScummVM (or Retroarch version) executable. The painful part is initially getting those files generated (to which the above tool helped me do initially) for the specific games you have and placed directly inside the game folders. The thread I linked below shows how to do it (3rd message from end) along with a zip file (at end of thread) of the games I had with text pointer files that will work with standalone ScummVM or RA. Once you get everything working then changes to versions don't impact your install either from LB side or ScummVM. If new games become compatible with ScummVM, you just make text pointers like the others and add accordingly to their game folder. The main reason I went to the bother initially was have the LB pause screen feature (for manuals) which works fine once you are back to using the executable without BAT files. Anyway, an option, not as easy as a couple clicks with the tool but does have advantage of doing once and done.

I would try a new RA install to a separate directory from your current RA install and see if the issue pops up on new install. When I have fried my RA install for whatever reason in past have done that and if it works on the new install, then copy my CFGs, config folder, System folder, overlays folder, and saves folder over in stepped manner. Somewhat of a pain but usually can find the problem item that way. Most times it was a corrupted/wonky setting in CFG file (although looked fine).