Jump to content
LaunchBox Community Forums

snarfo67

Members
  • Posts

    65
  • Joined

  • Last visited

Posts posted by snarfo67

  1. Okay, maybe you can earn some bronze coating on that statue. My only issue so far is with the advanced controller config. My XBox One Elite controller is seen by FS-UAE as 'xinput controller #2' and I can't get the f10 to quite to work on it (I know it works since it works on the first xinput controller) no matter how I change the syntax. Actually I posted a question on an FS-UAE forum but so far no nibbles. Here's the text from that post:

    Hi all,

    FS-UAE detects and works with my controllers just fine--- however, I'm trying to map the game exit function to f10 and assign it to the right thumbstick button on my XBox One Elite pad and it's making me crazy. FS-UAE detects my controller as 'xinput controller #2' since I have a few other controllers hooked up to this htpc as well. I can go into the advanced controller setup and enter the string to enable this on the first 'xinput controller' (which works), but for the life of me I can't get the syntax to use controller #2 for the special mapping string:

    xinput_controller_2_button_9 = action_key_f10

    I've tried using #2 instead of just 2, with and without the underscore, etc., but I just can't get it to work on this second stick. Little help, anyone?

    To be clear, I can control the games with my Elite controller just fine--- it's just the f10 to quit and the speedup trigger functions don't work.

  2. 17 hours ago, Headrush69 said:

    How exactly did you update/add the roms? (Directly into your MAME rom directly or using a rom manager)

    1) Update packs only have the roms that have been added or changed within a set, not a complete repack of the roms needed for that version of mame.

    If you just copy the update pack into where your mame roms are, these incomplete updates will often overwrite the set you had before.

    2) Launchbox doesn't use the mame.xml. The 'scan for new roms' option just does directory scan if the platform rom directory is properly set.

    If you want to merge the update packs you need to use a rom manager like ClrMamePro. Technically you could do it manually, but I wouldn't suggest anyone bother unless it was for a few specific roms.

     

    Yeah, I use ClrMamePro to update them so as far as I can tell they function well enough.

    17 hours ago, SentaiBrad said:

    I just grab a new update pack, plop in the new stuff, but chances are we're not utilizing all the new stuff anyways. We're using MAME data information, but it's not something the user can add or change around, it's something Jason needs to manually update, the process of LaunchBox converting all the names, and assigning all the metadata properly. We're still using the .174 set. Unless something really breaks or changes with later revisions of MAME releases that requires his attention, there are other things that are taking a higher priority.  I would still update anyways, existing games can get updated too, I myself am on .181, but if there is anything new (which wouldn't be many games), it's most likely not getting imported anyways. So if you have a set, have imported things, and plop in a new update pack, if an existing rom was updated then there is no need for a re-import, and anything new is currently not being parsed anyways. Scanning for new roms will work theoretically in that position, if LB was recognizing the new changes after .174.

    Ah, that makes sense. I'll keep my MAME updated since I also use it to run Intellivision and Sega Genesis emulation (Retroarch is awesome, but its control setups are a miserable experience for me) and just keep an eye out for MAME version updating in Launchbox down the road. Thanks for the info!

  3. Not sure if this is off-topic or not, but it's at least related :-)

    I was using a complete .180 set and added the .181 updated files when it was released. I tried using the 'scan for new roms' function in LB but it came up empty (and ran very quickly considering the ROM folder size). I thought maybe LB might use the mame.xml file so I generated a new one from .181 and tried the rescan but again no bueno. Is there a painless way to add the new additions to MAME as they trickle out? For the record I just use the vanilla MAME64 executable these days since it supports high score saves now.

  4. @martinconroy One thing you might want to do is update your Windows 10--- build 1511 is from November of last year. If you haven't gotten 1607 automatically yet (the "Anniversary Update") you can download it manually from Microsoft's Windows 10 site with the update tool. Not a guaranteed fix of course, but being current is a good starting point :-)

  5. Not sure if I should send this to higan or @Jason Carr --- the current beta is working great for me (no crashes) with the exception of a couple VLC-related issues. The main one is when scrolling through a list of games and the video doesn't always load at all, which I realize a number of people have reported already. The other oddity only happened when I was swapping through a few of the very cool new themes and some audio from videos got stuck. Eventually I had an overlapping cacophony of game sound effects and music :-). If that's more of a VLC issue than a LB issue I'll post it for Higan. For the record I'm using the current 64-bit version of VLC.

    For me there's no real advantage to using VLC so I'll go back to the built-in Windows media player engine. The codecs included in Windows 10 are a lot more comprehensive than in older versions of Windows so all my stuff plays just fine without a 3rd-party solution. I really only use VLC to play videos outside of any programs anyway (even if its UI looks like a Windows 95 holdover) for the robustness of its options.

  6. Hi all, I'm working on converting my Hyperspin setup to Launchbox and I've hit a snag when launching any Intellivision game. A dialog pops up saying Error, DxPinput::OpenJoystick: Setproperty failed with error: ERROR_FILE_NOT_FOUND A Google search hasn't netted me any info, nor can I find any forums for jzintv (my default emulator) or Nostalgia, both of which I have installed. jzintv will run games just fine outside of Launchbox, though curiously Nostalgia (5.0) pops up the exact same error dialog and aborts. The error reminds me of the bad old days when you had to sometimes manually copy a DirectX .dll into an emulator folder, but this one isn't giving me much to go on. Anyone else had this issue and figured out a fix? intv-error.PNG
×
×
  • Create New...