sundogak

You cannot hide an entire platform. It has been on the polls to add as a feature (one I would like as well) but never got enough votes. You can edit in mass games within the platform and hide them. If all games in a platform (or playlist) are hidden and you keep "show hidden games" check box off in BB, it will not show the platform. Then in LB you can still work/see if you keep that toggle to see hidden on. Not ideal but only way short of removing.

Daphne is a bit wonky with screen resolutions and playing well with front ends. There are a few things to try. 1) Try turning off the startup screens within Launchbox (Tools Menu, Edit Platform, Daphne, Startup Screen tab). I have found, depending on how you have set your resolution launch commands in Daphne emulator, the startup screen can get pushed into the foreground. It is more likely when in BB since it is fullscreen already as part of interface. 2) If you want to have the startup screen, try checking "Aggressive Startup Window Hiding" in the same tab as noted in #1. That can typically force the startup screen back to the background. 3)The other is more fiddly, but you tell Daphne to launch at the window height of your monitor then the windows don't get jerked around when switching resolutions. So if you have a 1920x1080 monitor, telling Daphne to launch at or close to the 1080 height will usually keep the windows from moving around as much. It is more complicated because although most games will work at 1152x1080, some will get distorted (like Dragon's Lair which the closest match is 1620x1080) and some people have different video roms which are different resolutions. I would try the other methods above first unless you are familiar with how Daphne launch batch commands work on your setup and see if fixes.

..and the "other" logo..in all it's non-artistic glory.

@BluSonik This should be the rest of the company logos that were missing from the previous page.

Go into LB and Tools menu, then Manage Emulators. Look at the setting in Edit emulator under MAME in LB. These are my settings: make sure you have the command line entered correctly in LB watching for the dashes and spaces (you can ignore the -sl4 phasor entry in my shot above) apple2ee -gameio joy -flop1 Also check the details tab in same window and see if have everything similar to below with all the check boxes unchecked: Question #1 - No there is no verbose mode other than if debugging LB itself (i.e., if LB is crashing). Sometimes easier if you turn off the startup screens can see things but most times like you found, the window will pop up quickly. Sometimes have used the emulator log to figure stuff out but will not likely help you in this case. The "Sample Command" line at the bottom of the Edit Emulator window is sometimes a key to problems in that LB takes that, adds whatever is in your Default Command Line Parameters and tacks on the ROM path. Question #2. You would need to add your MAME config path in your command line to where MAME.ini is located if launching command line outside the MAME directory. As you found, in the MAME directory when launch command then MAME assumes where the relative path is and launches. As to if that is the issue within LB, not likely as long as your MAME.ini and UI.ini pathes point to everything correctly (since it works outside MAME then seems that is fine). Basically, LB is launching "within" wherever you pointed LB to look for MAME.EXE file. Unless for some reason your MAME exe is in someplace odd, the typical MAME setup LB will work fine. Ultimately, LB inserts the various parts in the windows above as a launch command so if you are launching from command line and works then would need those similar parts in LB somewhere; hence the default command line entry box is key, particularly for Software Lists since not a simple MAME and ROM command. I would double check the above settings in your emulator. Since you said MAME is working otherwise, then screenshots from the LB side are more likely to lead us to the problem in that it isn't a MAME issue directly (i.e., the command that is calling MAME in LB is glitched.

@RevJoe98LB automatically backs up key XML files. They are located in your ...\Launchbox\Backups directory as Zipped files. The zip files are named with date and time. So go in to the most recent one and look within the zip file and will see a Platforms folder which contains the Arcade XML file. Extract and take the non-corrupt file and replace the corrupt one in your ...Launchbox\Data\Platforms directory. If you just want to restore all XMLs back to a certain time, then LB has a restore feature under Tools and Restore in LB. It will point you to the same Zip file folder as mentioned above to select the date you want. I have never used it myself. But if you just want to restore one platform would do as noted above.

