Jump to content
LaunchBox Community Forums

bundangdon

Members
  • Posts

    1,219
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by bundangdon

  1. Okay, good to know. Thanks for the advice, and I'll let you know if I encounter any issues during the install
  2. This is great news! I'm really glad to hear that the android app is back in development, as I still have the original android Launchbox app on my phone at this very moment. Time for an update
  3. Good to know! Thanks a lot for the update
  4. @faeran Any ETA on when we can get the Community Theme Creator files for this? Looking forward to making some 'adjustments' especially since this is such a smooth running theme
  5. Sorry to revive an old post, but I had the same issue today (after a 'fresh' windows install) and this method completely solved it. Much appreciated!
  6. I made a similar view with Community Theme Creator, which looks like this: Feel free to download it here TextGamesView.xaml
  7. Great job once again @faeran! Hope to see the Community Theme Creator project files soon
  8. Yep! Just did a test with Sega Game Gear and it's working properly. I tested it both with Retroarch (on its own), and once again with the same emulation setup in LaunchBox and there were no problems. The bezels and the cfg files provided by the Bezel Project program were displayed there with the few games I tested. You may want to check your Retroarch configuration ("manage emulators" in options) and make sure the cores are set up properly, and if you have more than one instance of retroarch set up, that might be a cause. Otherwise, you may want to consider setting up Retroarch again in LaunchBox and basically 'start from fresh' and see if you can get better results.
  9. Okay, I'll do a test with it now and see what happens
  10. That's kind of an odd situation, but I've had a similar thing happen to me as well I'd check to see if the cores you're using through Launchbox are the same ones you set up with the Bezel Project. For example, you may have "mesen" set up with the Bezel Project for NES games, but perhaps LaunchBox is launching the FCEumm or Nestopia core. I'd start by checking that first
  11. Just to add my 2 cents. Coming from my own experience in recent days, if you want to play the less demanding "A" titles, 2D games, and mostly indie stuff, you can get by playing Yuzu with a budget GFX card, but I'd have to say you'll need a pretty beefy processor (CPU) and a decent GFX card to play the more sophisticated 3D and "AAA" games. The same holds true for PS3 games as Neil mentioned. I have an older CPU (i7 4790s) and Nvdia 1070GTX, and while I'm running Super Mario Odyssey, it's playable but sluggish at best.
  12. okay, it's basically a copy of the mame.ini file, but customized for only cdi games. so if you don't have it, just copy the mame.ini file and rename it to cdimono1.ini and then change the settings accordingly
  13. For some reason, this is one of the most tricky systems to get working with Mame, based on the number of posts I've seen here on the LaunchBox forums, and I'd have to agree with that, mostly because of Mame's slightly picky configurations for software games like this. First, make sure you have the correct bios file (named "cdimono1.zip" or "cdimono1.7z") and also make sure you have the cdimono1.ini the "ini" folder of mame with the correct directory of where your bios is located. For example, like this: # # CORE SEARCH PATH OPTIONS # homepath . rompath C:\launchbox\emulators\mame\bios hashpath hash samplepath samples artpath artwork ctrlrpath ctrlr I just tested this out, and it's now working for me.
  14. Yep, you have two choices: stick with the older mame and remove that "-keyboardprovider" from the default command line parameters, or update to the latest mame, but you'll probably have to find the latest set of mame roms. To answer your question, "newer is better" certainly does apply here, but I wouldn't be able to go into any specifics and if you're content with your current/original setup, then I'd stick with the older version of mame
  15. in launchbox, "tools" - "manage emulators" also, if you haven't changed your mame files in the past 5 years, you may want to update that as well since there's been a lot of changes since then
  16. Try replacing your mame default options with this instead, and see if it works -keyboardprovider dinput -skip_gameinfo -nowindow
  17. Great work once again! It was truly an honor to help out while testing this theme in recent months and congratulations on putting out another excellent theme!
  18. That newly updated text filters view looks really nice! I'd give a little more room for the fanart and other artwork, with a little less room for the games list, but that's probably just me
  19. Note (to anyone out there who might be following this thread), I've recently updated this with a slimmed-down, working version. More updates to come, so stay tuned
  20. Yep, the 4.2 version works for me It's a nice use of the given space, without going overboard either. And great work too with these latest updates by the way!
  21. Not sure, but this was a fork of the "Nostalgia" theme (by eatkinola), and I had the same crash-issue with that theme. I'll take a look at it once more tonight and check to see what happens with the latest official version of BigBox UPDATE: Just tried this theme now and I get hit with a barrage of errors, including this one: Could not load file or assembly 'System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. App: Big Box Version: 11.10 Type: System.IO.FileNotFoundException Site: Void .ctor() Source: Ao.Bigbox.Themer.v3_9_6 at Ao.Bigbox.Utils.Fu.EnvironmentInformer..ctor() at Ao.Bigbox.Utils.Fu.EnvironmentInformer.get_Instance() at Ao.Bigbox.ViewModels.EnvironmentInfoVM.UpdateEnvInfoProps(Boolean async) at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 10:00:46 PM Exception
  22. Yep, very sorry about that and I apologize for the very late response. Ever since Launchbox/BigBox changed the theme system with recent updates, this theme no longer works properly. I'm currently rebuilding this from the ground up and will upload a working version in the coming weeks.
  23. I'm not sure if there's a proper tutorial out there just yet, but the theme creator is relatively easy to figure out. There's a theme included with the program called "Plain n Simple Community". I played around with that for a while, before diving into my own theme a little later.
×
×
  • Create New...