spycat

I'm having some issues with the versions feature as well. This works properly in LaunchBox Mode Boxart View where the version displays after the title text below the game's boxart cover and you can hide it by unticking Show Versions (Control + R). However in the details flyout box and also the details right sidebar box the version always shows and is prefixed with a v. Show Versions has no effect here. In List View the version text displays ok (no v) but again it always shows irrespective of whether Show Versions is ticked or not. In BigBox Mode the version text never shows. Maybe the BigBox Options, Game Details needs a Show Versions tick box?

Apologies Jason. The right-click menu doesn't appear to be buggy after all! I was moving the mouse over a game in List View and right-clicking to open the right-click menu and was having issues with launching the various options. However, if I move the mouse over a game and left click to highlight it, and then right-click to open the options menu, then it works just fine.

Hi Jason. I've been trying out the new List View feature. If I select List View, and then go back to Boxart View, The boxart always displays by Genre. In List View mode, launching games works ok when left clicked but the right-click menu is quite buggy; e.g. launches the wrong game, opens the wrong manual etc. It's early days yet and this will turn out to be a lovely feature. And now a few personal suggestions if I may. An option to hide unwanted fields. The ability to re-order fields in a left to right priority. Customising the style of the grid. I like OpenEmu's alternate bars format. Font and text colour customising.

Hi Derek. The Escape key is the ePSXe team's official and only way to exit this emulator properly (process ended). This applies up to the latest version 1.9.25. Using ESC is fine if your keyboard is reachable when you're actually gaming. If you want to exit using a game controller then you need the controller to pass an action as a keyboard ESC press. A common ePSXe emulated games profile using Xpadder or a similar app to pass a combo (to avoid native click clashes) as an ESC key press should do until an official LaunchBox solution becomes available.

Hi Triclinic Start LaunchBox itself (not BigBox). Select Tools, Options, Updates and tick the Update to Beta box. Click OK and close LaunchBox. Now start either LaunchBox or BigBox and the New beta available box should appear.

I also use gzdoom in application mode, as I do for all my Windows games. However, if it works in emulator mode then that's fine too. I'm not sure if this is your problem with Hexen Deathkings. This is an expansion pack for Hexen Beyond Heretic and so it needs the HEXEN wad in gzdoom. If the HEXEN wad is missing then HEXDD won't run.

Hi folks. I'm using Nostalgia 5 to emulate the Mattel Intellivision. At the moment I have 12 Intellivision games set up in LaunchBox. 11 launch perfectly, but Demon Attack fails to launch and gives me the error shown in the first attached image below. Also, if I set LaunchBox aside and use the emulator itself (see image 2 below), I can launch this game either by clicking on it in the games list or by clicking the Run Selected Game option in the File menu. However, using the Load File option returns an error similar to the LaunchBox one. This issue appears to lie with either the game or the emulator and not with LaunchBox. Just wondering if any members using this system have had a similar issue with this particular game and if they found a solution to run it in LaunchBox.

Hi Jason. A small issue I've noticed in betas 9, 10, 11 using my mouse. In LaunchBox mode when I click the information icon for a game's boxart image, the details box pops up but closes as soon as the mouse is nudged. Re-clicking on the icon pops up the box again and this time it stays put as it's supposed to do. Moving to a different game's boxart and clicking it's information icon gives the same issue. And now for some nice news. As I mentioned in a previous post, exiting BigBox to Desktop mode wasn't working for me. This affected a few betas but you have solved it in beta 11. Many thanks.

Hi Jason. Here's another. There's probably quite a few of these out there. http://launchbox.en.uptodown.com/

Xpadder works fine. No more -s1=3 crossed fingers approach. The downside is that while a common Xpadder game profile works for all Odyssey2 games, the Additional Apps if used to auto launch and close Xpadder needs manual setting up for each game. Game saving and loading in O2EM. There appears to be no option to specify a saves folder, like you can do for bios and roms; game savestates have to go in your main folder. Game saves are enabled by using the -savefile=file parameter and as they are on a by game basis they need to use the Use Custom Command Line Parameters. Best thing is to abandon the Default Command Line Parameters and put global (all games) parameters in your o2em_def.cfg file; things like fullscreen etc., and use the Custom Command Line Parameters for game specific things like save files. One thing, if you save your progress in a game and then launch the game again, it does not offer an option to either start a new game or load the saved one. It just loads the last saved state of the game.

Hi Derek, out of curiosity, which controller did you use? It looks like controller use may be hit and miss and I just struck it lucky with using a Sony PS2 one. I agree, the Xpadder solution would be best, as the -s1=3 switch really only affects the 5 gameplaying keys. With Xpadder it would be possible to map the other emulator keys like ESC and the function keys too. RetroArch might be another route, but I know nothing about it apart from it may have o2em support. By the way, I've had no issues with games with spaces in their rom names. Stuff like Atlantis (USA, Europe).bin and Pick Axe Pete (USA, Europe).bin launch just fine. Very strange indeed.

Hi Derek You can get the latest windows binary (1.18) here. http://o2em.sourceforge.net/# I'm using the same bios as the first one on your list (Spoiler 2) You can rename it to o2rom.bin if you like. Hi Randalf You can make a settings file for o2em like this. First use Notepad to make a new text file and name it o2em_def Enter whatever settings you want as the o2em guide explains and save. This file will have the .txt extension and you will need to change this to the .cfg extension. This file goes into the same folder as your o2em.exe You need to clear the Default Command Line Parameters box in the LaunchBox Edit Emulators window for o2em, as anything in here will overrule stuff in your new config file.

You can try adding this to the Default Command Line Parameters box in the Edit Emulator window. -s1=3 It works fine for gameplay using my Sony PS/2 controller. I can navigate with either the left analogue or the D-pad and the Circle button performs the actions.

