Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    4,352
  • Joined

  • Last visited

  • Days Won

    34

Everything posted by JoeViking245

  1. Support for pre-configured drives will not be given here.
  2. I see. You might want to submit a feature request. (A top this page - Help & Support < Request a Feature)
  3. Well, they kind of already do. It's just called something a little different. Skip games unplayable in MAME. Take for example Daytona USA 2: Battle on the Edge (daytona2). That games overall status is Preliminary. But you will never be able to play it in MAME. Supermodel3 emulator, yeah. But not MAME.
  4. Different forks process the ROMs (and emulate) differently. So maybe they do seem to work better in them, or they're not as particular as the Official branch of MAME (which is what LaunchBox defers to). The good news is ROMs that, for whatever reason don't import, you can easily drag and drop those "just a couple" of ROMs right onto LaunchBox and import them that way.
  5. Did you try checking Use All Attached Controllers? Something in the back of head says 'restart LaunchBox after enabling the controllers'. (or was it after doing something else? Regardless, worth trying that as well.)
  6. LaunchBox's basis for what's considered playable/un-playable comes direct from MAMEs Overall status. Not any of the subsets (emulation, graphics, color etc.). If it's red (i.e. kov and kovplus), it doesn't get imported (unless of course certain filters are un-checked). If it's yellow (i.e. kov2p) or green (i.e. kov2nl), it will get imported.
  7. We'll assume it's Xinput then. So you'll want to set up the "game controllers". "Is there a way to get my joysticks to be recognized in BigBox/LaunchBox?" LaunchBox: Tools < Options < Game Controllers Check Enable Game Controllers Then choose a device from the pulldown If you have just one encoder, you should be fine Otherwise, you may need to check Use All Attached Controllers Now go to Mappings Set your Move Mouse and Navigate Up/Down/Left/Right accordingly ...and any others to your liking Scroll down and set Exit Game Note that LaunchBox (at least for me) works better with a regular mouse [and keyboard] BigBox: System Menu < Options < Controller Turn on Enable Game Controllers Now go to Controller Mappings and set the items to your liking For now, you may want to keep the default ones that are set to {None}. Leave those extracurriculars for a 'rainy day'. Do scroll down the list and set Close the Active Window. This is also known as 'Exit the Game'. Note: Exit is to close (aka shutdown) BigBox. My advice is to leave it as {None} (or clear it if it's set to something). If you're still exploring how you want BigBox to look, you might also want to set Switch View and Switch Theme. These will of course change the current Theme's View or change the currently selected Theme. (Makes for handy shortcuts) Both of these can have their items set to a Joy movement, Button press or Button-combo press.
  8. Open Notepad. Move Joy 2 (or 3 or 4) around and see if any letters are "typed". If there are, then it's in Keyboard mode. And if so, you can then move Joy 1 'Left' to move the cursor left.
  9. Are your joysticks/buttons set by the encoder as Xinput (Controller Bindings) or Keyboard (Keyboard Bindings)? Note: Bindings are set separately in LaunchBox and BigBox, respectively. As much as love the joys and buttons on my cab, though possible to set them up on the cab inside these emulators (some not so easily. Others may not be available to do so), I use an Xbox controller for those. (1) It's more natural when playing. (2) It's way easier to set up. (my 2-cents )
  10. Some Fruit games (aka slots) are also included in with Casino games. So if you un-checked Fruit Games, you'll get (some) slots even though Casino Games was checked. A quick search on the Arcade Database (not to be confused with the LaunchBox database) shows 8 variants of Black Hole. Some of which are for pinball machines, so we can throw those out. But of the remaining, only 1 is considered playable (blkhole). The rest are all marked as Not Working. Did you leave Skip games unplayable in MAME checked? On my test, both of these were imported. For this example, are you referring to your subsequent media scraping issue? Your topic referred to games being skipped when importing. Is your issue/concern more-so towards Arcade/MAME games scraping the wrong media? Sticking to the original topic, games skipped when using the MAME Arcade Import Wizard are wholly dependent on the filters that were checked/un-checked. If you leave Skip games unplayable in MAME checked, games that are marked (by MAME) as Preliminary (and a few other potential criterium) will be skipped. You may be able to "play" a Preliminary game in MAME. But their emulation is just 'not up to snuff'. If you check Skip Clones Entirely, if the parent game is unplayable but a clone of that game is playable, it won't import. Note: Prioritizing Regions and/or Variant may take precedence over this. If you need confirmation on that, let us know. There's also the potential issue of same game, different titles. If you're missing Thunder Zone, look for Desert Assault. To be able to work towards resolving the issue of some games not being imported, we need to know who the offenders are and also the filter selections you used.
  11. There are several possible factors involved here. The main one being the filters you may have left checked during the Arcade Import Wizard. Got anything specific that was skipped? No.
  12. I can't answer the syncing issue. But as for image/video file naming conventions, LaunchBox looks for file(s) that either: Have the same name as the games Title Have the same name as the games ROM The suffix (i.e. _01) to the name is not required. But is helpful if you have more than on media of that type for that game. Mostly useful with i.e. Screenshot-Gameplay images. There are some caveats with using Game Title that pertain to Invalid Characters. The 2 common ones you come across are ' (apostrophe [single quote]) and : (colon). Those get replaced with _ (underscore). i.e. an image for Joe's Game: Volume One would become Joe_s Game_ Volume One.png (or Joe_s Game_ Volume One_01.png) The nice thing about images and videos, if you manually copy them into their respective folder(s) and they meet the criteria of one of the 2 bullets above, and account for the invalid characters (as necessary), there's no other associating needing to be done. For Images you'll probably want to (need to) Refresh the image cache. LaunchBox: View < Media < Refresh All Images. Since they're all new images... you can press Ctrl+Shift+M to Refresh the media that was missing (is newly added). BigBox: System Menu < Options < Image Cache - Refresh All.
  13. As you'll have seen in the video, that line was placed in PlatformFiltersDetailsView.xaml. It's the 4th line of text up from the bottom. Open the file in any text editor and change the wording.
  14. Aw snap! That what happens when I try to clean up my working code. 😊 I'll fix that post for future readers. Glad it all worked as intended. Sorry the outcome wasn't as hoped. 👍 👍
  15. Fear not. If you can get the paths and executables, it will. 😎 (I actually tested this one before posting. Something I'm trying to get better at actually doing. lol)
  16. No need to. Just create the batch file and use it to start LaunchBox. It'll do it all for you. A one-shop-stop, as it were. (You could even to change the icon for the shortcut to use the one in LaunchBox.exe. )
  17. If, when you disable G-Drive syncing and you're happy with how LaunchBox/BigBox performs via G-Drive (which I guess at this point is actually running from your local G-Drive folder), then... A variation of a Google search result looks like this: This link mentions "googledrivesync.exe" which is now "GoogleDriveFS.exe" (at least on my PC). It seems there's no command-line parameters you can pass to the executable to turn G-Drive syncing on/off. So you have to "kill" the process. From the Windows Command Prompt, to kill G-Drive altogether, you can run taskkill /IM GoogleDriveFS.exe /F Then to restart it, double click "GoogleDriveFS.exe". Mine's located in "C:\Program Files\Google\Drive File Stream\100.0.2.0\" LaunchBox/BigBox has a Startup Applications feature that can load an application when one or the other or both (or neither?) are started. (Which could be a batch file containing the above command.) But there are no (immediately accessible) means to launch an app when either close. "Immediately accessible" meaning, you could create a plugin that captures the System Event LaunchBoxShutdownBeginning and/or BigBoxShutdownBeginning and then (re)start the process "GoogleDriveFS.exe". Alternately, you could create/use a batch file that handles the whole kit-and-caboodle. Something like this (edit accordingly) taskkill /F /IM GoogleDriveFS.exe timeout 5 start /w "" "D:\LaunchBox\Core\LaunchBox.exe" start "" "C:\Program Files\Google\Drive File Stream\100.0.2.0\GoogleDriveFS.exe" Do This: Verify YOUR Google Drive executable is indeed "GoogleDriveFS.exe" Change the path to YOUR LaunchBox location DO point to the /LaunchBox/Core subfolder Change LaunchBox.exe to BigBox.exe if that is your preference Verify that is the path to YOUR "GoogleDriveFS.exe" If all's good/tested/working, make for a 'prettier' presentation... Create a shortcut to the batch file Right-click the shortcut and select Properties Change Run from Normal Window to Minimized Click OK to save and close. Use the shortcut to start the "whole kit-and-caboodle". The above makes it so the Command Prompt window does not appear.
  18. This would be located in your Windows "Display Settings" under "Scale and layout".
  19. Take a look at this and see if it helps.
  20. The only times I've seen this happen is when I launch the game, and it's the 1st time Steam has been launched (on that particular day), and Steam has an update. Steam will do its update thing and then show the "On Sale" and 'Main' windows. This happens in the background, so you don't see anything when the game [eventually] starts, and you play it. It's when you exit the game you see those windows still lurking [on top of BigBox]. I've gotten in the habit of, before I start BigBox, if I know I'm going to be playing a Steam game, I'll Start Steam 1st. Let it do its thing close/minimize Steam when it's done then start BigBox.
  21. Interesting that it works. Because that's exactly how the plugin does it (but in code-lingo. Not batch file lingo). Glad you got it sorted.
  22. Note in the .cue file, it gives reference to all the other flies in that folder. The .iso file and the 2 .wav files. This confirms for me that you need to send to chdman the .cue file. It will look in that (.cue) file and process all the files listed. My guess is that your batch file converted the iso file ONLY. The giveaway is it says "ISO to CHD.bat". The line in the batch file probably starts with something like for /r %%i in (*.iso) which tells you, it's ONLY looking for the .iso file. The iso doesn't know to look for the wave files. Whereas if you found a batch file that was maybe called "CUE to CHD.bat", it would have *.cue instead of *.iso in there. Processing the .cue file (hence all the files it references) would make the resulting .chd a lot larger than 4,360 KB. It is possible. Look for a file called "CUE toCHD.bat". Another option is to use this plugin and select the option cue to chd.
  23. That's what we like to hear and see! 😎
  24. Perfect! When you launch a game from LaunchBox that has the varying file types in them, which is the file the ROM path points to? And (just as important), doe that game then run correctly? Can you also share a screenshot of a game [folder] that 'have ISO CUE and some WAV files in the same folder'? And then what is the contents of the [single, because there should only be one] .cue file? (you can open it with any text editor) The contents should list which files are needed to make up the game. That's what chdman parses to create the chd file. You can try it manually if you'd prefer. "path/to/chdman.exe" createcd -i "your file.cue" -o "yourNewGame.chd" If you don't have a lot of games to convert, it may be easier to simply do it manually. Just don't delete any of the cue/iso/wav files until you've tested the chd. That would be a topic for another/new thread.
  25. It only looks at the [single] file that the games application path (ROM path) is pointing to. The plugin does not per se, auto detect your existing file formats. As deduced by step 4 (above) "Select the file format you’re converting from". If you select iso to chd, it will scan the selected platform ONLY for games that have a .iso file extension. Same with .cue and .gdi. And then convert them. Respectively. As I said in the other post, I don't know .wav is. And I don't emulate that system. However, a quick search indicates those (.wav) are used in conjunction with the .cue file. Which is what you would have imported into LaunchBox and what the plugin will look for. The question I think you need to find the answer to (if you haven't already) is, does the emulator(s) you'll be using support .chd files?
×
×
  • Create New...