Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'cache'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LaunchBox
    • Android
    • Beta Testing
    • Collections and Builds
    • Features
    • Troubleshooting
    • Website/Forum Support
    • Noobs
    • News and Updates
  • User-Created Content and Downloads
    • Big Box Custom Themes
    • Big Box Sound Packs
    • Big Box Startup Videos
    • Custom Theme Tutorials
    • Game Media
    • LaunchBox 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
    • Legacy Themes
  • LaunchBox Custom Themes
  • Startup Themes
  • Pause Themes
  • Big Box Startup Videos
  • Big Box Sound Packs
  • Third-party Apps and Plugins
  • Game Media
    • Game Theme Videos
    • Game Media Packs
    • Game Marquee Images
    • Game Clear Logos
    • Game Box Art
    • Game Cart Images
    • Arcade Cabinets
  • Platform Media
    • Platform Theme Videos
    • Platform Console Images
    • Platform Backgrounds
    • Platform Banners
    • Platform Clear Logos
    • Platform Bezels/Overlays
  • Playlists & Playlist Media
    • Playlists
    • Playlist Theme Videos
    • Playlist Backgrounds
    • Playlist Banners
    • Playlist Clear Logos
  • LaunchBox/Big Box Media

Blogs

  • Jason's Devotions
  • Thatmans Blog
  • THAT NINTENDO SWITCH EARLY REVEAL WAS FROM A STOLEN CONSOLE
  • Version 8.8

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 4 results

  1. Archive Cache Manager View File A tool which manages a cache of recently extracted game archives for quick loading. Also allows per emulator file extension priority for files within an archive. Description When an archived game (in zip, 7z, or other compression format) is extracted and played, it is stored in the archive cache. The next time the game is played, the data is loaded directly from the cache, eliminating the extraction wait time. As the cache approaches its maximum size, the least recently played games are deleted from the cache, making room for new games. Features Configurable cache size and location. Configurable minimum archive size, so small archives aren't cached. File extension priorities per emulator and platform (cue, bin, iso, etc). Some combinations of emulators and file extensions don't work with LaunchBox's built-in priority. Cache cleanup using either least recently played games or least played games. Optional loading screen while an archive is being extracted. Installation / Update Extract the archive to your LaunchBox folder, which will create an ArchiveCacheManager sub-folder. Navigate to the new ArchiveCacheManager folder and run Install.bat. Within LaunchBox, ensure the desired emulator has the "Extract ROM archives before running option" checked. Uninstallation Navigate to the LaunchBox\ArchiveCacheManager folder and run Uninstall.bat. Delete the ArchiveCacheManager folder. NOTE: The archive cache is not removed on uninstallation, but can be manually deleted. Configuration The first time a game is extracted using Archive Cache Manager, a configuration file called Config.xml is created in LaunchBox\ArchiveCacheManager. Modify this file using Notepad or similar to make any configuration changes. An overview of each of the configuration items is below. <MaxCacheSize> This is the maximum size on disk (in megabytes) that the cache is allowed to grow to before cached items are deleted. The default is 20000MB, or 20GB. <MinArchiveSize> This is the minimum size (in megabytes) an uncompressed archive needs to be before it is added to the cache. The default is 50MB. <CachePath> This is the path of the cache folder. The path can be absolute or relative, where relative paths are to the LaunchBox\ArchiveCacheManager folder. The default is Cache. <UsePlaycountWhenClearingCache> Items can be removed from the cache based on the least recent playtime, or the least played games. Set this to True to delete the least played games from the cache. Default is False (delete the oldest game from the archive). <ShowLoadingScreen> Shows a simple loading screen while the game is being extracted. Note that this setting does not affect BigBox, for which the loading screen is never shown. Default is True. <VerboseLogging> Archive Cache Manager has extensive logging to aid in debugging, but this can also slow down the cache management due to the extra disk I/O. The default log behaviour is to now only log exceptions and other important events. Extended debug/verbose logging can be re-enabled with this setting. Default is False. <ForceHardLinks> The default Archive Cache Manager behaviour is to use the direct path to an archive in the archive cache. This eliminates the need for the previously used method of hardlinks and directory junctions linking the archive cache to LaunchBox's temp folder. This option forces the use of hardlinks/junctions. Default is False. <ForceFileCopy> This option overrides both the direct path and hardlink/junction behaviour described above. With this option enabled, a direct file copy will be made from the archive cache to the LaunchBox temp folder. Use this option if there are problems with the other two methods. Default is False. <FilePriority> This defines the file extension priority for the specified emulator (and optionally platform). The emulator name in the <Emulator> tag must match the emulator name set in LaunchBox. An optional <Platform> tag can be used for individual platform file extension priorities in a multi-system emulator (e.g. Retroarch). The file extensions in the <Extensions> tag are a comma separated list. Duplicate the entire <FilePriority> block to add new emulator (and platform) extension priorities. In the example below, the Retroarch file priorities will only be applied to games belonging to either the 3DO or TurboGrafx-CD platforms. Games belonging to another platform started with Retroarch will not have a priority applied. <FilePriority> <Emulator>PCSX2</Emulator> <Extensions>iso, bin</Extensions> </FilePriority> <FilePriority> <Emulator>Retroarch</Emulator> <Platform>3DO Interactive Multiplayer</Platform> <Extensions>iso</Extensions> </FilePriority> <FilePriority> <Emulator>Retroarch</Emulator> <Platform>NEC TurboGrafx-CD</Platform> <Extensions>cue</Extensions> </FilePriority> Known Issues Loading screen game title is filename when game started as additional app Cover art display doesn't yet use LaunchBox's image loading priority Submitter fraganator Submitted 01/03/2017 Category Third-party Apps and Plugins  
  2. Just thought I would give people a little tutorial here on how to use "mklink" to create a Symbolic Link for the Launchbox Cache. Some people say it improves performance (I certainly noticed it) and some say they don't notice much of a difference, I guess it depends on your set up. This method worked for me very well when I moved the Cache to my SSD, I found that I could now use images set to there highest quality without any impact on performance and the images look great on a 4k TV. So here is what worked for me: 1. First download and install LINK SHELL EXTENSION found here http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html (be sure to install the dependency's first)You should now have the option when you right click on a file to "Pick Link Source". 2. On your SSD where you want your CACHE to be located create a folder called "CACHE" (I find that creating a Folder named something like "Launchbox Cache" and then placing the new Cache folder inside it works best). 3. Go to your Launchbox folder and find the original CACHE folder in the IMAGES folder and copy everything in the CACHE folder to your new CACHE folder on your SSD. (this may take a while, alternatively you could just delete everything in the original cache folder if you wish but you will have to repopulate it later after the folder is linked, not a big deal really I just leave launchbox in "attract mode" so the Cache gets filled up). 4. Once you have copied everything (or deleted everything) from the original CACHE folder also delete the actual ORIGINAL CACHE folder itself as well (this part is important). 5. now go to your SSD and right click your new CACHE folder (or the folder it's in) you created earlier and select "Pick Link Source" 6. now go to your IMAGES folder in launchbox right click it and select "Drop as Junction" This will automatically create a new CACHE folder (where you deleted the original) INSIDE the IMAGES folder with a little chain icon attached to it indicating that it is now linked to your SSD CACHE folder! That's it simple but took me a while to get my head around so I just thought I would post this. A way to test if this is working correctly is to do the same with your platform videos folder, if after following the instructions above your videos display properly, everything is working fine! or of course you could just watch the space left on your SSD as the cache fills up.
  3. Version 1.5

    192 downloads

    A tool which manages a cache of recently extracted game archives for quick loading. Also allows per emulator file extension priority for files within an archive. Description When an archived game (in zip, 7z, or other compression format) is extracted and played, it is stored in the archive cache. The next time the game is played, the data is loaded directly from the cache, eliminating the extraction wait time. As the cache approaches its maximum size, the least recently played games are deleted from the cache, making room for new games. Features Configurable cache size and location. Configurable minimum archive size, so small archives aren't cached. File extension priorities per emulator and platform (cue, bin, iso, etc). Some combinations of emulators and file extensions don't work with LaunchBox's built-in priority. Cache cleanup using either least recently played games or least played games. Optional loading screen while an archive is being extracted. Installation / Update Extract the archive to your LaunchBox folder, which will create an ArchiveCacheManager sub-folder. Navigate to the new ArchiveCacheManager folder and run Install.bat. Within LaunchBox, ensure the desired emulator has the "Extract ROM archives before running option" checked. Uninstallation Navigate to the LaunchBox\ArchiveCacheManager folder and run Uninstall.bat. Delete the ArchiveCacheManager folder. NOTE: The archive cache is not removed on uninstallation, but can be manually deleted. Configuration The first time a game is extracted using Archive Cache Manager, a configuration file called Config.xml is created in LaunchBox\ArchiveCacheManager. Modify this file using Notepad or similar to make any configuration changes. An overview of each of the configuration items is below. <MaxCacheSize> This is the maximum size on disk (in megabytes) that the cache is allowed to grow to before cached items are deleted. The default is 20000MB, or 20GB. <MinArchiveSize> This is the minimum size (in megabytes) an uncompressed archive needs to be before it is added to the cache. The default is 50MB. <CachePath> This is the path of the cache folder. The path can be absolute or relative, where relative paths are to the LaunchBox\ArchiveCacheManager folder. The default is Cache. <UsePlaycountWhenClearingCache> Items can be removed from the cache based on the least recent playtime, or the least played games. Set this to True to delete the least played games from the cache. Default is False (delete the oldest game from the archive). <ShowLoadingScreen> Shows a simple loading screen while the game is being extracted. Note that this setting does not affect BigBox, for which the loading screen is never shown. Default is True. <VerboseLogging> Archive Cache Manager has extensive logging to aid in debugging, but this can also slow down the cache management due to the extra disk I/O. The default log behaviour is to now only log exceptions and other important events. Extended debug/verbose logging can be re-enabled with this setting. Default is False. <ForceHardLinks> The default Archive Cache Manager behaviour is to use the direct path to an archive in the archive cache. This eliminates the need for the previously used method of hardlinks and directory junctions linking the archive cache to LaunchBox's temp folder. This option forces the use of hardlinks/junctions. Default is False. <ForceFileCopy> This option overrides both the direct path and hardlink/junction behaviour described above. With this option enabled, a direct file copy will be made from the archive cache to the LaunchBox temp folder. Use this option if there are problems with the other two methods. Default is False. <FilePriority> This defines the file extension priority for the specified emulator (and optionally platform). The emulator name in the <Emulator> tag must match the emulator name set in LaunchBox. An optional <Platform> tag can be used for individual platform file extension priorities in a multi-system emulator (e.g. Retroarch). The file extensions in the <Extensions> tag are a comma separated list. Duplicate the entire <FilePriority> block to add new emulator (and platform) extension priorities. In the example below, the Retroarch file priorities will only be applied to games belonging to either the 3DO or TurboGrafx-CD platforms. Games belonging to another platform started with Retroarch will not have a priority applied. <FilePriority> <Emulator>PCSX2</Emulator> <Extensions>iso, bin</Extensions> </FilePriority> <FilePriority> <Emulator>Retroarch</Emulator> <Platform>3DO Interactive Multiplayer</Platform> <Extensions>iso</Extensions> </FilePriority> <FilePriority> <Emulator>Retroarch</Emulator> <Platform>NEC TurboGrafx-CD</Platform> <Extensions>cue</Extensions> </FilePriority> Known Issues Loading screen game title is filename when game started as additional app Cover art display doesn't yet use LaunchBox's image loading priority
  4. Back again with another issue. BigBox had been working great for me lately and I have now realized it was because I had not updated it in a while due to there having been no new Betas for a while. A new Beta was released yesterday and as soon as I updated all cover flow images had to load again and if I go to the "Force Populate" option in the menu it starts from scratch where before the update it was it was showing a quick green loading screen since everything was populated. I realize now this has been a major problem for me for a long time so Is this a known issue? it would suck if I had to constantly repopulate after every update as I have a massive library and I have to leave BigBox populating over night.....
×
×
  • Create New...