Allow customizing image cache paths in order to help with running LaunchBox over a network

[maks]

Issue discussed here... https://www.launchbox-app.com/forum/troubleshooting/launchbox-very-slow-over-nas

Steps: 1. Install and setup Launchbox to Network Attached Storage (ex. QNAP, Synology, etc) 2. Map Network Drive of your Launchbox install to any computer 3. In your Antivirus, whitelist your Launchbox install location 4. Setup any system, allow art to cache 5. Attempt to navigate Launchbox UI, launch games, etc.

Results: Launchbox response is very slow when installed to a network device. It can take 5 seconds to move to each game, each artwork piece takes around 3 seconds to load, and launching a rom such as NES can take at least 20 seconds.

Tested on: -QNAP TS-251+ (NAS) -PC #1 Alienware Alpha i3, SSD, 8gb ram (Win8.1) -PC #2 Asus Maximus V i5 2500k, 16gb ram (Win10) -All devices are connected via Gigabit ethernet

Note: My Hyperspin setup works fine in this situation. About 4 seconds to launch HS, navigating UI is nearly instant, and launching games such as NES roms occur in 1 second.

[Jason Carr]

Thank you maks, this is mostly due to LaunchBox using the LaunchBox folder for image caching. I think if we allowed people to specify a local path to use for image caching, then this would improve. I still don't recommend running LaunchBox over a network path, because performance will not be ideal in that scenario no matter what we do. Using a syncing solution like Dropbox is a much better solution for this stuff. We'll leave this open though so we can add those options.