Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'chd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LaunchBox
    • Android
    • Beta Testing
    • Collections and Builds
    • Features
    • Linux
    • News and Updates
    • Noobs
    • Troubleshooting
    • Website/Forum Support
  • User-Created Content and Downloads
    • Big Box Custom Themes
    • Big Box Sound Packs
    • Big Box Startup Videos
    • Custom Theme Tutorials
    • Game Media
    • LaunchBox for Android Custom Themes
    • LaunchBox for Windows Custom Themes
    • Pause Themes
    • Platform Media
    • Playlists & Playlist Media
    • Startup Themes
    • Third-Party Applications and Plugins (Released)
    • Third-Party Applications and Plugins (Development and Beta Testing)
    • Videos
  • LaunchBox Games Database
    • News and Updates
    • Contributions
    • Features
    • Troubleshooting
  • Off Topic
    • DOSBox
    • Emulation
    • Games
    • Monkeys
    • Buy / Sell / Trade

Categories

  • Big Box
    • Custom Themes
    • Startup Themes
    • Pause Themes
    • Sound Packs
    • Startup Videos
  • LaunchBox for Windows
    • Custom Themes
    • Custom Badges
  • LaunchBox for Android
    • Custom Themes
  • Third-party Apps and Plugins
  • Game Media
    • 3DO Interactive Multiplayer
    • Aamber Pegasus
    • Acorn Achimedes
    • Acorn Atom
    • Acorn Electron
    • ALF TV Game
    • Amstrad CPC
    • Amstrad GX4000
    • Android
    • APF Imagination Machine
    • Apogee BK-01
    • Apple II
    • Apple IIGS
    • Apple Mac OS
    • Arcade
    • Atari 800
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Jaguar
    • Atari Jaguar CD
    • Atari Lynx
    • Atari ST
    • Atari XEGS
    • Bally Astrocade
    • Bandai Super Vision 8000
    • BBC Microcomputer System
    • Camputers Lynx
    • Casio Loopy
    • Casio PV-1000
    • Coleco ADAM
    • ColecoVision
    • Commodore 64
    • Commodore 128
    • Commodore Amiga
    • Commodore Amiga CD32
    • Commodore CDTV
    • Commodore MAX Machine
    • Commodore PET
    • Commodore Plus 4
    • Commodore VIC-20
    • Dragon 32/64
    • EACA EG2000 Colour Genie
    • Elektronika BK
    • Emerson Arcadia 2001
    • Enterprise
    • Entex Adventure Vision
    • Epoch Game Pocket Computer
    • Epoch Super Cassette Vision
    • Exelvision EXL 100
    • Exidy Sorcerer
    • Fairchild Channel F
    • Fujitsu FM Towns Marty
    • Fujitsu FM-7
    • Funtech Super Acan
    • Game Wave Family Entertainment System
    • GamePark GP32
    • GameWave
    • GCE Vectrex
    • Hartung Game Master
    • Hector HRX
    • Interton VC 4000
    • Jupiter Ace
    • Lviv PC-01
    • Magnavox Odyssey
    • Magnavox Odyssey 2
    • Matra and Hachette Alice
    • Mattel Aquarius
    • Mattel HyperScan
    • Mattel Intellivision
    • Mega Duck
    • Memotech MTX512
    • Microsoft MSX
    • Microsoft MSX2
    • Microsoft MSX2+
    • Microsoft Xbox
    • Microsoft Xbox 360
    • MS-DOS
    • MUGEN
    • Namco System 22
    • NEC PC-8801
    • NEC PC-9801
    • NEC PC-FX
    • NEC TurboGrafx-16
    • NEC TurboGrafx-CD
    • Nintendo 3DS
    • Nintendo 64
    • Nintendo 64DD
    • Nintendo DS
    • Nintendo Entertainment System
    • Nintendo Famicom Disk System
    • Nintendo Game & Watch
    • Nintendo Game Boy
    • Nintendo Game Boy Advance
    • Nintendo Game Boy Color
    • Nintendo GameCube
    • Nintendo Pokemon Mini
    • Nintendo Satellaview
    • Nintendo Switch
    • Nintendo Virtual Boy
    • Nintendo Wii
    • Nintendo Wii U
    • Nokia N-Gage
    • Nuon
    • OpenBOR
    • Oric Atmos
    • Orion-128
    • Othello Multivision
    • PC Engine SuperGrafx
    • Philips CD-i
    • Philips VG 5000
    • Philips Videopac+
    • Pinball
    • Radio-86RK Mikrosha
    • RCA Studio II
    • SAM Coupé
    • Sammy Atomiswave
    • ScummVM
    • Sega 32X
    • Sega CD
    • Sega CD 32X
    • Sega Dreamcast
    • Sega Dreamcast VMU
    • Sega Game Gear
    • Sega Genesis
    • Sega Hikaru
    • Sega Master System
    • Sega Model 1
    • Sega Model 2
    • Sega Model 3
    • Sega Naomi
    • Sega Naomi 2
    • Sega Pico
    • Sega Saturn
    • Sega SC-3000
    • Sega SG-1000
    • Sega ST-V
    • Sega System 16
    • Sega System 32
    • Sega Triforce
    • Sharp MZ-2500
    • Sharp X1
    • Sharp X68000
    • Sinclair ZX Spectrum
    • Sinclair ZX-81
    • SNK Neo Geo AES
    • SNK Neo Geo CD
    • SNK Neo Geo MVS
    • SNK Neo Geo Pocket
    • SNK Neo Geo Pocket Color
    • Sony Playstation
    • Sony Playstation 2
    • Sony Playstation 3
    • Sony PocketStation
    • Sony PSP
    • Sony PSP Minis
    • Sord M5
    • Spectravideo
    • Super Nintendo Entertainment System
    • Taito Type X
    • Tandy TRS-80
    • Tapwave Zodiac
    • Texas Instruments TI 99/4A
    • Thomson MO/TO
    • Tiger Electronics Handheld
    • Tiger Game.com
    • Tomy Tutor
    • Touhou Project
    • TRS-80 Color Computer
    • Vector-06C
    • VTech CreatiVision
    • VTech Socrates
    • Watara Supervision
    • Web Browser
    • Windows
    • Windows 3.X
    • WonderSwan
    • WonderSwan Color
    • WoW Action Max
    • XaviXPORT
    • ZiNc
  • Platform Media
    • Platform Theme Videos
    • Platform Console Images
    • Platform Backgrounds
    • Platform Banners
    • Platform Clear Logos
    • Platform Bezels/Overlays
    • Platform Media Packs
    • Platform Default Image Packs
    • Platform Templates
  • Playlists & Playlist Media
    • Playlists
    • Playlist Theme Videos
    • Playlist Backgrounds
    • Playlist Banners
    • Playlist Clear Logos
    • Playlist Media Packs
  • LaunchBox/Big Box Media

