-
Posts
7,330 -
Joined
-
Last visited
-
Days Won
27
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Retro808
-
Controller automation should work in BigBox as well. Did you open setting in BigBox and set your controller automation mappings?
-
So you tested it and it doesn't work? If so, then the kits are different as all other 8bitdo controllers work like that. Its not just Android mode it is their d-input mode for windows also. On this model (image below) it is just start, most other models it is Start+B. D-input mode connects to windows just fine and I see that mode is available in the diy kits manual. If it does not work for you then you may just be stuck waiitng for a workaround or a firmware upgrade.
-
So looks like he is saying in that post if you delete the autoconfig file for that controller name you should be able to generate a new one. The other issue though is it is recognizing it as an xinput. I believe in order to be able to make the effective swap you have to set the controller to dinput mode (Android). Try starting it with Start+B and see if you can change the map better. As mentioned earlier that is the only way I can get the non DIY kit controllers to work properly for the correct A/B mappings. Xinput mode will continue to recognize Xbox style controller binds.
-
Are you talking about the "0"? That does register as a button from the 8bitdo controllers. Below is how my SN30 Pro is set in RA and A/B are correct when playing SNES games. I wonder if the kits just do not work right. I would probably email 8bitdo. Cam you edit the core's config file you are using in RA and see if it will work? input_player1_b_btn = "1" input_player1_y_btn = "4" input_player1_select_btn = "10" input_player1_start_btn = "11" input_player1_a_btn = "0" input_player1_x_btn = "3"
-
Not really sure. I have not messed with the DIY kits in RA and I do not have one anymore as I gave it to a coworker. I know for the other controllers that if I start in d-input mode (I think the manual lists it as Android) I can map the buttons in RA to the correct A and B. Just double checked and the SF30 Pro and A and B are correctly mapped. Hopefully a firmware update down the line will allow better mapping on the DIY kits.
-
I believe that when you do the initial start option (choosing to start as xinput, dinput, switch mode) you do the proper start method such as start+up then each subsequent start if you just hit the start button it starts in the last mode you chose. So you dont need to do start+up each time after you do it once. You should be able to start using the start+up method than follow the remap options listed in the manual. Hold Select+Down for 3 seconds to saw A-B and X-Y. I have not messed with that so I cannot confirm it will do what you want.
-
I use the 8bitdo controllers. The manual will show you how to boot it in xinput, dinput, swtich mode, etc... dinput should set the correct button layout. A is A, B is B. If I remember correctly though the kits actually have a hotkey swap for switching A/B X/Y in the user manual. edited: added manual link take a look at the button mapping section.
-
@matchaman A quick google search found a bunch of related posts to this and VLC users. Looks to be a bug in VLC itself. Here is one example it is a bit older thread but there were more recent one in the search. Not sure if any of this will help you.
-
You should be able to run them fine. None of my emulators, game exe files, or Launchbox/BigBox are run as admin and they all launch fine. For Mame if you open Mame and hit tab you can set your exit command inside. It will allow you to hit 2 buttons at one time to set a combo. You can try pasting this AHK in the Auto hotkey tab of the other emulators. LB controller automation I believe uses "escape" to close the emulators. So this should help. $Esc:: { Process, Close, {{{StartupEXE}}} }
-
What systems are you having issues with. I have not used a 360 controller in while, but it should work. I know we have some mods and members that use Xbox controllers regularly so they will likely chime in. Also, it is recommended to not run LB with admin rights. Doing so can cause issues with programs/emulators that require elevation.
-
Use Retraorch. It was recommend earlier. Pretty much the go to for Sega Megadrive/Genesis.
-
Games Work in MAME but not in LaunchBox
Retro808 replied to LordDangerMouse's topic in Troubleshooting
@esko918 You can also edit the Mame.ini file and add .; in the section for the ini path. This will tell Mame to look also in the root folder for the ini file. Otherwise if neither of the options work you may have something else wrong. -
Go to BigBox settings and in images refresh the cache for all images. When you add new images make sure you do this each time to ensure the cache now captures the updated images.
-
Yes, you have to make the folder. It is not generated by Launchbox. Are you talking about if you are running a shutdown video when you close BigBox if you restart BigBox too fast the the start-up video does not play? Are you using that outro/shutdown video plug-in from the 3rd party downloads?
-
Not sure why that happened, but if you are using a LB version that is recent startup videos now go in their own folder. So you should have a /Launchbox/Video/Startup folder and then you can drop multiple videos in it (file names do not matter) and LB will use them at random on startup.
-
Ok, however you still did not answer the question asked. What is the name of the system/platform you are importing Street of Rage 3 into Launchbox as? If you are importing as Arcade under Mame LB will not find it since it is not an arcade rom. Edit: ninja'd by one of the best ?
-
What is the exact name of the platform you imported the game as? Reason I am asking is in the Launchbox screen on the left you have a platform name of "Mame" and in the associated platforms image you have "Arcade Mame". Just as an FYI the assocated platform name in an emulator setup must match the actual name of the platform you have in Launchbox. This may not be why it is not showing, but it can lead to issue with roms actually working through Launchbox.
-
You figured it out. That’s all that matters.
-
I would probably check the old emulator set-up and make sure the Default Emulator box is not checked in the associated platforms tab. If BigBox is trying to launch the game through the old emulator something in your setup is telling it to do so. Go tools>manage emulators in Launchbox and in the old emulators check the associated platforms tab for that check box. If it is checked uncheck it.
-
Do the games launch with Retorarch in Launchbox? If they do it should work in BigBox since your Launchbox set-up is what feeds BigBox. Even though you bulk edit the games to a new emulator you need to make sure Retroarch has the platforms for those games listed in the associated platform tab.
-
Just open Retroarch menu and see what keys/controller buttons you have it set to. Open Retroarch or launch a game and hit F1. Go to the input menu and look under hotkey binds. I cannot tell you what the default is as I changed mine.
-
In Higan when you launch a game a new menu appears next to "library" with the system name of the game you launched. You need to enter that menu and make sure gamepad is enabled. In your video you launched a Famicom game so "Famicom" appears next to "Library" in the menu. Go into "Famicom" and choose "Controller 1" and make sure gamepad is enabled. I have not used Higan in a while, but I remember having this same issue when I tested it.
-
Knowing which emulator you are talking about would help. Retroarch? Launchbox/BigBox do not have bezel support.
-
Copy that! Thanks @Jason Carr