Hi Randalf. O2EM works fine with LaunchBox. See the setup images below (your paths will differ). If you've set things up like this then all should be ok. Your bios and game roms need to be unzipped to work. The bios rom goes in the BIOS folder and the games go in the ROMS folder. The -fullscreen parameter is optional.

Hi TheSickness. The problem seems to be that you imported your Mame games into the Games folder in LaunchBox instead of the roms folder inside your version of Mame. Mame's roms folder is where the emulator expects the game files to be, unless you reconfigure it to look elsewhere. If all your game, bios and device roms and your chds are in there, then there is no need to keep a duplicate copy of them elsewhere in LaunchBox. These are doing nothing just taking up space and they can be deleted.

Hi Russ. Are you talking about Mame32, the Windows GUI version of Mame. I used to use this a long time ago. It did the job, but I wasn't too keen on it and switched to using the official Mame, first with EmuLoader and now LaunchBox. I use LaunchBox to play Mame emulated games and EmuLoader just for easy gui based configuring of Mame. Out of curiosity I searched it out. Apparently it's been replaced with MameUI32, so I downloaded this (version 0.146) and copied my Mame roms and sound samples to it. When I ran an audit, it rejected some of my roms mainly due to my neogeo bios being a different version. I set it up in LaunchBox and it's working fine - tested Zaxxon, Osman and several other availables and they all launched ok. Here are images of MameUI32 set up in my LaunchBox. Your paths will be different of course.

Hi Jason. With 5.3 beta 8, if I launch BigBox either directly or from within LaunchBox and then exit to LaunchBox, BigBox closes but LaunchBox doesn't open. This worked fine before. This is for me a very minor little issue. I'm just curious if anyone else is seeing it. By the way, I like the new feature to click images in LaunchBox game details popup and right sidebar.

Hi folks. I don't use Retroarch so I can't comment about it. But if you are using Mame as an emulator in it's own right with LaunchBox you can disable the game info screen either by adding -skip_gameinfo as a LaunchBox Default Command Line parameter or by editing the Mame Configuration Settings file (mame.ini) to set skip_gameinfo to 1 The Roms copyright warning screen can't be bypassed since Mame 0.100 way back in 2005. But this box only pops up when a game is first run. The problem game screen can't be bypassed, and will always show for a game that has support issues in Mame. Personally these startup boxes don't bother me. They can be clicked through in no time at all.

Hi Jason. The new scripting system seemed to be causing some Additional Apps feature issues for me. Legitimate stuff like launching Xpadder profiles, or other versions (trained etc) of a game, or other discs for multi-disc games, all worked ok. But I was also taking advantage of the versatility of the Additional Apps feature to display text based stuff like game instructions, controls, help, solutions etc. and image based things like game maps, videos etc. These could be actual files or urls. Since the new scripting arrived these no longer worked and returned an error message. However with the new beta 7 everything works perfectly. Awesome work Jason! By the way are there any plans to allow videos in the Game Details Popup/Sidebar in LaunchBox itself?

Hi Jason Yes that's fixed the error I was seeing. Many thanks to you.

Hi Jason Here is a capture of the error when you try to launch a game using some emulators. It seems to occur with any emulator that does not have the blue coloured Click here to download the Emulator option that appears in the Edit Emulator window top right.

Hi Jason Just tried out the new beta. Most emulators are launching games ok, but I did run into a problem with some obscure emulators. For example Playstation games emulated with ePSXe launched ok, but those emulated with pSXfin returned an error. Opening the AutoHotkey Script tab in the Edit Emulator window for this emulator and clicking the Reset to Default Script box cured this issue. This method also worked for all other emulators that gave me the error on game launch.

Hi Jason I updated to the latest beta and found that the AutoHotkey file was removed from the AutoHotkey folder within LaunchBox. Rolling back to the previous beta restores this file, and updating once more to the current beta deletes it again. Is this normal. Other than that, the new beta works perfectly in both LaunchBox and BigBox and the new Edit Emulators window looks good.

MAME currently supports two of these pre-CPU arcade games of the 1970's: PONG and more recently BREAKOUT. DICE (Discrete Integrated Circuit Emulator) as of version 0.9 emulates 21 of these games. It's GUI based and can be run standalone or used with LaunchBox. It's an unusual emulator in that the games are inside the executable itself. So, as there are no actual game files for LaunchBox to point to, you need to launch DICE in application mode and add the game name (as known to DICE) as a parameter. Some games, however, also need an external ROM image in order to work properly. These are Anti-Aircraft, Attack, Clean Sweep, Crash n Score, Indy 4, Jet Fighter, Shark JAWS, Steeplechase, Stunt Cycle and Wipeout. When sourcing these ROMs you need to ensure you get the TTL versions. The ROMs (still zipped) go in the roms folder and they must be renamed to the DICE recognised names as listed in the text file that comes with the emulator. The attention span of these games in today's gaming world is probably a few seconds, but for the arcade enthusiast they are worth preserving. http://adamulation.blogspot.com.br/ Note that VirusTotal returns a ratio of 1/57 for the DICE executable. I've had no issues with this program and this is most likely a false positive. Use your own judgement.

I have VLC which plays virtually everything. However, I'm still back in the good (bad) old days of Vista SP2 32 bit, and so I'm stuck with WMP 11 which doesn't play mp4 videos and as a result BigBox won't play them either. Rather than play around with 3rd party codecs I batch converted my mp4 Emumovies game videos to wmv format which WMP 11 recognizes. The converted file sizes are larger, but they play perfectly in BigBox. Just goes to show that where there's a need there's a way!