sundogak

Already done. Page 32, 51 and 52.

You can widen the screen by dragging the side pane wider (see red area). Or you can double click on video for full screen. Otherwise it is theme dependent and would need to alter code there.

see this thread for AHK scripts in your emulator tab within LB (Running script) that will exit with XBOX Button. For example: vk07:: Process, Close, {{{StartupEXE}}} vk07 is the Xbox button on an Xbox one controller

If just running ISO on your hard drive (and not via an actual CD player) then your setup should be something like this in LB: The error in your screen snap indicates that for some reason the emulator isn't getting the name/path of the ISO file. Double check you are not trying to launch a separate configuration file or have a conflict (typically stored in \PCSX2\inis). If you have a non-standard setup then may need to indicate in LB in the Default Command Line Parameters where your ini files are located: --cfgpath="Path": Specifies the configuration files path to use instead of inis. --cfg="CFGFile": Specifies the configuration file to use instead of PCSX2.ini (does not affect plugins). See here for more info Normally, you do not have to set these if running a standard PCSX2 setup so wouldn't add them if you haven't done any custom paths. Lastly, the "release" version (1.6) lags quite a bit behind, so might check what version of you have. Nightly versions (+1.7) are here. Just make sure you make a backup if using 1.6 and going to 1.7 since difference in plugins/etc. There also shouldn't be anything to change in the CDVD plugin.

1) Does it work outside LB in MAME? 2) Why are you using Mess? MAME and MESS have been merged for quite some time now so likely means using an old version. 3) the command you have in LB is correct with a7800 -cart and what I have and works fine. Double check by retyping the command. Sometimes errant space/character can cause troubles. 4) If doing software list stuff in MAME (i.e., non-Arcade) AND they are unzipped and in non-MAME naming format then make sure you have the boxes below unchecked. 5) Are you sure your ROM set is valid and not corrupted? MAME can run a78 ROMS (i.e., not MAME software list standard zips) but they have to have been dumped correctly.

If so inclined, you can always open up the individual platform XML files under Launchbox\Data\Platforms where the notes data are stored and search accordingly for whatever is you don't want to see (making backups of original XMLs first..but don't store backups in Data directory). After that, you would need to not import/update anything notes related, or your curated data will be overwritten with the user DB provided information. Or, use the bulk edit wizard and nuke all notes completely and update however way you wish.

A summary of options here

No, not within LB

@noMADx469The white bordered versions are simply scans of the original media but have not had any work to cut out the border and hole. Someone has to have taken a scan and using a media program like Photoshop or GIMP remove the white space. There are templates that people have done to help with process, so the edges and rings are uniform. However, to do a "good" disc cut, it is relatively time consuming. Scans can be crooked/warped, need touchup, and each system had unique ways of how the CDs/DVDs were mastered (different holes mostly). A quick and dirty cut can be done, but those are usually obvious with rough edges, spindle not centered (which in a BB theme where disc spins will "wobble") and just overall poor cut out. PNG supports transparency whereas JPG does not, which is why you see that the cut versions are all PNG. But I can take a JPG file and simply convert it to PNG but that doesn't automatically address the cutout issue. So, making PNG the standard wouldn't resolve the issue you capture. Plus, the JPG images are good placeholders until someone comes along to clean up the image. Example of lots of time/skill to do cut outs for DC:

Plus, the audit feature in Tools menu which has the most common media types and can sort by zero entries.

@rodww Check your Battle.net settings here: If not set to minimize the Battle.net app will take focus back from BB and LB.

Try with the PBA Configuration Utility (Display DX11) and set Window Mode to Full Screen instead of Window.

Viking already did this. It is in the very first posting of this thread.

Already done...see page 19.

You don't have to mess with the shortcuts, just make sure signed in and BattleNet running or it will just go to the launch screen but not actually run the game that your application path for the game is pointed to the Battle.net.exe root folder is set correctly to C:\Program Files (x86)\Battle.net (assuming standard C drive install) that you use the game specific code (first page ones still work) and place in Application Command-Line Parameters field. See example below: For all Blizzard Games change Update Application Path and Root Folder (example shown in snapshot is for Diablo II Resurrection): Application Path: C:\Program Files (x86)\Battle.net\Battle.net.exe Root Folder: C:\Program Files (x86)\Battle.net Then the game specific items are same as listed on first page: Application Command Line- Parameters for Diablo Resurrection: --exec="launch OSI" Application Command Line- Parameters for Diablo III: --exec="launch D3" Application Command Line-Parameters for Overwatch: --exec="launch Pro"