The start and pause screens are in the tabs in edit platform. Well, nothing sticks out as incorrect. Since you said it works in RA outside LB, it is odd LB having issues. Other than trying another PSX core (like the HW version) or another game (something with CUE, but that doesn't make sense if works outside LB). The other thing to try is to install a second "from scratch" Retroarch emulator in LB (Call it something like Retroarch Test) and see if something we cannot see (errant character in a name or something). You don't do anything to your working Retroarch emulator in LB, you leave that as well as your RA install outside LB. You just add another instance of Retroarch in LB and link to same exe and only point to the Sony PSX core. You can have multiple emulators for the same platform, when you right click a game you can select which emulator to run (or pick one as default). Then try running it with the "Retroarch Test" emulator and see if same problems. You could delete the main one in LB, but looks like you got quite a few things setup there so don't want to mess with that too much. Sort of out of ideas from my end after that, sorry to say.

Your question on multiple cores, no you can have multiples. They don't impact each other. You said you had it working in RA, but I assume the RA core you used outside LB and the one listed in the LB drop down are the same. Nothing immediately an issue in screens you showed above. What is one of the games you are testing edit screen look like? Lastly, would turn off startup screen and pause screen while testing and check have default AHK scripts and nothing in the "Running AHK" tab. All these work fine in RA and LB but just helps eliminate any variables while figuring out what is wrong.

Post screen shots of your settings as noted above.

Screen snap the above two windows and an example game rom window that will help folks to see if there is a glitch in the setup. There isn’t anything in RA that you have to make work with LB. LB is “just” a launcher so if working outside LB it means a setting somewhere in LB is likely causing an issue. You might also temporarily turn off startup screens in LB so you can see if any windows are popping up that would be masked otherwise. Is LB and RA working for other platforms or is it just PS1?

@itsturningred What he was talking about was the settings here under Tools, Edit Emulator, the "Don't Use Quotes" option box: Also should double check your Associated Platform name matches your platform title as well as a core is selected.

It must be that your are not using a proper MAME set from naming perspective. The 5200 launches fine for me via RA. I don't use it as primary but had tested /set it up. Here are my screens:

Good to see another option. For the MAME issue of CDI Text and full screen issue that can be addressed by going into the setup menu in MAME. So TAB, Video Options and then select MAIN SCREEN only and not Main + LCD. MAME is emulating the LCD screen on the front of the CD-i player which is on by default but with that step will get rid of it. That also addresses the second item which gives you a full screen. There is no way I know for MAME to resolve the third issue which is the button push at the start screen.

@drewjbx One item to note is the Hatari RA core is some versions behind (1.8 versus 2.2) and about 5 years old versus standalone Hatari.

@LapoAlso, you can change directly within Hatari what buttons to use for Quit. Right ALT is the modifier key and Q is quit. But you can just directly tell Hatari what you want. For example, you can directly assign ESC (or whatever key you want) to the "Without Modifier" box in the Keyboard setup and then can dispense with any AHK type deals (assuming you don't need that key in a game). You can also tell Hatari to exit without confirming by going into the Hatari.cfg file and looking for "bConfirmQuit" and changing that to FALSE. EDIT: I didn't realize I had it already and it is what you originally asked (sorry haven't used Hatari in awhile) is placing this in the Hatari Emulator Exit tab (make sure to delete any other exit AHK in running tab in previous email). This will send a ALTR Q quit command: Send {RAlt down} Sleep 50 Send {Q} Sleep 50 Send {RAlt up}

@drewjbxThe other thing to test is if you have the "Keep desktop resolution in fullscreen" checked.

@BluSonik see attached @BluSonik EDIT: Noticed there was a glitch in original ones, so replaced them with fixed versions (blue shading was misaligned on left side).

@drewjbx I had used Hatari and still have it setup (use Steem and/or RA with Hatari core). I don't have any issues with startup screen in Hatari. With standalone Hatari this is my setup screen: --fullscreen --statusbar n --fast-boot y --desktop-st n --force-max y --confirm-quit n --disk-a My recollection was that the --force max command helped keep the windows in check and not lose focus.

@LapoI have a keyboard and keypad button set via AHK script. Place at least the ESC line into the Running AutoHotkey Script tab in the Edit Emulator screen: Use the Escape key to close Hatari. This should allow LB to exit via the pause screen Exit Menu selection. $ESC::WinClose, ahk_exe hatari.exe Optional Example : Use double press of Xbox One Guide Button to exit ;for exit only with double press of XBOX Guide vk07:: if (A_PriorHotkey <> "vk07" or A_TimeSincePriorHotkey > 400) {} WinClose, ahk_exe hatari.exe return EDIT: See my last entry on next email for best solution and directly what you asked.

@BluSonik Here are a couple options now that LB has gone final with release.

Work productivity = 0 New Logos =1

Work Procrastination......complete for a bit.

About half of these have been done by others in this thread or are in Supersprayer's pack (linked at end). May be a bit on any missing since work beckons. Other company not on your list are in Supersprayer's Pack

Good to have options; this logo was also in the original Viking pack in his Game Handheld pack at the beginning of this thread. Also there is a PSD blank template as well.

Yes, because it uses the MAME hash files to translate the MAME zip file name to a normal text title. So you have to have a normal MAME Software List set for whatever importing. Similar to MAME arcade for LB import wizard it is then (usually) close enough for the LB DB scraper to match. Particularly, if like Mame arcade DB entries, people have also entered in alternate titles. The few that don't match are not the fault of the tool, just differences in way MAME folks title their names versus what is in the LB DB. At a minimum, you have a "human" readable title versus the MAME short file name to do a manual match if LB doesn't do a fuzzy match. I have used it for some of the "oddball" systems I hadn't tried but were in the MAME software list set, like Fairchild Channel F system. That is a good one to test since not many games but enough you wouldn't want to do manually (~40). There were about 4 out of the set that didn't match (a few were not in DB like Demo Cartridges), in most cases due to glitches in LB DB which updated. Definitely, far easier than putting them in manually if using the MAME sets.