Retro808

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.

You said "One of them is not working"...so does one actually work for you? Are you putting the AHK in the right place? I do not use Desmume, but just installed it and set it up using the below AHK and it works fine.

You just need to use a value that is used in Launchbox. These are the play modes you can choose from when you edit a game.

Either of these pasted into the AHK tab should work. Esc:: Send !{f4} or $Esc:: { Process, Close, {{{StartupEXE}}} }

If you run just Mame and LEDBlinky without Launchbox does the issue still persist?

@Jason Carr Seeing that adding to and removing from playlists that are manual is not updating unless rebooting BigBox. Rolled back to prior beta and the issue is there as well.

If you have the font installed on your machine it is pretty simple. Look for the line of code below. Somewhere inside that section add FontFamily="[Name of Font]" In the second code you see I added the Arcade font to it. The name needs to be the actual Font Name (see pic). <TextBlock Grid.Row="0" Grid.RowSpan="3" Grid.Column="0" Grid.ColumnSpan="2" Text="{Binding NowLoadingText}" Foreground="White" HorizontalAlignment="Center" VerticalAlignment="Center" FontSize="60" Typography.Capitals="AllSmallCaps" /> <TextBlock Grid.Row="1" Grid.Column="1" Text="{Binding Path=NowLoadingText, NotifyOnTargetUpdated=True}" Foreground="Aqua" HorizontalAlignment="Center" VerticalAlignment="Center" FontSize="70" Margin="0,0,0,0" FontFamily="Arcade" />

If you are trying to change the theme in the folder named "Default" you cannot. You can edit other themes you have downloaded or copy the default folder, paste, then rename it what you want. Then you can edit it and use custom text and fonts.

Try going into BigBox settings and refresh the image cache. Sometimes when you add new images manually you will need to do this to get them to show.

If the emulator offers multiple save states you can achieve this by deleting some line in the AHK of the Pause feature in the Edit Emulator screen. Such as in Mame if you delete the lines for Send 1 down and Send 1 Up it will bring up the list of save and load states in Mame for you to choose from.

I would not recommend editing LB xaml files unless absolutely necessary. If you do, always best to back up the original first. AHK will probably be in the Emulator.xaml

No, that should not cause an issue. I have my path set in ReDream as well. Not sure what is wrong. There are not many settings inside of ReDream that could affect it, and there are no command lines to be sure you have entered in Launchbox. The image I attached is my settings and it drops straight into a game. It is a pretty easy emulator to set in Launchbox. Maybe post the same pic I did of your ReDream setup. Then also choose a game and right click, edit. Share a pic of the Launcher tab and Emulation tab.

If you revert back to one of the prior versions you remember it working with does the issue go away? If you look in your /Launchbox/Updates folder you can see prior version. You can choose one you know worked and reinstall it. It will not hurt any of your media or game imports. I honestly cannot recall if anyone has posted LEDBlinky issues with the latest releases.