Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    5,345
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by JoeViking245

  1. Most likely when you ran the installer, it got installed into your existing LaunchBox folder. e.g. D:\LaunchBox\LaunchBox\. When you manually install an update (or reinstall), it's important to select the correct folder. DO NOT select the existing LaunchBox folder directly. Instead, choose the root folder where LaunchBox is located. In my example above, you'd select D:\. On the last screen of the install app, before clicking Install, verify the path it shows LaunchBox will be installed to. When selecting the D-drive, the last screen will show D:\LaunchBox\.
  2. The free version doesn't offer updates. Your 1-year license expired sometime after January 27th and before February 9th of this year. You have a lifetime license and that version is causing a glitch-in-the-Matrix. Try Menu - Help - Check for Updates
  3. Looking at their github site, you use --game as the parameter. "The emulator can also be started directly with a legally obtained game directory or ELF file:" kyty_emulator.exe --game "D:\Games\ExampleGame" From the Windows Command Prompt, you can get a list of available parameters by executing kyty_emulator.exe --help As for getting the games imported into LaunchBox, that may be a different story. I don't think you can add a "folder". So may be easiest to import the respective ELF files.
  4. I was under the impression that in Arcade, clone ROMs (10yard85.zip) were considered the same game as their parent ROMs (10yard-zip). In this example "10-Yard Fight '85" is listed as an alternative name to "10-Yard Fight" [since it's the "same game"]. However, in the LB Games Database "Vs 10-Yard Fight" (vs10yard.zip), another clone of 10yard.zip has its own separate listing. But even though it has its own db ID#, the description is the same as "10-Yeard Fight" as are most of the images. But it is missing most of its metadata. So a couple quirks, I suppose. Inconsistency in how clones with different titles than their parents are separated out. And incomplete metadata for the separated out clones. Personally, I think they should be lumped together and listed as alternate names. But then again, I don't have any involvement with the inner workings of the LB Games DB ( not do I want to. )
  5. No idea on this one. Hopefully someone else can chime in on it. When you edit an individual game and go to download images, this is what you'll get. Alternately, you can select the [single] game and go to Tools < Download < Update Metadata and Media for selected Game... and have the option to set the limit per image type. Neither option will let you select e.g. which of the 2 available Arcade Cabinets to download. If you're doing just one or a couple (or several), there's a plugin that will let you view and select exactly what and which images to download. LaunchBox Games Database Image Viewer-Plus And of course, there's always room for Feature Requests.
  6. To clarify, you opted into the betas, restarted LaunchBox, it said there was 'a new beta release available, would you like to install it?', and you selected "yes"? Is your LaunchBox install location on a local HDD/SSD? Is the folder somewhere such that it gets backed up to something like OneDrive, Dropbox or some other service? The 2nd message seems to contradict the 1st message. Like, it can't run the installer file that it is "unable to download". Does the /Updates/ folder contain the "LaunchBox-13.28-beta-6-Setup.exe"?
  7. That may very well be, I don't know. But using the Fuse standalone emulator is different than using the fuse_libretro core inside RetroArch. Per the document I linked above, using the core in RA does require the [additional] BIOS file(s).
  8. Opt into the betas from inside LaunchBox. Tools < Options < General < Updates
  9. The Vita3K importer was fixed in release 13.19. It has also been updated in release 13.28-beta. Here's a link to the procedure I did just this morning to test it and it worked without issue. The procedure will be the same for LaunchBox version 13.19.
  10. Just did a fresh Vita3K install (into LaunchBox) and all appeared to work here. Here's the steps I took: Open Vita3K emulator and made sure games have been imported into the emulator and are playable (from within the emulator) Close Vita3K Open LaunchBox Deleted my existing Sony Playstation Vita platform Deleted my Vita3k emulator (in LaunchBox) Closed LaunchBox (to ensure it's all 'fresh' when reopening) Opened LaunchBox Added new emulator Selected Vita3k from the dropdown menu for Emulator Name LaunchBox auto populated some fields, including the Associated Platform Browsed to my existing Vita3K emulator folder and selected Vita3K.exe Clicked OK to save and close Closed Manage Emulators Made sure Auto Imports was enabled Tools < Options < General < Automated Imports (box was checked) Closed LaunchBox Opened LaunchBox waited 5 maybe 10 seconds LaunchBox updated the local database LaunchBox imported the 3 games I had installed into Vita3K
  11. I know this process has been overhauled in the 13.28-beta release. You can try that, if you're so inclined. I have a test install of 13.27 and had received the same error. What seemed to have resolved it for me was: close LaunchBox delete everything in the /Metadata/ folder Run the 13.27 setup file and install to the same location If doing this, before clicking the last Install button, make sure the path is correct and that it doesn't have /LaunchBox/LaunchBox/ in the path Once the install is finished, close then restart LaunchBox (for whatever reason) Run: Tools < Download < Force Update Games Database Metadata...
  12. I didn't know you could download a Metadata.zip file containing the LaunchBox.Metadata.db file. Where did you find that at? You might be able to, with LaunchBox closed, delete the LaunchBox.Metadata.db file, start LaunchBox and then run Tools < Download < Force Update Games Database Metadata...
  13. Listed here are what's required for the BIOS file(s). Sinclair - ZX Spectrum (Fuse) - Libretro Docs
  14. I think you're the only one I've heard of that actually uses the shader feature. Stateside, or otherwise. So for anyone who's going to start using it [and downloads one of the recent betas or waits until I update the official release), they're good to go. Good point. I forgot that clicking Save in the main Settings window reloads all the settings into memory. We call that a 'hidden feature'. Thanks for all your testing and patience!!
  15. v1.3.1 Released New Feature: Added DemulShooter Ready badge. Indicates if DemulShooter will be started when the game is launched. To enable: View < Badges < Plugin Badges < Enable DemulShooter Ready Renamed some Titles to match the LB Games DB New Title (old Title) Big Buck Hunter: Ultimate Trophy (Big Bick Hunter: Ultimate Trophy [spelling error]) Drakons: Realm Keepers (Drakon Realm Keepers) Gekitou Densetsu: Block King (also available alt name "Block King Ball Shooter") Ghost Squad: Evolution (Ghost Squad Evolution) Heavy Fire: Afghanistan (Heavy Fire Afghanistan) House of the Dead 2 (House of the Dead II) House of the Dead: Overkill (House of the Dead Overkill) House of the Dead: Remake (House of the Dead Remake) Jurassic Park (Jurassic Park Motion) Let's Go Jungle! Special (Let's Go Jungle Special) Mission: Impossible Arcade (Mission: Impossible Arcade) Music GunGun! 2 (Music Gun Gun! 2) Operation Wolf Returns: First Mission (Operation Wolf Returns First Mission) Plants vs. Zombies: The Last Stand (Plants VS Zombies: The Last stand) Rambo (Rambo Arcade) Target Bravo: Operation Ghost (Target Bravo) Terminator: Salvation (Terminator Salvation Arcade) Tomb Raider (Tomb Raider Arcade) Loving Deads: The House of the Dead EX (House of The Dead: EX) The House of the Dead EX (alt name) House of the Dead EX (alt name)
  16. Does this coincide with my last post? Essentially, if you manually edit the xml file (e.g. to change the comma-decimals to dot-decimals), you need to restart LaunchBox for it to read the [new] values when going into BezelLauncher Setup. What's happening is, when you start LaunchBox, the plugin loads all the settings for the different emulators into memory. So when you go into BezelLauncher Settings, it's reading all the data from memory rather than accessing the file each time. If so that's good news! Can we call it fixed (in v2.2.2-beta-1 and beta-2)?
  17. Looking at the error log, that looks like it occurred when clicking "Test". At that point it's trying to read the old comma-decimals and erroring. The 'fix' was to save changes as a dot-decimal. That said, you'll need to edit your BLSetup.xml settings file and change the <ShaderRect> and <ShaderOpacity> values. You can reset them to: for ShaderRect 0,0,0,0 or replace the comma-decimals with dot-decimals. e.g. 0,0,0.2,0.2 for ShaderOpacity 1 Note: You'll need to restart LaunchBox after editing the xml file.
  18. I thought so too. Can you share your "BLSetup.xml" file. Plan "B" BezelLauncher (v2.2.2-beta-2).7z
  19. Correct. The free version of LaunchBox has all sorts of goodness in it and lets you play your games. It also allows you to preview Big Box with the limitation you can't launch the games. You can get a 1-year license that will unlock features unavailable in the free version (e.g. the Startup/Shutdown Screens, where you can disable the mouse during gameplay) and can get version updates for one year. This will give you time to decide if the unlocked features are 'worth the price'. If you decide at a later date to upgrade to the lifetime license, you can do so at a discounted rate. Or you can get the lifetime license from the get-go. And, of course, you can stick with the free version and still have fun playing games.
  20. One means of doing that is to create a new "emulator" that points to the reader executable. e.g. "D:\LaunchBox\System\Software\LaunchBox Reader\LaunchBox.Reader.exe". The make that "emulator" default for that platform. You can get possible command-line parameters by running at the Windows Command prompt "LaunchBox.Reader.exe --help". e.g. Basic usage: LaunchBox.Reader.exe --path "C:\Docs\Manual.pdf" LaunchBox.Reader.exe open --path "C:\Docs\Manual.pdf" --theme black --fullscreen I suspect that 2nd set of parameters can be rewritten to "--theme black --fullscreen --path". Then when launched with the "game", LB will append the path at the end. Just like you see with regular emulators. EDIT: Found this in the LaunchBox Strategy Guide. Using LaunchBox Reader as a standalone app
  21. When you purchase LaunchBox Premium, it opens up more features available in LaunchBox as well as gives you uninhibited access to Big Box. I guess I didn't know what you were meaning when you asked "That's with Big Box isn't it?".
  22. Full instructions are included in the link.
  23. That's good. It's also a different part of the whole process. So the beta should fix what's needed should you decide to go that route.
  24. Guess maybe you're back to having to read the wiki.
×
×
  • Create New...