Retro808

Also you do not need to have the command line -run=dc -image= in this tab since you also have it in the associated platform tab. Just an FYI. Especially if you are going to use Demul to run Atomiswave, Hikaru, or Naomi. Just have it in the associated platforms tab.

That would be my best guess. I have not had my 4K monitor or TV connected to my launchbox setups in a while, but they all displayed correctly the default and many other themes. Change the scaling in your display setting and see. Easy to change back if it doesn't affect it.

What is your scaling set to? BigBox will not have any settings to adjust scaling you would have to do this in your pc's display settings. I know we have a bunch of forum members and mods who run 4k without this issue.

It is hard to say what could be causing it. We have seen pause working very well with Retroarch. Have you tested making sure all other programs are closed to reduce the risk of something else affecting the process? Are you seeing it with any core you use or only certain ones? Just taking a stab in the dark here. Have you tested with any other emulator?

Thanks Neil. I was just headed to do that and could not find the thread. LOL.

I know there have been some recent posts on focus loss like this with mame. It has been working well for a lot of users. Are you using the standard command line mame or one of the offshoots like MameUI or Arcade64?

In Launchbox, BigBox, or both?

Yeah, defining "Game Over" for use here as well as what one considers nice/clean is a bit subjective, but the good thing is themes can be edited to suit your need if you know how. The Startup/Shutdown themes are created by users and shared with the community. If you have the skills you can either create one or edit one of the existing ones. In the default shutdown.xaml you can delete that text and have it not show at all or change it to another term. The only theme you cannot edit is the one in the folder named "Default". You can copy it, rename it, then edit if you like.

That version is about 2.5 years old so there could be some minor issues with it and current Launchbox/BigBox features. We have seen older versions having issues with the new features. Try editing your Mame set-up in Launchbox and delete the "-keyboardprovider dinput" in the default command line prompt section. See if that helps. With new feature development in LB/BB I would recommend updating to a more current mame version and rom set. If that is something you do not wish to do, then you will likely need to find some work arounds to issues you are or may experience.

There is not a list compiled with that information. Typically that box is unchecked by default for almost all emulators, unless through Jason's testing or through feedback from the forum a specific emulator would need that checked and then Jason had the box ticked already. You might read through this thread to see if anyone reported any emulators that had issues and needed that box checked. I have quite a few that I use on a test pc and none of them have needed that checked.

@Belos I edited your post. Please be aware linking to sites with roms is against our forum rules.

Until Jason does implement a solution I would post a thread out in troubleshooting. I have seen a couple members post some in depth responses to AHK questions. Maybe they can help find a workaround. I would be interested in any solution as I am about to build a driving cab.

Ahh well then there is that too. LOL.

It will only show the Save/Load if you have an AHK for Save and Load states for the emulator populated. The save/load states in Launchbox only work if an emulator supports that option. Jason populated some of the systems with known save/load states and the stock configuration keys they use to initiate. Ao for ones that Jason may not use or is not aware of the end user will need to populate the commands. Once populated they should now show up as options in the Pause menu.

You should be able to run an AHK before the game launches using the additional apps feature. Right click and edit a game and choose the additional apps tab. I don't think a guide will be released. I recommend posting a thread in the troubleshooting or noobs sub-forum requesting help. We can give you a quick walkthrough there to keep the beta test threads clean for beta testing issues. You can also watch the latest video on this release. ETA shows you a quick how to on using the Pause feature.

Did you try any other emulator? You mentioned in a prior post you have not tried other emulators. I see in your video you have Mame and Model 2 emulators listed. Pause screens work fine with those two. Have you tested those on your setup?

Did you set the pause option for controller automation? There are LB and BB settings. Both your videos show an Xbox One controller recognized. It definitely works. It has been beta tested quite a bit. I have it running on 3 setups just fine.

Did you set your Pause button/Key in Launchbox? It is not actually using what is set in RA. You have to set it in the Launchbox settings. There are two areas to set Pause map. A Pause key and an automation for a button combo.

When you add your emulators to Launchbox, if you name the emulator something other than what it is normally called Launchbox will still recognize it to populate any AHK scripts Jason may have put in by default for the new Pause screen stuff.

Updates probably will not be too big an issue since the scripts are simply an AHK command to press the keys mapped in the emulator for save/load states. It uses the default from the emulator. So as long as the emulator creators do not change the default keys in their updates than Launchbox updates likely will not affect much. What would be a bigger issue is if you use different key/button maps.

Glad your sorted.

Now that you clarified exactly what you have been doing I know. Use this AHK with the .exe and it sends it to full screen. I just tested it. WinWaitActive , DeSmuME ; Send !{Enter}

OK Well, now I am confused. if it is not working why did you say earlier you are using the vbs?

From your image it looks like you are launching an exe and not a vbs. You have the emulator path as DeSmuME_X432R_X64.exe. That's the exe for the Japanese fork. Here is an old post about launching desmume from a vbs in Launchbox. The last post advises to use one of the AHK I posted as well. I just set up the version you have in your pic as well and it works with the same AHK. Not sure why it is not working for you. Any chance you have another Desmume emulator setup (one for the vbs) in Launchbox and you are editing the wrong one with the AHK?

Also just tested with the other AHK and that one works as well.