There is a Daphne logo in the very first page, download link by Viking. It is in the Arcade zip file. There is also a generic laser disc logo on the first page postings.

You might double check and see if you have a service or anything running in task manager with "nahimic" in the title. It is audio junkware that comes with Realtek audio drivers (typically) and causes various problems (graphics and audio) if running with emulators (MAME and VPX to name a few). It has a bad habit of popping up during updates without asking to turn back on. Also verify nothing got changed in your MAME.ini. Maybe run a quick test by backing up your original MAME.ini and using a default to see if some setting got changed. Other than that, something is running that is conflicting so would be trial/error to see what is running in your task manager and terminating to see if corrects.

The "Hell" Gottlieb table isn't in the LB DB so there is no metadata to import unless you add it in the DB (any user can add data). In this case, LB guesses incorrectly and picks the Frankenstein table since it has "hell" in the title (Shelley's). Pinball metadata for most part is relatively limited in LB DB versus other platforms for various reasons.

Well, one item is you are using an old beta. Current version is 12.6. So would update at least to the 11.13 release.

Here you go:

If you are using it for that limited use case, then you might look at the smaller bay units (2 bay or 4 bay). Particularly if using in "JBOD" (just a bunch of disks) mode and not using RAID you will not lose any capacity due to RAID redundancy. I wouldn't recommend doing non-RAID on anything +4 disks and larger unless you REALLY don't care about your time and data. Even if you have data or access to replacement, there is typically the time factor of getting it into use form/tagging, etc as well as physical time to copy back/download. If you have an 8-disk bay unit in non-RAID volume across all drives, and any of the 8 drives has corrupt data or dies, you lose data across entire volume. I have had hard drives die, but never any issues with RAID itself, particularly if using off the shelf RAID setup like QNAP or Synology. Now if you are keeping off NAS off most times then drive wear and tear will be less, so maybe for your use case not a big deal. Just something to consider. Also, if intention is to use WAN access, make sure you got permissions/NAS firewall set correctly to avoid idiots who have nothing else better to do than mess with people's stuff.

@Runadumb I just hit this recently since converting some iso's to CHD. The standard 7zip install doesn't include the standalone 7za.exe. However, if you installed 7zip through Windows installer you can simply just change the script to: "C:\Program Files\7-Zip\7z.exe" x -y -o%new_dir% "%%f" or you can copy the 7z.exe to local folder along with chdman.exe and batch and will work as well. Also "rem" out this line if you don't want your zips to be deleted since in my case I wanted my source 7z files to remain. rem del /q /s "%%f"

