Retro808

Looks really nice @Super_Paulie. Following this thread pretty closely as I have been waiting on marquee support to get some love. Great to see in the mean time theme edits can get us some good views. It missed out by a few places on the last feature request poll. So hopefully the next poll we can push more votes.

I have let mine run quite a few times for a day or more with no issues.

Some troubleshooting would probably be needed. I have 3 builds running in my house and most stay on throughout the day. I have not had any freezes from attract mode with them in over a year. I think it has been a while since anyone reported on it as well. I see there was a thread back in June but that member never responded again. I will tag @Jason Carr and see if there is anything he would recommend for troubleshooting.

According to mame those other versions you are missing are hacks. You would have had to uncheck the box for "Skip hacked games" as well.

Agree, but what he is describing is an exact issue I had. In one of the beta threads I ran the issue by Jason as I would also get this issue or when it did work and I exited Launchbox would freeze. I stumbled across checking the video and anytime I put it to openGL it would work fine. Anything else the issue occurred. Even had some issues with pc games doing the same. Jason did put some things in place that eventually the issue stopped. Not sure if this will help him out, but like you said worth a shot.

In Mame itself what is the video option set to? It should have options like Auto, OpenGL, BGFX, and D3D. Try changing it and see what happens when you launch through Launchbox afterwards. Try setting it to opengl if it is on something else. I had a pretty similar issue a while back.

OK a couple things wrong here 1. Go to you mameui64 folder and look for a sub folder called “Ini”. In there find a file called mame.ini and copy it then paste it in the main folder where the mameui64.exe is. 2. Mameui64 is not pointed to the folder where you are teliing Launhcbox the roms are. Open mameui64 and go to the directories option. In the directories for roms click browse and navigate to the arcade folder where your roms are and then save. The paths in the 1st and last pics you posted should match. Then repost the last pic so I can see if the paths changed. 3. Test a game in both MameUI64 directly and test the same game in Launchbox and let me know what happened.

Can you answer the following and provide the pics requested. This helps to see where the disconnect is. In your last set up your were moving roms, adding and removing emulators and it makes it hard to troubleshoot when changes are constantly made. I recommend leaving everything as is right now and provide the below info: 1. As you have it set-up right now if you open MameUI and choose a game to run does the game run? 2. Right click any game in Launchbox and share pics of the Launcher Tab and the Emulation Tab 3. Go to tools>manage emulators in Launchbox. Edit the MameUI platform and share pics of the Emulator Details tab and the Associated Platforms tab. 4. Open MameUI and go to the directories option, choose roms and share a pic of the screen showing your rom path. 5. Since you loaded a fresh install of MameUI, in the folder where you have MameUI64.exe located do you also see a file in that same folder called Mame.ini? I know you have shared pics before but I want to see it as you have it right now.

When you right click a game and choose launch with does it show other options besides MameUI? It sounds like you have both Mame and MameUI set up and Launchbox is confused on which one you want it to start as default. If you have Mame set up in your manage emulators list as well as MameUI see which on you have the tick box checked for "default emulator". You also mention it works if you move to MameUI64\rom folder and it does not if you run from original location. The roms can be in any folder you want you just need to make sure both Launchbox and MameUI are pointed to the same folder.

It looks like you are you using MameUI for arcade games, correct? if so make sure your mame.ini file is located in the same folder the mame.exe is located. If you do not see it there look in the Ini folder. If it is there copy it and paste it in the main folder where the mame.exe is.

You are likely watching a video with that person using an older version or a beta. If you are on 8.9 you are on the most current interface. Af of 8.6 there is nothing known as .Next. .Next is now officially just Launchbox.

You are now in what used to be called Next. That is the way it looks and works in the new version. It was called Next for a while so user can try it out and see what changes were coming to the standard Launchbox interface before Jason removed the old version and put this one live. The notes under version 8.6 here talk about the change. Launchbox can also now be themed and a theme developer can change some of the layout and appearances. Here are a few already made.

Launchbox.next is now Launchbox. Next was available as a separate .exe as Jason finalized it from beta release. It officially replaced the old Launchbox.exe as of version 8.6.

Not sure then really. Mapping buttons on the Xarcade is pretty straight forward in Retroarch and should work when done. What version Retroarch are you using? Can you share the same images from your setup that I did?

I had to reload as I posted the wrong image.

Not sure. Unless you have a core override that is using a different map when you start a game for that core. The tankstick works pretty easily with RA. I have had mine set up for a couple years now. Here is my user 1 bind and it works even though I no longer use RA for arcade games. Just tested a few games and it all still works as setup.

Does your P2 directions work in game? If not try turning you NumLock on your keyboard either on. That is a thing with tanksticks if P1 directions were recognized as the Numeric 2, 4, 6, and 8 keys. Mine used to do that. It now recognizes P1 directions as the arrows keys and I no longer need the NumLock on.

Not sure if we can help as this is a Launchbox forum and there are only a few people who post here consistently that use RocketLauncher. May be better suited to post your issue on the RL forum. A quick Google search of "RocketLuncher Error This is a folder and must point to a file" found this post. Not sure if it will help, but then again RL forum may be a better source for an RL related issue. There were quite a few other posts on their forum for this issue. Hopefully one of the experience RL users here will chime in.

Try putting the following AHK script in the AHK tab of your edit emulator screen for Demul. You may need to raise or lower the sleep time for your system. I believe every 1000 is 1 second.

If you are using MameUI try making sure your mame.ini file is located in the root folder where the mame.exe is. If it is located in the ini folder copy it into the main folder. See if that helps.

Thanks Monkus. I will tag @Jason Carr maybe a change somewhere broken something. I did test and again and several set-ups and it is definitely not automatically updating.

Right now it is not possible in BigBox. What I would recommend is creating a BitBucket ticket and link it here to see if you can get the community to vote on it. An easy way for Jason to track things the community wants to see implemented and also see how much of the community wants to see it. Click on Help & Support above then choose Request a Feature it will take you to BitBucket page.

Yeah...I am sure that I am sure. Jason has said many times his list of things is not short. In the beta threads he posts what the new betas include so he lets people know what he has been fixing and adding. You will notice in the latest beta thread there is a "fixed" section.

I am sure Jason knows it has not been fixed since. He did say he would add it to his list of things to tackle, but that list I am sure is not a short one. So you may have to give him some time to work through what he has on his plate.

Yeah I am not sure there is something that generates the playlist to update on its own without a trigger from the user. Usually had to do the steps you mention or restart. Even BigBox is the same way. I am actually not sure if this has always been the case or not. I have a Fav playlist but do not change it much.