Blogs

  • Jason's Devotions
  • Thatmans Blog
  • THAT NINTENDO SWITCH EARLY REVEAL WAS FROM A STOLEN CONSOLE
  • Version 8.8
  • Game Theme Videos
  • Exclusive Bezels
  • Save Up Your Time by Outsourcing Creative Graphic Design
  • cocktail mass settings mame 4 launchbox?
  • Bigg Homi
  • aj gaming2357

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 10 results

  1. Archive Cache Manager View File A LaunchBox plugin which caches extracted ROM archives, letting you play games faster. Also allows launching individual files from archives, and loading preferred file types from an archive. New in v2.13 Fix config window DPI scaling issue Config window performance improvements Option to skip version during update check New in v2.12 Option to copy non-archive files to cache Support for extracting additional formats Option to extract chd to cue+bin using chdman Option to extract rvz, wia, gcz to iso using DolphinTool Option to specify a launch folder for cached games (game platform, game title, or emulator title) Useful for managing common RetroArch settings Smart Extract option to only extract required files from an archive Useful for merged ROM sets Emulator selection when launching a file from "Select ROM In Archive" list Option to bypass LaunchBox's check the ROM file exists when launching a game Allows launching cached game immediately - no waiting for slow disk spin-up or network latency Allows playing cached games 'offline' if NAS or cloud storage unavailable Config window and UI overhaul Minor bug fixes Description When a compressed ROM (zip, 7z, rar, gz, chd, rvz, etc.) is first extracted, it is stored in the archive cache. The next time it is played, the game is loaded directly from the cache, virtually eliminating wait time. As the cache size approaches the maximum size, the oldest played games are deleted from the cache, making room for new games. Features Skip the extraction wait time for recently played games. Configurable cache size and location. Configurable minimum archive size (don't cache small archives). Option to extract all discs in a multi-disc game, and generate M3U file. Option to copy ROM files to cache without extraction. Option to keep select ROMs cached and ready to play. Select and play individual ROM files from an archive. Filename and extension priorities per emulator and platform (cue, bin, iso, etc). Support for additional archive formats (chd, rvz, etc) Badge to indicate cached games Example Use Cases Why use Archive Cache Manager? Here's some example use cases. Zipped ROMs located on network server or cloud drive, where disk read or network transfer time is slow. ROM library maintained as accurately ripped/dumped collections, where specialised compression formats not an option. Extract and play archives from location other than LaunchBox\ThirdParty\7-Zip\Temp, such as high speed SSD. Playing ripped PS2 games with PCSX2 where the disc image is bin/cue format, avoiding the "CDVD plugin failed to open" error message. Playing MSU versions of games, where need to launch the rom file instead of the cue file from the archive. Your library contains GoodMerged sets, and you want a quick way to play individual ROMs. Installation Download the latest release from https://forums.launchbox-app.com/files/file/234-archive-cache-manager/ or https://github.com/fraganator/archive-cache-manager/releases Unblock the download if necessary (right-click file -> Properties -> Unblock) Extract this archive to your LaunchBox\Plugins folder, then run LaunchBox / BigBox. Within LaunchBox, ensure the emulator or emulator platform has the "Extract ROM archives before running" option checked. Uninstallation Quit LaunchBox / BigBox, then navigate to the LaunchBox\Plugins folder and delete ArchiveCacheManager. Delete the archive cache folder (default is LaunchBox\ArchiveCache). Usage Extracting and Caching Archive Cache Manager runs transparently to the user. All that is required is the emulator or emulator platform has the "Extract ROM archives before running" option checked. Extraction and cache management is carried out automatically when a game is launched. Cache and extraction behaviour can be modified in plugin's configuration window. Multi-Disc Games To use the multi-disc cache feature, check the "Multi-disc Support" option in the Archive Cache Manager config window. The next time a multi-disc game is launched, all the discs from the game will be extracted to the cache and a corresponding M3U file generated. If the emulator \ platform supports M3U files (as configured in LaunchBox), the generated M3U file will be used when launching the game. Otherwise a single disc will be launched, and swapping between cached discs can be done manually in the emulator. Selecting and Playing Individual ROMs From an Archive To play an individual ROM from an archive containing multiple ROMs (different regions, hacks, or discs), right-click it and choose "Select ROM In Archive...". A window will popup with a full listing of the archive contents. Select the desired ROM file, then click Play. That ROM will now launch with the configured emulator. The next time the game is launched via the normal Play option, the previous ROM selection will be automatically applied. To select another ROM, use the same "Select ROM In Archive..." menu. The same menu is also available in BigBox, though currently only supports keyboard input. Keeping Games Cached Games can be marked 'Keep' so they stay cached and ready to play. To keep a game cached, open the plugin configuration window from the Tools->Archive Cache Manager menu. From there a list of games in the cache is shown. Check the Keep box next to the game, then click OK. Badge The plugin includes a badge to indicate if a game is currently in the cache. It is available under the Badges->Plugin Badges->Enable Archive Cached menu. There are additional Simple White and Neon style badges, which can be found in the LaunchBox\Plugins\ArchiveCacheManager\Badges folder. Copy your preferred icon to the LaunchBox\Images\Badges folder and rename it Archive Cached.png. Configuration Configuration can be accessed from the Tools->Archive Cache Manager menu. An overview of each of the configuration screens and options is below. Cache Settings This page shows a summary of the cache storage and currently cache items, and provides options for cache configuration. Configure Cache Clicking the Configure Cache... button opens the cache configuration window. Configure Cache - Cache Path This is the path of the cache on disk. The path can be absolute or relative, where relative paths are to the LaunchBox root folder. Default: ArchiveCache If the cache path is set to an invalid location (LaunchBox root for example), an error message will be displayed when clicking OK. If the cache path is set to an existing path that already contains files or folders, a warning will be displayed when clicking OK. Click Yes to proceed, or No to go back and change the path. Configure Cache - Cache Size This is the maximum cache size on disk in megabytes. The oldest played games will be deleted from the cache when it reaches this size. Default: 20,000 MB (20 GB) Configure Cache - Minimum Archive Size This is the minimum size in megabytes of an uncompressed archive before it will be added to the cache. Archives smaller than this won't be added to the cache. Default: 100 MB Keep A Keep flag can be applied to a cached item. When set, the item will be excluded from cache management and not be removed from the cache. This is useful for less frequently played games which need to load without waiting (very large games, party games, favourites, children's games, etc). Default: Disabled Open In Explorer Clicking the Open In Explorer button will open the configured cache path in Windows Explorer. This button is disabled if the cache path does not exist. Refresh Refreshes the cache summary and list of cached items from disk. Delete Clicking on the Delete button will remove the selected items from the cache (including items with the Keep setting). Delete All Clicking on the Delete All button will delete everything from the cache (including items with the Keep setting). Extraction Settings This page provides settings for archive extraction and launch behviour. Each row in the table applies to the specified emulator \ platform pair. If a game is launched which doesn't match an emulator \ platform, the settings in All \ All will be used. Emulator \ Platform The specific emulator and platform for the settings to be applied to. Add a new emulator and platform row using the Add... button. Remove an emulator \ platform row using the Delete button. When a new row is added its settings will be copied from the All \ All entry, except for Priority which will be blank. Priority Files from an archive can be prioritized in the case where an emulator requires a certain filename or file type. This setting defines the filename or extension priority for the specified emulator and platform combination. The priorities are a comma delimited list, where the highest priority is the first entry, the next highest priority is the second entry, and so on. If a match is not found in the archive when a game is loaded, the priority in All \ All is used. A wildcard (*) can be used to perform partial filename matches. Examples include: bin, iso - Files ending with bin, then files ending in iso, then all other files. eboot.bin - Files named eboot.bin, then all other files. *(*E*)*[!].*, *(*U*)*[!].*, *[!].* - GoodMerged style, prioritizing European 'good' ROM dumps, then USA 'good' ROM dumps, then other region 'good' ROM dumps, then all other files. Note that the priority is applied to all archives, even if they are not cached. The fallback All \ All priority is the basis for the contents of the multi-disc M3U file generation. Be careful removing entries such as cue, unless a specific emulator \ platform is used to handle cue and similar file types. Default: All \ All | mds, gdi, cue, eboot.bin PCSX2 \ Sony Playstation 2 | bin, iso Action The action to take when processing a ROM file. Extract - Extract an archive to the cache. Non-archive files will be passed directly to the emulator. Copy - Copy the game file to the cache. Archive files will copied, but not extracted. Extract or Copy - If the game file is an archive, extract it to the cache. Otherwise copy the game file to the cache. Default: Extract Launch Path The path within the cache to launch the game from. Useful for managing common settings in RetroArch which are based on the game's folder. Default - The archive folder in the cache, which is in the form <Filename> - <MD5 Hash> Title - The game's title set in LaunchBox (e.g. Final Fantasy VII) Platform - The game's platform set in LaunchBox (e.g. Sony Playstation) Emulator - The emulator title set in LaunchBox (e.g. RetroArch) Games will always be extracted \ copied to the <Filename> - <MD5 Hash> location. If the Launch Path is set to something other than Default, the corresponding folder will be created within the cache, and NTFS hardlinks will be created which point to the extracted \ copied files. Default: Default Multi-Disc Check this option to enable multi-disc support. When enabled, the following actions occur when playing a multi-disc game: All discs from a multi-disc game will be extracted \ copied and added to the archive cache. M3U files will be generated, with the name based on the M3U Name setting. The M3U contents will list the absolute path to one cached file per disc, where the file is chosen based on the emulator \ platform file priority, or the special All \ All priority. If the emulator \ platform supports M3U files, the generated M3U file will be used when launching the game. Default: Enabled M3U Name The name of the M3U file created when launching a multi-disc game, and Multi-Disc is enabled. The M3U file name is used by some emulators to create a save file and match settings. Game ID - The unique ID for a game, generated by LaunchBox. This is the same M3U naming convention used by LaunchBox (e.g. 2828d969-4362-49d5-b080-c2b7cc6f7d59.m3u) Title + Version - The game's title and version combined, with (Disc N) removed from the version (e.g. Final Fantasy VII (Europe).m3u) Default: Game ID Smart Extract Check this option to enable smart extraction, which will only extract a single file from an archive if a number of rules are met. See the Smart Extract Settings section for details. Default: Enabled chdman Check this option to extract a chd file to cue+bin files using chdman. The executable chdman.exe must be copied to the folder LaunchBox\Plugins\ArchiveCacheManager\Extractors. Default Disabled DolphinTool Check this option to extract rvz, wia, and gcz files to iso files using DolphinTool. The executable DolphinTool.exe must be copied to the folder LaunchBox\Plugins\ArchiveCacheManager\Extractors. Default Disabled Smart Extract Settings When enabled, the Smart Extract option will check if it's possible to extract only a single file from an archive. For merged archives containing multiple ROM versions and hacks, this avoids the need to extract a potentially large number of files to play a single game. Smart Extract will extract and launch a single file from an archive if the following conditions are met: An individual file has been selected through the "Select ROM in Archive..." right-click menu. All of the file types in an archive are the same, excluding files with Metadata Extensions. All of the file types in an archive are Stand-alone ROMs, excluding files with Metadata Extensions. Stand-alone ROM Extensions A comma delimited list of file extensions which can run stand-alone (no dependencies on other files). Default: gb, gbc, gba, agb, nes, fds, smc, sfc, n64, z64, v64, ndd, md, smd, gen, iso, chd, gg, gcm, 32x, bin Metadata Extensions A comma delimited list of file extensions which indicate ROM metadata, and aren't required to play a ROM file. Default: nfo, txt, dat, xml, json Plugin Settings Always Bypass LaunchBox Path Check When enabled, bypasses LaunchBox's check that a game's application path (ROM file) exists before launch. If a game is cached and the source ROM storage is slow or unavailable, the game will still launch immediately. The bypass check happens automatically if the extract action is Copy, or the file is not zip, 7z, or rar. Default: Disabled Check For Updates On Startup Enable this option to check for plugin updates when LaunchBox starts up. This is a simple version check of the latest release on github, and nothing is automatically downloaded or installed. If a new update is found a message box will appear shortly after LaunchBox is started, with the option to open the download page in a browser. Default: On first run, a message box will appear asking the user if they'd like to enable the update check. Source Code Source available on GitHub, licensed under the LGPL: https://github.com/fraganator/archive-cache-manager Submitter fraganator Submitted 01/03/2017 Category Third-party Apps and Plugins  
  2. Version 2.14

    612 downloads

    A LaunchBox plugin which caches extracted ROM archives, letting you play games faster. Also allows launching individual files from archives, and loading preferred file types from an archive. New in v2.14 New right-click menu option - "Batch Cache Games" Extract or copy multiple games to the cache, ready to play later Bulk cache games from NAS or external storage Cached games can be played even if network or external storage disconnected Description When a compressed ROM (zip, 7z, rar, gz, chd, rvz, etc.) is first extracted, it is stored in the archive cache. The next time it is played, the game is loaded directly from the cache, virtually eliminating wait time. As the cache size approaches the maximum size, the oldest played games are deleted from the cache, making room for new games. Features Skip the extraction wait time for recently played games. Configurable cache size and location. Configurable minimum archive size (don't cache small archives). Option to extract all discs in a multi-disc game, and generate M3U file. Option to copy ROM files to cache without extraction. Option to keep select ROMs cached and ready to play. Select and play individual ROM files from an archive. Batch cache feature for extracting or copying multiple games to cache at once. Filename and extension priorities per emulator and platform (cue, bin, iso, etc). Support for additional archive formats (chd, rvz, etc) Badge to indicate cached games Example Use Cases Why use Archive Cache Manager? Here's some example use cases. ROMs located on NAS or external storage, where disk read or transfer time is slow. ROM library maintained as accurately ripped/dumped collections, where specialised compression formats not an option. Extract and play archives from location other than LaunchBox\ThirdParty\7-Zip\Temp, such as platform specific folder (for RetroArch Content Directory settings). Playing ripped PS2 games with PCSX2 where the disc image is bin/cue format, avoiding the "CDVD plugin failed to open" error message. Playing zipped MSU versions of games, where need to launch the rom file instead of the cue file from the archive. The library contains GoodMerged sets, and you want a quick way to play individual ROMs. Installation Download the latest release from https://forums.launchbox-app.com/files/file/234-archive-cache-manager/ or https://github.com/fraganator/archive-cache-manager/releases Unblock the download if necessary (right-click file -> Properties -> Unblock) Extract this archive to your LaunchBox\Plugins folder, then run LaunchBox / BigBox. Within LaunchBox, ensure the emulator or emulator platform has the "Extract ROM archives before running" option checked. Uninstallation Quit LaunchBox / BigBox, then navigate to the LaunchBox\Plugins folder and delete ArchiveCacheManager. Delete the archive cache folder (default is LaunchBox\ArchiveCache). Usage Extracting and Caching Archive Cache Manager runs transparently to the user. All that is required is the emulator or emulator platform has the "Extract ROM archives before running" option checked. Extraction and cache management is carried out automatically when a game is launched. Cache and extraction behaviour can be modified in plugin's configuration window. Multi-Disc Games To use the multi-disc cache feature, check the "Multi-disc Support" option in the Archive Cache Manager config window. The next time a multi-disc game is launched, all the discs from the game will be extracted to the cache and a corresponding M3U file generated. If the emulator \ platform supports M3U files (as configured in LaunchBox), the generated M3U file will be used when launching the game. Otherwise a single disc will be launched, and swapping between cached discs can be done manually in the emulator. Batch Caching Games Multiple games can be cached at once using the Batch Cache Games window. Select one or more games in LaunchBox, then right-click a game and choose the "Batch Cache Games..." option. A window will popup displaying the list of games, and begin checking the extracted ROM sizes. Once the checks are complete, click the Cache Games button to begin caching. Games are cached according to the plugin's emulator and platform settings. A game may be extracted, copied, or no action taken if it doesn't match a caching rule, or it's already cached. Each game's caching progress will be displayed in the Status column, and a progress bar at the bottom of the game list shows the overall caching progress. If there are any errors while caching, an error message is displayed with the option to continue or stop. Tip: For games stored on a NAS or an external drive, use Batch Cache Games to cache a selection of them locally. Enable the plugin's Always Bypass LaunchBox Path Check option to allow the cached game to be launched directly, even if the network or external drive is disconnected! Selecting and Playing Individual ROMs From an Archive To play an individual ROM from an archive containing multiple ROMs (different regions, hacks, or discs), right-click it and choose "Select ROM In Archive...". A window will popup with a full listing of the archive contents. Select the desired ROM file, then click Play. That ROM will now launch with the configured emulator. The next time the game is launched via the normal Play option, the previous ROM selection will be automatically applied. To select another ROM, use the same "Select ROM In Archive..." menu. The same menu is also available in BigBox, though currently only supports keyboard input. Keeping Games Cached Games can be marked 'Keep' so they stay cached and ready to play. To keep a game cached, open the plugin configuration window from the Tools->Archive Cache Manager menu. From there a list of games in the cache is shown. Check the Keep box next to the game, then click OK. Badge The plugin includes a badge to indicate if a game is currently in the cache. It is available under the Badges->Plugin Badges->Enable Archive Cached menu. There are additional Simple White and Neon style badges, which can be found in the LaunchBox\Plugins\ArchiveCacheManager\Badges folder. Copy your preferred icon to the LaunchBox\Images\Badges folder and rename it Archive Cached.png. Configuration Configuration can be accessed from the Tools->Archive Cache Manager menu. An overview of each of the configuration screens and options is below. Cache Settings This page shows a summary of the cache storage and currently cache items, and provides options for cache configuration. Configure Cache Clicking the Configure Cache... button opens the cache configuration window. Configure Cache - Cache Path This is the path of the cache on disk. The path can be absolute or relative, where relative paths are to the LaunchBox root folder. Default: ArchiveCache If the cache path is set to an invalid location (LaunchBox root for example), an error message will be displayed when clicking OK. If the cache path is set to an existing path that already contains files or folders, a warning will be displayed when clicking OK. Click Yes to proceed, or No to go back and change the path. Configure Cache - Cache Size This is the maximum cache size on disk in megabytes. The oldest played games will be deleted from the cache when it reaches this size. Default: 20,000 MB (20 GB) Configure Cache - Minimum Archive Size This is the minimum size in megabytes of an uncompressed archive before it will be added to the cache. Archives smaller than this won't be added to the cache. Default: 100 MB Keep A Keep flag can be applied to a cached item. When set, the item will be excluded from cache management and not be removed from the cache. This is useful for less frequently played games which need to load without waiting (very large games, party games, favourites, children's games, etc). Default: Disabled Open In Explorer Clicking the Open In Explorer button will open the configured cache path in Windows Explorer. This button is disabled if the cache path does not exist. Refresh Refreshes the cache summary and list of cached items from disk. Delete Clicking on the Delete button will remove the selected items from the cache (including items with the Keep setting). Delete All Clicking on the Delete All button will delete everything from the cache (including items with the Keep setting). Extraction Settings This page provides settings for archive extraction and launch behviour. Each row in the table applies to the specified emulator \ platform pair. If a game is launched which doesn't match an emulator \ platform, the settings in All \ All will be used. Emulator \ Platform The specific emulator and platform for the settings to be applied to. Add a new emulator and platform row using the Add... button. Remove an emulator \ platform row using the Delete button. When a new row is added its settings will be copied from the All \ All entry, except for Priority which will be blank. Priority Files from an archive can be prioritized in the case where an emulator requires a certain filename or file type. This setting defines the filename or extension priority for the specified emulator and platform combination. The priorities are a comma delimited list, where the highest priority is the first entry, the next highest priority is the second entry, and so on. If a match is not found in the archive when a game is loaded, the priority in All \ All is used. A wildcard (*) can be used to perform partial filename matches. Examples include: bin, iso - Files ending with bin, then files ending in iso, then all other files. eboot.bin - Files named eboot.bin, then all other files. *(*E*)*[!].*, *(*U*)*[!].*, *[!].* - GoodMerged style, prioritizing European 'good' ROM dumps, then USA 'good' ROM dumps, then other region 'good' ROM dumps, then all other files. Note that the priority is applied to all archives, even if they are not cached. The fallback All \ All priority is the basis for the contents of the multi-disc M3U file generation. Be careful removing entries such as cue, unless a specific emulator \ platform is used to handle cue and similar file types. Default: All \ All | mds, gdi, cue, eboot.bin PCSX2 \ Sony Playstation 2 | bin, iso Action The action to take when processing a ROM file. Extract - Extract an archive to the cache. Non-archive files will be passed directly to the emulator. Copy - Copy the game file to the cache. Archive files will copied, but not extracted. Extract or Copy - If the game file is an archive, extract it to the cache. Otherwise copy the game file to the cache. Default: Extract Launch Path The path within the cache to launch the game from. Useful for managing common settings in RetroArch which are based on the game's folder. Default - The archive folder in the cache, which is in the form <Filename> - <MD5 Hash> Title - The game's title set in LaunchBox (e.g. Final Fantasy VII) Platform - The game's platform set in LaunchBox (e.g. Sony Playstation) Emulator - The emulator title set in LaunchBox (e.g. RetroArch) Games will always be extracted \ copied to the <Filename> - <MD5 Hash> location. If the Launch Path is set to something other than Default, the corresponding folder will be created within the cache, and NTFS hardlinks will be created which point to the extracted \ copied files. Default: Default Multi-Disc Check this option to enable multi-disc support. When enabled, the following actions occur when playing a multi-disc game: All discs from a multi-disc game will be extracted \ copied and added to the archive cache. M3U files will be generated, with the name based on the M3U Name setting. The M3U contents will list the absolute path to one cached file per disc, where the file is chosen based on the emulator \ platform file priority, or the special All \ All priority. If the emulator \ platform supports M3U files, the generated M3U file will be used when launching the game. Default: Enabled M3U Name The name of the M3U file created when launching a multi-disc game, and Multi-Disc is enabled. The M3U file name is used by some emulators to create a save file and match settings. Game ID - The unique ID for a game, generated by LaunchBox. This is the same M3U naming convention used by LaunchBox (e.g. 2828d969-4362-49d5-b080-c2b7cc6f7d59.m3u) Title + Version - The game's title and version combined, with (Disc N) removed from the version (e.g. Final Fantasy VII (Europe).m3u) Default: Game ID Smart Extract Check this option to enable smart extraction, which will only extract a single file from an archive if a number of rules are met. See the Smart Extract Settings section for details. Default: Enabled chdman Check this option to extract a chd file to cue+bin files using chdman. The executable chdman.exe must be copied to the folder LaunchBox\Plugins\ArchiveCacheManager\Extractors. Default Disabled DolphinTool Check this option to extract rvz, wia, and gcz files to iso files using DolphinTool. The executable DolphinTool.exe must be copied to the folder LaunchBox\Plugins\ArchiveCacheManager\Extractors. Default Disabled Smart Extract Settings When enabled, the Smart Extract option will check if it's possible to extract only a single file from an archive. For merged archives containing multiple ROM versions and hacks, this avoids the need to extract a potentially large number of files to play a single game. Smart Extract will extract and launch a single file from an archive if the following conditions are met: An individual file has been selected through the "Select ROM in Archive..." right-click menu. All of the file types in an archive are the same, excluding files with Metadata Extensions. All of the file types in an archive are Stand-alone ROMs, excluding files with Metadata Extensions. Stand-alone ROM Extensions A comma delimited list of file extensions which can run stand-alone (no dependencies on other files). Default: gb, gbc, gba, agb, nes, fds, smc, sfc, n64, z64, v64, ndd, md, smd, gen, iso, chd, gg, gcm, 32x, bin Metadata Extensions A comma delimited list of file extensions which indicate ROM metadata, and aren't required to play a ROM file. Default: nfo, txt, dat, xml, json Plugin Settings Always Bypass LaunchBox Path Check When enabled, bypasses LaunchBox's check that a game's application path (ROM file) exists before launch. If a game is cached and the source ROM storage is slow or unavailable, the game will still launch immediately. The bypass check happens automatically if the extract action is Copy, or the file is not zip, 7z, or rar. Default: Disabled Check For Updates On Startup Enable this option to check for plugin updates when LaunchBox starts up. This is a simple version check of the latest release on github, and nothing is automatically downloaded or installed. If a new update is found a message box will appear shortly after LaunchBox is started, with the option to open the download page in a browser. Default: On first run, a message box will appear asking the user if they'd like to enable the update check.
  3. This is just a heads-up that in recent versions of PCSX2 chd support was added. For me converting iso's and bin/cue's to chd yields a size reduction from anywhere between ~30% to ~60% compared to the original files. The conversion is lossless and reversible. As chd's use streaming decompression (the data requested by the emulator is decompressed on the fly), no decompression before starting a game is needed like with .zip or .7z. Although PCSX2 already supported other compression formats like .cso (lossy compression) and .gz, chd's don't require the creation of an indexing file upon first boot and with chd the compression ratio is slightly better. If you have already compressed your collection to .cso or .gz converting to chd probably isn't worth it, but if your still using iso's and bin/cue's compressing to chd has some advantages. To convert your PlayStation 2 iso's and bin/cue's to chd create a bat file with: for /r %%i in (*.cue, *.iso) do chdman createcd -i "%%i" -o "%%~ni.chd Copy the bat file and chdman.exe (found in your Mame installation folder - but is probably a good idea to download the latest version of Mame and get it from there) to your root PlayStation 2 games folder. Start the bat file and chdman automatically creates all the chd's in your root PlayStation 2 games folder, even if you keep all your games in subfolders. A warning though. Converting your games to chd's can take a very long time depending on the size of your collection and your cpu. *Edit* I forgot to mention. To use chd's with PCSX2, you must use the latest development build of PCSX2. Download here: https://pcsx2.net/download/development/dev-windows.html
  4. Hi all, I'm trying to get flycast running through launchbox for Dreamcast games, but I'm really struggling with this at the moment and could use a few tips and pointers. I'm using CHD's for the games and they work without a hitch in retroarch on their own. The collection of games has been imported into Launchbox successfully with all the cover art and details etc. I've associated the flycast core with the Dreamcast section, but when I try to run any of the games, nothing happens, it doesn't even load retroarch at all. I have all the correct bios's in place, so it must be something to do with either file structure, filename or a launch command that I need to include. I'm guessing creating a batch file, could be a last resort to solve this. Can anyone help at all?
  5. Brand new to this! I just cleaned up a spare laptop and downloaded MAME along with LaunchBox. I downloaded a few games like Mortal Kombat and Killer Instinct (along with associated chd files) from the Internet Archive. The games work in MAME and show in Launchbox which is great. I'd like to download what I believe is called a "ROM set" where there are thousands of arcade games and not just download one at a time like I did. I've searched and read a lot, but I can't seem to find a place to actually download something like this. Can someoone point me in the right direction? I also hear things like merged vs. split, but again, I can't seem to find a download for one or the other. I'd like to download a large set and if I'm missing any games I want, then I can download individually and add them. HOw do I do that?
  6. I'm having an odd issue with Launchbox. In general had no problems but this specific game (Chaos Heat) will not work in Launchbox no matter what. It works without a problem in MAME when the application is used directly, but when the CHD (this is a CHD-only game) is imported to Launchbox, a couple of key things go wrong. First, the metadata does not get properly configured. The game is in LaunchBoxDB, but it is not recognized as a valid game and the name does not even set properly (screenshots below). I can manually go in and set the name and import the metadata after the fact, but this does not fix the second, primary issue. The game will not launch through Launchbox no matter what I do. This cannot be overstated, no matter what settings I play with I cannot get this game to work. I have several other CHD-only games that all function in Launchbox without a problem and there is virtually nothing I can find that is unique about this game's case to point to in this case. I have other games on Taito's G-NET System that all work and are running identical configurations (and in fact Super Puzzle Bobble is a G-NET game that also CHD-Only, and this game works without issue!). I am drawing blanks here and pulling my hair out over this game, so I wanted to post over here and see if anyone has any idea. I will include a detailed walkthrough of my setup below so you all can get an idea of what I am running to (hopefully) spot something that can help. First, the configuration of the specific MAME build I am using for G-NET games (Chaos Heat included): I use this config setup for all of my MAME games in general, and have had no issue before. Here is the listing in the import wizard. Usually it would list the game properly, such as listing "Chaos Heat" instead of rom name "chaosheat". This is the first oddity I notice when importing. When I click "Finish" and let it import, here's what the finished product has for metadata (nothing): A few oddities here. First, it does list that it is grabbing the images when importing, but goes way too fast and doesn't show any when finished. Also, you can see it does link to the correct LaunchboxDB item, but as shown it doesn't correctly grab the name for some reason? The metadata is at least there for this game, as inaccurate as it is. Once I manually import the pictures, the next thing is to try to play the game. When I try to do this Launchbox does the same thing that it would do if a game was missing a rom file or something similar: it displays the loading screen and then immediately quits back to the game list. No error messages or anything. Problem is, there are no errors for me to troubleshoot in this case since the game functions completely fine when I launch it directly through MAME, and it plays without any issue! This is a great game and it pains me that it is being so troublesome to set up. If anyone has anything they can suggest to try or at least if anyone can verify that the game works fine for them it would be greatly appreciated! Feel free to let me know if anyone needs more information on this and I would be happy to help, I just want my Chaos Heat! ? Here's a screenshot showing the game is indeed working for me through MAME directly:
  7. Full sets take up a lot of space. I have that space, but that doesn't mean I want to use any more than I have to. Additionally, importing folders full of bin/cue/wav/etc for certain disc rips is messy. In a perfect world, every game would be compressed and stored in a single file. It seems most systems have at least one option, but with so many emulators and so many compression formats, it's been tricky figuring out what that option is. So far I've determined the following system - emulator - compression combos: PSP - PPSSPP - CSO Playstation 1 - Beetle PSX - CHD Playstation 2 - PCSX2 - GZ Gamecube/Wii - Dolphin - GCZ Dreamcast - DEmul - CHD Are these the best combos for these systems? What about other disc-based systems - Amiga CD32, Sega CD, etc? Thanks.
  8. Hi all, I have gathered a full set of US PSX games plus not a few PAL ones as well so my aim here is to save some space. After weeks of playing around and reading I have come up with different ways of combining games with multiple bins (normally audio tracks) into one, which is pretty straightforward to be honest. After this I tend to convert them into PBP files but since it is painfully taking a lifetime to convert every single game one by one I am seriously considering batch converting them to CHD. (I was using ePSXe first and now RA Mednafen HW). Everything is OK until this point BUT I have realised after combining bin files some games, they lose audio tracks and while playing I can hear, for instance, the sound effects but not the music. This has happened to me recently with Wipeout 3. My ideal world is to be able to: 1) Combine every single game to has just one cue/bin without losing any audio information and prepare them to 2) Batch conversion to CHD. This also without losing any kind of information from the prior cue/bin. Nor data or audio wise. My methods of combining bin files are: Daemon Tools Lite + Img Burn: mounting the .cue with Daemon in a virtual drive and creating and image from disc with the latter software. UltraIso: opening the .cue or main .bin and converting the game (again) into cue/bin. I am keen on suggestions of every kind or if you have a different workflow/pipeline for achieving this. Many thanks if you read this! This is driving me crazy.
  9. I am not a Noob really, but a Noob when it comes to CHD files. I keep my CHD's separate from my ROM's. I have a full set of .182 of both. I have watched the tutorials, and searched these forums. 1. Does every CHD have a corresponding ROM? 2. How do I add the CHD's to LaunchBox? When I point the importer to the location with all of the CHD's it doesn't seem to get all of the entries. I must be doing it wrong. Thanks for any help
  10. I am having trouble running mame games like Killer Instinct , the mortal kombat serie , Street fighter 3rd strike , sunset riders , all games with chd actually , I have the chd and the rom files because they run perfect outside launchbox . And as far as i know , i correctly entered the rom path. Any suggestions because i have been struggling for over three days now.
×
×
  • Create New...