-
Posts
44 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by drtechnolust
-
The path was specified in the mame.ini. For some odd reason lightspeed was not creating roms paths for over 5000+ files in a 12000 rom pack. I went back to mameui64 set the rom path again to double check loaded a chd based rom and that worked. Then I used the launchbox rom importer and did a file import of each 7z file. I tested after the import and the games load successfully. Thankyou @DOS76.
-
@Jason Carr After doing some testing with a clean install of Launchbox and using my data folder it seems the bottle neck is with the parsing of Platforms.xml file at startup. Wouldn't there be a performance gain for large data structured libraries such as mine (25000+ games and 60+ platforms) to use an ini system since it maybe faster to parse. Non edited stock Platforms.xml - Launchbox startup time 4 seconds. Edited Platforms.xml - Launchbox startup time 1 minute 25 seconds Thanks for all your hard work! Platforms.xml
-
I'm having trouble getting mame roms with chds to launch. I've tried lightspeed but I get an error with lightspeed that "rom cannot be found" I've tried with launchbox importer with an error that it's looking in the rom.7z for the chd folder. Rom Folder Structure: Mame > Games > rom.7z CHD Folder Structure: Mame > Games > "Foldername of CHD" > example.chd
-
-
Which XML and code to modify the games screen text, font, color, and background opaqueness for the game data. I also increased the size of the platform wheel art to because I thought it was a little too small. I add a curve to the wheel on the game screen and would like to increase the size of the clear wheel art a bit. @CriticalCid I love your theme great job!!
-
@Jason Carr I would have to agree with Camelspit on this one. I'm migrating over a 8tb drive from hyperspin to launchbox and the performance should be priority before more features are added. I don't think the issue is with my pc since it is a highend pc. 1. Big Box startup time should be less than 10 seconds to start. 2. Importing roms is taking a lot of time out of actually tinkering with the software to customize the build. What is actually being done during the importing of roms. Is it just building the database xml file and creating the folder tree for the platform? I ask because even if I just go through the process to import the roms without the options to download any media or metadata the process is still lengthy. AMD 8350 overclocked - Sapphire 8GB RX480 OC Nitro - Samsung Pro SSD 250GB (Launchbox) - 2 HGST 4TB (Game Drive) - 16GB G.Skill ripjawz 1866Mhz
-
This is a great feature or even an option to choose starting platform\wheel in Big Box.
-
This happens when I click on a platform to open the games menu. After switching from CriticalZonev1.1 to CleanBG I received the following error. This error does not occur if I go back to CriticalZonev1.1 without changing any other features in options. I thought with the new beta by switching themes it will inherit features that need to be turned off or on automatically. An error occurred while parsing the custom TextGamesView. The default view is shown instead. Details on the error are below: An error occurred while parsing the custom GameDetailsView. The default view is shown instead. Details on the error are below: Version 7.0-beta-5
-
Import feature fails to identify metadata from TheGamesDB.net
drtechnolust replied to Specular's topic in Troubleshooting
To fix this error I followed the video below, which is just setting up the monitor resolution etc. Time 5:10 - 6:20 -
System.IO.IOException: The process cannot access the file 'I:\LaunchBox\LaunchBox\Themes\Documentation.pdf' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.File.InternalWriteAllBytes(String path, Byte[] bytes, Boolean checkHost) at Unbroken.LaunchBox.Wpf.BigBox.App..ctor() at () at Unbroken.LaunchBox.Wpf.BigBox.App.Main() Share violation if Documentation.pdf is open and you launch Big Box at the same time.
-
Sentai thanks... I checked the Platform a few hours ago but when I went back it was showing a blank platform with 1 game. After deleting that, it resolved the issue. Thanks!!!!!!
-
Can anyone tell me what the name of this missing platform image so I can fix it? It's just showing recent games or something...
-
Is the beta testing closed? I've selected the option to receive beta updates via LaunchBox, restarted the application several times and still I have no updates available. I'm on version 6.12 at the moment.
-
Is there a third party tool that I can use to download the links all at once. I've tried IDM and several google extensions but the they don't work since the page is in a frame so the apps can't grab the links...
-
Is there a way to have a download all button? It's too tedious to keep clicking on links. Example if I click the "download file" button it opens up another dialogue with several download buttons for each individual file.
-
1. The clear logo wheel art is not changing even after clearing the cache. I tried using the Minimal HD, ClearBG, and Metal theme. I tested with putting the Arcade image in both of the following folders. I'm using the ClearLogo_Silver_Ring_v1.7 pack. I:\LaunchBox\LaunchBox\Images\Arcade\Clear Logo I:\LaunchBox\LaunchBox\Themes\Metallic\Images\Platforms\Clear Logo 2. Is it typical for Big Box to take 1+ minutes to open? 3. Is it typical for Big Box to take 1+ minute to switch back after pressing the back button? CPU: AMD 8350 GPU: RX 480 Memory: 16 GB HD: 2TB 7200 WD drive