Correct, the 1821+ is the newer version of the 8-bay series (which is the DS18## designation) that came out this year. The 1821 has a faster CPU versus the 1819+. I would always go with as many bays as you can afford initially even if you don't plan on filling. The 8-bay seems to be sweet spot versus the pricier 12-bay. The most common way to get files to other clients is you setup a shared folder that is then visible on your home network. Then you can map that folder to your clients (Apple, Linux, Microsoft). For client machines, you then see the NAS like another computer on the network and then under that you will see folders that are shared. To keep things consistent, I map all my shares on the NAS consistently across all clients. You can set permissions to the folders to however way you want (everyone, particular users or groups, read only, etc). For home setup, I keep simple and block all WAN access (i.e., outside home net). What Windows sees on home my network with the 1819 and 1817 units (you can name whatever want): After you map a drive in Windows to folder on NAS (you can make any drive letter that is available): You can also setup as an iSCSI drive to make the client think the folder/drive on the NAS is actually just like a connected physical drive, but I have never messed with all that so cannot share much info there. Shared folders like above work with any emulation I have dealt with as well as works okay with SYMLINKS on Windows. However, there are some modern PC game clients, namely BattleNet and EA/Origin, that will refuse to run on a shared NAS folder "because it causes issues" per those game publishers (which is baloney). That would be case where iSCSI might work, but again haven't tried (I just keep PC games local...plus modern games larger/need fast access). Drive wise you should make sure to stick with actual NAS drives particularly if in the 8-bay realm or larger. These things will be running 24/7. Seagate IronWolf, Seagate EXOS (enterprise, cheaper but noisier), and WD Reds. I have used all at one point or another (can intermix) but mostly using Seagate since WD seems to be consistently pricier. The Reds seem to be the quietest with the Seagate's you will hear a lot of "drive heads moving around" if you have the NAS on your desk. Depends on your sensitivity to those things. Also, RAID can "feel" like a backup system, but it isn't. It is simply drive redundancy where if a drive dies the whole NAS doesn't lose data. The key is you have to swap out the faulty one with a new one and with a large multi-TB partition it can take DAYS to rebuild. While it is rebuilding if you lose another drive (or two depending on how setup if use SHR), then you lose all data. Having a spare HD of same size as your installed sets helps (they tend to die when everyone is out of stock...or high prices due to whatever supply chain issue). I am also religious about if the drive testing starts (does on schedule you set) showing any drive errors, I swap it out. Even if you have backups, just replacing everything can take a long time to replace TBs of data. If go Synology, you will also need to decide on RAID type since you are fixed with that decision unless you nuke the whole storage pool (basically, wipe and reformat). You can use normal RAID, or Synology's "flavor" which has some advantages. I have mine all set to Synology Hybrid Raid (SHR) which is basically RAID 5 but allows swapping out larger drives and partition will be resized (over multiple days). Anyway, all seems daunting at first but once you get the hang of it, they are cool tools and handy for storage as well as useful for various Apps including running Docker. Edit: I should also mention you can "roll your own" NAS with things like UnRaid and FreeNAS. I looked into them way back (sure they have matured) and can get a cheaper/more flexible NAS versus QNAP or Synology. Although comfortable building that sort of stuff, I just wanted something that would "work" with minimal hassle. The tradeoff is pricier versus home brew relative to feature set and you are locked into the Synology and QNAP way of things which are modified Linux kernels.

Having the ROMs/Images on NAS is usually not an issue, particularly anything non-CD based. The time needed to pull a relatively small size ROM file for cart based systems isn't a big issue and the lag would be at the beginning of the game so once running wouldn't see any difference. The bottleneck will be images and media caching if that is not done locally. If you run LB locally then won't have issues there. One thing to think about is how to synchronize the local LB setups as well as emulators on the local setups (if at all). Something like FreeFileSync works well to sync media to the other local installs. Also, for CD based emulation (or MAME CHDs), those files are much larger so if you have slow network or doing wireless that can lag on retrieving parts and pieces. So, a key piece is what your network speed is as well as what type of emulation you are wanting to do. There are a couple threads here with people's experience and for some it isn't a big deal with lag. For me, when first tried it, the lag was noticeable on a wireless setup (several years ago generation wise on wireless). However, I haven't been running games off the Synology and use it strictly as a "master file backup". I then use FreeFileSync to sync the 3 different setups from the master: 1) kids - stripped down simple games 2)TV Room - subset of games good to play on large screen 3) main PC with full setup. For setups 1 and 2, rarely change them so those are pretty static and size wise the installs are small since not the whole rom set. I did this originally since the place we were living in at the time was all wireless to the clients and I just couldn't get good consistent speed to the NAS (upstairs..far side of house). So, I just did local installs inclusive of any games/ROMs. My main PC and the NAS have full sets of each because I had too much time invested to lose my setup (i.e., have a backup..Synology has a file sync tool to do this as well). This new place has wiring to each room and can mostly get 2.5 Gb speeds to clients as well as have 10 Gb cards on the Synology's. I did some test, and works well off the Synology only, but just haven't bothered messing with the all local setups since "they work". As for the NAS type/brand, almost any of the major ones will work fine so really comes down to price/size of NAS you want. In past used ReadyNAS and currently use Synology 1819+ and an older 1817+. QNAP also makes reputable systems. The bottleneck on the NAS with 10 Gb network cards becomes the drives, even at 7200 rpm (unless $$ and use SSDs). So with all that, any slowdowns you see will not be limited by the NAS but will be your home network speed to get to the NAS data. Flakey wireless? Then likely not going to be happy with anything CD based. Cart based should work well over most any setups assuming you locally install the media, emulators, and LB. Fast network/hard line at 2.5 Gb to 10 Gb range, then wouldn't be much different in performance to USB external drive.

Within LB, go to Tools, Options, Media...then set your Box Front Priorities to however you want as far as media order preference.