Jump to content
LaunchBox Community Forums

sundogak

Members
  • Content Count

    633
  • Joined

  • Last visited

  • Days Won

    4

sundogak last won the day on May 7

sundogak had the most liked content!

Community Reputation

296 Excellent

1 Follower

About sundogak

  • Rank
    64-Bit Supercomputer

Recent Profile Visitors

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

  1. You can force load BIN files via LB it is just through the RA frontend that you won't see non-WS extensions. Just drag and drop the BIN file in LB and then associate with the WonderSwan platform and have Retroarch setup as the emulator. LB will launch as a command line and it will load a BIN file even though the core via the RA front end will not see it since looking for different extensions. You can also load the MAME zip files the same way but you would need to make sure to check the extract rom box. Then LB will extract first and send to RA as BIN. If this causes issues with your other RA setups then either setup another RA emulator instance or use the first method by extracting first and setting to point BIN versus ZIP. Otherwise, no, you cannot force the core in the RA content loader view to see anything that is not a core valid extension. However, via command line (i.e., LB method above), RA will try and load whatever you tell it to since the content view restricting extensions is not applicable. Of course you have to be sure the file you are trying to send is valid or obviously won't work regardless.
  2. sundogak

    sym links

    This tool mentioned here to move the cache files via sym links works well so would think you could use for what you wan to do
  3. Like JoeViking245 said, it is not truly portable. But my original setup was on an external drive and you can make it "mostly" portable with a few extra steps on new CPU (CPU #2). All the needed install files are placed in the directory, so that can be copied to new location. Just make sure you keep the same path mappings. So for example, my external/NAS drive was always called "G". That takes care of not having to mess with table paths, etc. Make backup of the registry keys at [HKEY_CURRENT_USER\Software\Future Pinball] and all sub keys on working setup. Again, you drive mappings have to be consistent here or will cause issues. Open up the registry backup file in text editor to view it and make sure all keys are under Future Pinball location only. Install via the BAM/FP installer on new CPU #2 Merge your registry settings on CPU #2 with the backed up version from CPU#1. Again, only the FP keys or will likely fry your Windows setup on CPU #2. Visual Pinball is similar although a bit more complicated because VP has more than one registry file you have to copy over and also have to watch for installer overwriting key ini files in install directory : [HKEY_CURRENT_USER\Software\Visual Pinball] [Software\Freeware] << this is VPinMAME key set [HKEY_CURRENT_USER\Software\UltraDMD] << if you have used UltraDMD If you use DOFLINX or B2S there are also keys for that as well.I
  4. For the 1819+ or 1621+ (models that use DSM 6), it only allows EXT4 or Btrfs as file system for internal drives. I recommend Btrfs over EXT4 if for nothing else, the fast copy/cloning of folders ability over EXT4. I have that setup on my 1817+ and 1819+ and works well. SMB encryption is off by default unless checked under File Services, Advanced settings. Also the Synology Hybrid Raid (SHR) over RAID 5 provides some additional future flexibility but with the same features as RAID 5. Particularly for the larger 6 and 8-bay models. Your decision on file system and RAID type is pretty much fixed once setup up in Storage Manager unless you backup and nuke the storage pool for the whole NAS. That takes substantial amount of time with large drive setups.
  5. Currently for the IIGS there is no transwarp option slot although that card option is available for the the Apple IIe series (-slot# twarp). There is a note in the MAMEDEV wiki that they are planning on adding ZipGS acceleration in 0.227 (which is delayed until December). You can change the CPU speed via -speed flag multiplier but that makes everything fast. Somewhat depends on what you are actually trying to do.
  6. If you have a MAME set you already have full set of Naomi and Naomi 2 games. This site has useful tool to allow you to search and list roms in the bios set. Click on Additional Filters and then search by bios/set (in this case NAOMI2). Then you can export the file list under Options. An example of the output is attached for Naomi 2 and Naomi 2 GD with no clones. If want clones then go to the site and uncheck as output option. You can set up a batch file to copy zip files based on the names below or manually copy. Anything listed with a "GDS" in name is a Naomi 2 GD system (CD ROM data along with ROM) so they will have corresponding CHD file along with the ROM zip. Name: Description for NAOMI 2 Set no clones as of 0.226: beachspi "Beach Spikers (GDS-0014)" clubkcyc "Club Kart for Cycraft (Rev A) (GDS-0029A)" clubkprz "Club Kart Prize (Export, Japan, Rev A)" clubkpzb "Club Kart Prize Version B (Export, Japan)" clubk2k3 "Club Kart: European Session (2003, Rev A)" clubkrt "Club Kart: European Session (Rev D)" initdexp "Initial D Arcade Stage (Export, Rev A) (GDS-0025A)" initd "Initial D Arcade Stage (Japan, Rev B) (GDS-0020B)" initdv2j "Initial D Arcade Stage Ver. 2 (Japan, Rev B) (GDS-0026B)" initdv3e "Initial D Arcade Stage Ver. 3 (Export) (GDS-0033)" initdv3j "Initial D Arcade Stage Ver. 3 (Japan, Rev C) (GDS-0032C)" inidv3cy "Initial D Arcade Stage Ver. 3 Cycraft Edition (Export, Rev B) (GDS-0039B)" soulsurf "Soul Surfer (Rev A)" kingrt66 "The King of Route 66 (Rev A)" vf4cart "Virtua Fighter 4 (World)" vf4evo "Virtua Fighter 4 Evolution (Version B) (Japan) (GDS-0024C)" vf4evoct "Virtua Fighter 4 Evolution (World)" vf4tuned "Virtua Fighter 4 Final Tuned (Ver. B) (GDS-0036F)" vf4 "Virtua Fighter 4 Version C (GDS-0012C)" vstrik3 "Virtua Striker 3 (GDS-0006)" vstrik3c "Virtua Striker 3 (World, Rev B)" wldrider "Wild Riders" Example of Naomi 2 GD folder with CHDs
  7. Any image can be put in the marquee LB folder (or you can set priorities to pull in). But the image proportions may not be really the best for use as a marquee depending on what you want to do.
  8. In Bigbox. Go to Options, General. Toggle off, Show Startup Splash Screen
  9. @Colorman3605 Current RPCS3 version works okay on my setup with LB and no launch errors. I assume you have verified they work in RPCS3 directly, outside of LB since sounds like somethings not right with the RPCS3 install if getting that error. As far as what LB points to, it is in the normal directory structure and the eboot.bin file. So for example, Demon Souls for US, LB points to this file:
  10. Daphne emulations needs both ROMS (how the game works), VLDP files (the actual video portion), and framefiles (text files that are basically index pointers for the video. Google search is your friend for Daphne VLDP. Also Internet Archive for Daphne.
  11. If you are just talking making it easy to move from new PC to new PC, then it isn't that complicated. You just need to be consistent about where you mappings are from old to new. Almost everything if arranged properly could just be mirrored over to new PC (if installed on local drive). Or just get an external drive, copy the stuff there, map it to something like "G" or a letter you know won't conflict later, set everything up and will be good to go later. You may have to mod a few things but otherwise all on there. 90% of the emulators (except pinball) install everything in whatever folder you select so there isn't anything to install from Windows perspective. As to the LB question, again, if just moving from PC to PC you could install on C drive (with all other stuff on external), copy the LB folder from old PC to new PC, run the installer for LB on new PC which will keep all settings but make sure setup on Windows correctly, and LB will still look for games where you had them as long as paths consistent (i.e. if on local drive, NAS, or external...just pick consistent drive letter). Or, install the whole deal on external but like said before, you will have a speed hit of varying degrees on image/scrolling depending on if you setup a cache locally or not. But it will work, my initial setup was on an external "G Drive" which had ALL emulation stuff (LB, emulators, media, games). A NAS will work identically to external drive, just may be additional speed hit on top if slow NAS and/or network. Local, external, or NAS ultimately all work the same as far as portability as long as make consistent choice on paths. Difference will be on performance of LB.
  12. @ThomasOEM If you are speaking about MAME software list there are a few threads running around on LB if do a search. This website (click "All Systems" button at left and then look under Name column) has comprehensive list of what you put in for the "name" in the Default Command-Line Parameters along with any options (usually computer based emulation) as well as media type name (for those that have multiple like cassettes, floppies). But in general, software lists work similarly in either one of two setups mentioned (i.e., with the "use file name only..." checked or not checked. Most I have encountered work with same settings as MAME arcade (no check boxes). As Neil9000 mentioned, for most part I don't use MAME for anything other than arcade and a few "oddball" platforms where there are no emulators or working Retroarch cores. As LB currently is setup, software list import is not the easiest and for cart based systems (or CD) I found easier to Retroarch or standalone dedicated emulator versus MAME. But in MAME, SNK Neo Geo AES is the only other one that wouldn't work using arcade setup. A few examples I have that run via normal MAME arcade setup:For computer based emulation in MAME where you have floppies (like Apple II or Atari 800) I have found that can use either (with the box checked or no). When used without the media type (i.e., flop1) and the "Use file name only.." checked if there are multiple floppy images in the zipfile, then MAME will auto load the floppies into appropriate slots (i.e., flop1, flop2). It uses the HASH file information to tell it how to load things, which is handy.
  13. @ThomasOEM I assume you were over at PD asking this. This is one of those platforms that requires a checkbox checked versus what is in the Arcade setup. So make an additional MAME emulator entry. I called mine "MAME_MESS" but you can call whatever. Then under that emulator, check the box "Use file name only..." Note this isn't checked in the normal MAME arcade setup. Example with 1942 game in software list for NES Then for NES platform input the nes -cart setting like normal (this is platforms only for my "MAME_MESS" emulator: Basically, one "MAME" version for those that require "Use file name only...." checked and others that don't.
  14. @Smilator Everything you propose can be done in theory but in practice will run into issues or if really look at situation will have different use cases anyway. An external drive or a NAS will have similar considerations. The ROMs/Games/Media are easily centralized, beyond that it gets sticky. Most emulators are portable or have a portable mode with the exception of things like pinball simulation (e.g., Visual Pinball). But portable only in the sense that they install all needed files in one root folder and don't have to be installed on a local "C drive" along with no Windows registry or files scattered around the Windows system. However, portable mode emulators are not designed to have multiple clients opening their files at same time. Most emulators have some sort of CFG, INI or other settings they are modifying while running the emulator. Two clients hitting the emulator settings at same time will cause all sorts of problems/corruptions. LB is same story there as well with XML files opened/modified while running. Also as @usuallee76 noted you may run into differences in video types, controllers, or capability from client to client that will mean at a minimum you will have to adjust those parameters per client. So even if the setup files for the emulator are not modified you still have config files with specifics about monitor size, GPU type, controllers, that may not be same from client to client. But you could have one "master" that you maintain and then replicate that for 90% of static installed files but the trick is knowing the 10% to adjust per client. I think also once you start really thinking about how you will use the other clients, you will likely see they are not really going to be all the same anyway. I have main install (high power PC, full meal deal), TV room, kids room. Each of those are subset of main "master" but they have different focus points. For example, I wouldn't want LB to be same theme for all three. TV room want a nice large text and simple theme as well as substantially smaller game set than master (no computer based stuff). Kids, they want something "kid" like for theme and with extremely curated game set that is mostly limited to cartridge based systems. The old Intel NUC they run on won't run PS1 or new games anyway. These setups also don't really change that much so the worry of keeping synced isn't too much a concern. If I do have to do something, I will use FreeFileSync to mirror portions of setups from NAS to local install (which all have "G drive" mapping somewhere so my paths work wherever installed). But ultimately, you will not be able to just take an external drive and plug it in to whatever new PC and expect it to run 100% out of the box without config updates/changes to reflect hardware on that PC. For NAS, anything directly shared with multiple clients would need to be static files and not anything the emulator (or LB) is modifying.
×
×
  • Create New...