Retro808
-
Posts
7,265 -
Joined
-
Last visited
-
Days Won
27
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Retro808
-
@tomkdesign Glad you're all sorted.
-
When you run mame64.exe with out a game and save your settings it will generate the mame.ini. But that may not be your issue since you are using the command line version. In the associated platforms tab of that image you shared. Do you have Arcade listed there? Whatever the name of the platform is that you imported your mame roms into needs to be listed there and it needs to be the exact name you have in Launchbox. From the video it looks like it is "Arcade" but hard to tell since it is cut off.
-
Yes to the wheel fade question. The steps are posted in this thread. See page 7. No to the left side wheel. Cid advised it would require a bit of work to rewrite the theme and at this time he is not planning on working on that. I think he mentions it in the first few pages of this thread.
-
What Mame are you using? MameUI, Arcade64, command line If your Mame.ini file is located in the ini folder copy it and paste it into the maind folder where the mame64.exe is. It is a know issue with any version of mame other than the actual command line version.
-
Is it freezing in Launchbox Next or BigBox (or both)? I do see you said BigBox, just want to confirm as I do no think the new release affected BigBox. The changes were just for Launchbox. In Mame what do you have your video set as? (auto, openGL, d3d) Reason I ask is I had the same issue. It would freeze exiting Mame on any video setting other than openGL. During the last betas Jason was able to have us test a few things and they fixed the freeze I was getting. Oddly enough it is this stable release that Jason added the changes. Can you try changing your Mame video to openGL if it is not already set to that and see if it still freezes.
-
Did you import those games by the exe file or from a shortcut? I had the same issue and it ended up being a few games I imported using shortcuts. In a couple games I deleted the shortcut from Launchbox and the games folder than generated a new shortcut and pointed Launchbox to it. That fixed a few games. On the others I had to just link Launchbox to the actual exe file.
-
Thanks @Jason Carr I will post out in the subforum and see what info I can get.
-
This was something a few have experienced in the betas. I have as well but the last beta and this new stable release fixed my issue. Does it do this after exiting all the emulators you use or just certain ones? Also does it do this every time or randomly?
-
@Jason Carr Is it possible to have the theme show a custom field in the area shown in the pic? I added a custom field to tell my kids if they use the "Joystick" or "GamePad" for a particular game and would love for it to either show here in the main game screen when it scrolls to this data section or at least have it show in the Game Details screen. Control Method: Joystick Control Method: GamePad
-
Launchbox.Next.exe Entry Point Not Found
Retro808 replied to Retro_Master's topic in Troubleshooting
How about a little more details? Was this in Launchbox, Launchbox Next, BigBox. What where you doing when you got the error? Opening the software, launching a game, importing a game, editing a game, etc... -
@KenSweep Yeah I missed that line in your post. ?♀️ ?
-
@KenSweep I believe the box flip thing with 3D images is just something not functioning in Launchbox/BigBox at all. If you are in Launchbox and have views set to 3D box it will not allow you to box flip there as well. I believe it only works with 2d box and 2d carts. I have no expertise in knowing if this is something can can be worked around and coded into a theme.
-
Is it just the exiting of emulators that doesn't work? Does the controller work in BigBox for things such as moving or selecting items? Try enabling "Use All Controllers" in BigBox.
-
Controller automation should work in BigBox as well. Did you open setting in BigBox and set your controller automation mappings?
-
Well that sucks. Wonder why for the kits it does not work like their production controllers. Gonna have to see if I can get that kit I gave away to a coworker to test out.
-
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.
