Jump to content
LaunchBox Community Forums

Darkman042

Members
  • Posts

    9
  • Joined

  • Last visited

Darkman042's Achievements

4-Bit Adder

4-Bit Adder (2/7)

0

Reputation

  1. I had some intermittent trouble getting Joy2Key working properly with Rogue Synapse's "Starfighter" but this seemed to do the trick!!! Thanks so much!
  2. So I fixed this problem by updating my MAME install completely. See my post about it here.
  3. Just an update in case anyone stumbled across this thread looking for help. I finally fixed the problem by updating to the latest version of MAME (which right now is .261) and also I completely updated the ROM set as well which unbeknownst to most noobs is SUPER important! Google “archive.org: Files for mame-merged” 3rd result has torrent links.
  4. Thanks!! Just over 3 years later and still helpful! 😀
  5. Hi, I tried to post on this thread but for some reason the "submit reply" button refused to do anything. The OP was told by various users that he couldn't make Launchbox work on a 32-bit machine anymore. I disagree. While the CURRENT version doesn't support 32 bit systems anymore, there is nothing stopping someone from downloading an older version. I downloaded version 11.0 from uptodown, and on my old Windows 8 32 bit thin client I tried it on, it works fine. Also had no problem using my forever license on it. EDIT: I tried to link to the download, but it was removed. {thanks mod team!!! 🤖} Just google "launchbox old version" that's how I got it.
  6. I wish that were the case, but for me there is. I have the mame.ini in the root folder already, and I tried taking out all of my command line arguments, but no dice. In MAME the controls work perfectly, but launching it with launch box they don't work. When the game starts, I can hit tab and see that the contols are still mapped, but the joysticks and buttons do nothing. I'm using Windows 10, and use SJ@JX usb encoders (https://www.amazon.ca/gp/product/B083RTT51K/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1) connected to arcade sticks and buttons. My MAME is an older version 0.122u1, but on it's own it works mint.
  7. I have the same problem! Did anyone ever figure this out? Mine actually works in MAME when not running launchbox. When I run MAME games through Launch box the controls are not recognized.
  8. My problem is similar to the one posted in this thread: My controls are SJ@JX boards wired to arcade joysticks and buttons. (Bought them from amazon, see here: https://www.amazon.ca/gp/product/B083RTT51K/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1) I tried the solution listed in the linked thread above(and in other threads) but no dice. I have the lifetime registration to LB/BB, I'm using a pretty old version of MAME (0.122u1). It's on a PC running Windows 10, and playing games is it's entire job. It is installed inside an arcade cabinet. Running MAME by itself my controls work fine. Through LB/BB they let me navigate the menus fine. I can start a SNES game through LB/BB and play it just fine. When I try to run a MAME game through LB/BB, the game runs but my controls are ignored. I can use tab on the keyboard to bring up the joystick configuration, and all of my previously set mappings for my joystick are there, but they just don't work. I've tried setting my mamepgui.exe to run as administrator. I've done the same to my LB/BB executables. I've enabled joysticks under the global options in MAME (before that they did not work outside of LB/BB which they do now). The command line argument "-keyboardprovider dinput" is not an option, because my version of MAME does not support it. I'm at the point where my machine is working just the way I want with this one exception. The thought of having to try and get a new version of MAME to run really sucks @$$. What about LB/BB could be blocking MAME from taking commands from my joysticks? The keyboard works with it both ways, so I already went down the joytokey rabbithole only to find out that it will not work under MAME. *ugh* If I can't figure this out I may have to swap my joystick boards for a keyboard one, but i believe that there must be a better solution than that. I have read many posts so far with similar problems but not too many with any kind of solution.
×
×
  • Create New...