Search the Community

Hey everyone, I've been trying to set up Nintendo 64DD within Retroarch and I've gotten most games working. Therefore, I wanted to share what I've learned along the way. I'm using the mupen64plus next core with ParaLLEl RDP and RSP. As for the N64DD games, I'm using the original Japanese dumps, no translation hacks (I haven't tested those, yet), and no cartridge conversions. Dezaemon DD and F-Zero X - Expansion Kit are expansions, which need specific N64 roms to load. The rest of the games are standalone, but still need an N64 rom to properly load. I'm using Super Mario 64 all of them, except for Kyojin no Doshin (Doshin the Giant), which for some reason won't load with Super Mario 64. I'm using Air Boarder 64 for that game. What you'll need: 1. The Japanese BIOS file version 1.2 2. The Japanese N64DD disk games 3. The Super Mario 64 (Japan) rom 4. The F-Zero X (Japan) rom 5. The Dezaemon 3D (Japan) rom 6. Another random Japanese N64 rom (I'm using Air Boarder 64 (Japan)) So here's the set up: 1. For the Japanese games, the Japanese BIOS file version 1.2 must be placed inside "RetroArch\system\Mupen64plus" and renamed to "IPL.n64" (the .n64 file extension is important, the z64 file can just be renamed, no need to convert it in any way). 2. Import the N64DD games into LaunchBox (the files can be zipped, no need to extract them). 3. In Launchbox, go to manage emulators --> Retroarch and find the Nintendo 64DD platform. Under Extra-Command-Line Parameters add: --subsystem ndd %romfile% "PATH TO\Super Mario 64 (Japan).zip" This should load most of the standalone games. 4. Go back to your N64 DD platform and find the Dezaemon DD game. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\Dezaemon 3D (Japan).zip" 5. Go back to your N64 DD platform and find the F-Zero X - Expansion Kit. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\F-Zero X (Japan).zip" 6. Go back to your N64 DD platform and find the Kyojin no Doshin game. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\Air Boarder 64 (Japan).zip" 7. For Sim City 64 to be able to go past the title screen, make sure that in the mupen plus core options, the follwoing settings are set: "Framerate" must be set to "Original", "Fullspeed" causes a black screen past the initial logos. Under "Pak/Controller Options", if player 1 (and possible the other players?) has a rumble pak inserted, it also doesn't work (same as above). Memory pak works. That's it. I've not tested playing much, but as far as I can tell, this is how to get almost all of the games working. There are 2 roms, I'm still having trouble with (maybe someone can offer a solution?): 1. The Randnet Disk does launch, but once the title screen shows "press start", nothing happens. Pressing start on the controller won't do anything. I know that this isn't a game, but it would still be nice to enter the program, just out of curiosity. 2. Kyojin no Doshin - Kaihou Sensen Chibikko Chikko Daishuugou (Doshin the Giant: Tinkling Toddler Liberation Front! Assemble!) is an add-on / add-in for the Doshin the Giant disk. It does Launch, but it won't go in-game. If I understood correctly, in order to get this game to work, you'd need to be able to swap between the Doshin the Giant disk and this add-on disk, and I don't think this is possible with mupen. If anyone know of a way to do this, please share! I hope this helps someone!

UPDATE: In order for CDi emulation to continue working, you need to get the updated cdimono1 bios file from mame. It was updated some time ago and CDi emulation on newer mame versions without the updated bios file is broken. This has been quite the ordeal, but I finally got it working, so I thought I'd share what I found out. There is some conflicting information online, so it took me a while to figure it all out. I found this discussion / tutorial written by people far more capable than me. My tutorial is based on that. I just wanted to write a more comprehensive tutorial and give some additional info (also this tutorial is technically for andriod devices, so I think it should be stated that it works for PC as well.) https://www.reddit.com/r/EmulationOnAndroid/comments/980mar/tutorial_phillips_cdi_on_android/ 1. What you need: 1.1 Retroarch's Mame core (without year tags) 1.2 This Archive: https://mega.nz/#!0OQ2zASD!UKoefHzpnsHBj79MdYRMWzdZYSv6kpPvxud0DmSSX3A (I hope I'm allowed to post this here) 1.3 CDi roms (I only tested the .chd format, but I'm pretty sure that cue/bin will also work) --> Keep in mind that there are many CDi roms that flat out don't work (more on that later) 1.4 Philips CDi bios files (mainly "cdimono1.zip", but I also have "cdimono2.zip" and "cdibios.zip". I don't know if they are needed for any games though) --> I cannot provide links to these bios files. You'll have to get them on your own. 1.5 LaunchBox, of course. 2. How to get your CDi games running: 2.1 Navigate to your main roms folder and create a folder called "Philips CD-i" (You can name the folder whatever you like, I just used the name that LaunchBox uses). 2.2 This is important: Inside the "Philips CD-i" folder, create another folder called "cdimono1". It's very important that you use this exact name. It doesn't work otherwise. 2.3 Copy all of your Philips CDi roms into the "cdimono1" folder. 2.4 Also copy your Philips CDi bios files into the "cdimono1" folder. 2.5 Download the archive from 1.2. Inside this archive you will find two more archives. Open the one called "CDI_blank.zip". Inside this archive you will find many different empty, "dummy" .zip files. These files have shortened title names for the CDi games (much like Mame roms). You'll need them so the Mame core is able to load your roms (more on that later). Copy all of these empty .zip files into the "cdimono1" folder. --> To sum up, in your "cdimono1" folder there should now be: your Philips CDi roms your Philips CDi bios files your empty .zip files 2.6 Open the archive from 1.2 again, but this time open the second archive within it called "RetroArch.zip". You don't need everything in here, just one specific subfolder: Go to "Retroatch --> system". In here, you will find a folder called "mame". Take that folder and put it in your own Retroarch directory in "YOUR_PATH\RetroArch\system\". 2.7 Download Retroarch's Mame core (without year tags) and leave all the settings at default (you can change the resolution if you want to) --> This is where misinformation held me back. There are many tutorials which tell you to change various settings, but believe me, you must keep the default settings. 2.8 Open LaunchBox and import the empty .zip files from 2.5. Important: You cannot import your CDi roms directly, it doesn't work. Unfortunately, this means that you will later have to rename all your imported roms with their actual names manually (There maybe a way to automate this, but I don't know, I just trail-and-errored my way through this). Also important: when importing, make sure that you choose retroarch as your emulator for the Philips CDi platform. --> you might want to start with just one file at first, just to make sure everything works. You can uset Hotel Mario ("hotmario.zip") for this, since I can confirm that this game actually works. If you have done everything correctly, you should have a game called "hotmario" in your LaunchBox. You can rename it to "Hotel Mario" and get all the metadata for it. 2.9 In LaunchBox, go to "Tools --> Manage emulators". Select retroarch. Go to "Associated Platforms", scroll down and add a new Associated Platform called "Philips CD-i". Choose "mame_libreto" as your core. Important: Don't add any "EXTRA Command-Line Parameters", despite what you might have read elsewhere online. --> You can now run Hotel Mario in LaunchBox and if you have done everything correctly, you should see a light blue screen. Wait a few seconds. You will then see a grey Philips CDi bios screen. Use your mouse and click "play". The game should now start. If it starts, you can import your other games. Keep in mind however, that not all of them will work. To find out which games are not supported, navigate to "YOUR_PATH\RetroArch\system\mame\hash" open the "cdi.xml" (here you can also find out which actual games the empty .zip files correspond to.) If it says something like "<software name="7thguest" supported="no">" that means that this specific game will not work, so you don't need to import it. 3. Further configuration (optional, but very much necessary in my opinion): 3.1 Since you most likely want to use a controller and not your mouse + keyboard, you'll have to map the controlls within the Mame GUI to your controller (I use an Xbox One controller). Once your game is up and running, hit TAB on your keyboard to bring up Mame's GUI. Navigate to "Input (this Machine)" and map the inputs to your controller like this: Mouse Button 1: Joy 1 B or A (your choice) Mouse Button 2: Joy 1 Y or X (your choice) Mouse X Analog: Joy 1 LX (press your left analog stick to the right) Mouse X Analog Dec: LEFT (press left on your D-PAD) Mouse X Analog Inc: RIGHT (press right on your D-PAD) Mouse Y Analog: Joy 1 LY (press your left analog stick up) Mouse Y Analog Dec: UP (press up on your D-PAD) Mouse Y Analog Inc: DOWN (press down on your D-PAD) Now go back and navigate to "Analog Controls". Reduce the two sensitivity settings drastically. "10" is a good point to start, but I found that even lower values ( 5 or even 1) are better for some games. Mouse X Sensitivity: 10 (your choice) Mouse Y Sensitivity: 10 (your choice) 3.2 Now your controlls should be mapped to your controller. However, when I did this, characters in games would start moving by themselves. This is because for some reason, the deadzone seems to be too small. If you experience this, do the follwoing: Once your game is running, press F1 to bring up retroarch's GUI. Navigate to "Settings" --> "Input" and scroll down to "Analog Deadzone". change the value from 0.0 to 0.5 (this worked for me). Important: you don't want to change this setting for all of your games or even for all platforms using the same mame core. You want this change to be in effect just when you play CDi games. So head back to "Quick Menu" --> "Overrides" and hit "Save Content Directory Overrides". This will save the changes you made just for CDi games. If the issue isn't solved for you, try increasing the deadzone value. Congratulations, you are now done! You are now able to experience a bad Mario game and three bad Zelda games (Why did I spend so much time on this?) Jokes aside, I hope this helps someone.

It took a little investigating to find a pdf viewer that supported both full-screen [upon opening] and a minimal footprint (sorry new Foxit reader versions). It turns out SumatraPDF does all of this with a few quick settings to set. Download (installer / portable zip , 32-bit / 64-bit ) I used the portable version. Put it somewhere you don't mind making it's permanent home. Run it once to create the necessary settings config file. Open the SumatraPDF-settings plain-text config file. Ensure the following settings are set: Set Esc key to escape the program EscToExit = true Under "FixedPageUI"... comment out the background line to turn off what is essentially a colored overlay on the pdf #BackgroundColor = #ffffff The only way to set the actual background behind the pdf is to set the following. I set a slight gradient but a single black #000000 can be set as well. GradientColors = #111111 #000000 A single whole page at a time as the default view DefaultDisplayMode = single page Set fullscreen as the default WindowState = 3 Obviously you'll need to set this as your default PDF viewer. This isn't tremendously difficult, but I'm sure others are looking for a possible solution to a front-end "hands-off"-ish manual viewing in BigBox. Esc is then set for exiting and the arrow keys will change pages. Set these with your controller(s) and your front-end solution should be good until there's a local pdf solution.

I had posted some instructions on this a while back but realized this is probably worth posting into a separate tutorial thread for future reference rather than leaving buried in another random thread. ParaJVE is a Vectrex emulator with built-in bezels and screen overlays, which are really necessary to get the whole Vectrex experience: Setting these up in LB could be a bit of a pain because in order for specific games to be launched via command-line, the appropriate game name had to be sent for each one via -game=[the game title] So I extracted all the names of the game titles that ParaJVE looks for, and created blank files for them so that they can be imported into LB as "roms". They're not actually roms, they're just telling the emulator which game to start. You can find them below: Game IDs.zip These are separated into different categories in the same method that they're separated in the ParaJVE UI. Some of these probably won't be of much interest to most people as there are things like Tech Demos in there. In any case, choose the categories that you want to import, place them somewhere on your computer. First let's setup ParaJVE itself in LB. To start, your emulator entry for it should look like this: Add your Vectrex platform (named "GCE Vectrex" if following the LB GDB format) to the associated platforms tab and check to use as the default emulator if you wish. Now, drag the folders for the Vectrex game IDs into LB and indicate that they're Vectrex games. When you get to the "custom options" part of the import wizard, be sure to select the "use folder names instead of ROM file names for game titles" option, otherwise the game titles will be wrong. Let the import complete and now they can be started and the appropriate game will launch. You'll probably want to change the controls once the emulator starts. You can do this by going to Controls -> Key Mapping and then changing the Joystick #1 and Joystick #2 controls as you see fit. Once this is done, go back to your emulator entry for ParaJVE and change the command-line parameter to the below if you want the games to start in fullscreen with no menu: -fullscreen=TRUE -menu=OFF -game= And that's it! NOTE: Java is required in order for ParaJVE to work.

The retrolust bezels for MAME are pretty straigtforward; however, the bezels for retroarch are little bit more confusing to set up. I can apply the bezels okay, but I'm having trouble changing the aspect ratio and the position of the game screen. Apologies for creating a separate thread. The retrolust post is like a million pages long, and it was difficult to wade through them

Alternative Frame for ArcCabView BGFX + how to configure your own frame View File For the purpose of bezel reflection in MAME, ArcCabView is a GODSEND, but I always thought the frame was too thin and too light when using Lights Out bezels.... so I made a wider darker one! The screenshots showcase the frame using different bezels. artwork and bgfx folders go into your MAME directory, overwriting two files: ArcCabView.json and frame.png (⌐⊙_⊙) How to use your own custom frame so it lines up properly with the game screen (using the default ArcCabView preset): 0. If not already installed, download ArcCabView_MAME_BGFX_Chain_2.2d and extract into your MAME directory (probably backup artwork/bgfx and bgfx folders in case you want to revert changes) 1. replace frame.png located in mame/artwork/bgfx/chains/ArcCabView with your custom image 2. load up a game in MAME, then press `/~ (onscreen display hotkey) and adjust Frame Size X, Frame Size Y, and Corner Size so the game screen fits the frame to your liking. 3. Exit game, and open the .cfg file for that rom in mame/cfg 4. Also open the ArcCabView.json file in mame/bgfx/chains/ArcCabView 5. find the adjusted values in the .cfg file and copy them into the .json file. The values in question are highlighted in the image below: 6. Save the .json file. 6½: Optionally, repeat steps 1-6 until satisfied... 7. ಠ_ರೃ P R O F I T. I don't see a lot of mentioning of ArcCabView here, so maybe some MAME users will find it to be a decent (or more subtle) alternative to Mega Bezel Shaders for Retroarch, which I use for other platforms anyways. I'm just very attached to MAME for arcade... Submitter d66dle Submitted 03/11/2025 Category Platform Bezels/Overlays  

I was asked how I create game specific color layouts and call outs using Ledblinky and LaunchBox. This is my tips and tricks and there may be other ways to achieve the same or better. Comment and share! Sorry for the crunchy audio and bad audio mix while BigBox is running. For some reason the audio got funky when BigBox is running. Probably because the computer was doing 20 things at once. I also noticed the on screen mame setup stuff is a bit hard to read due to adjusting exposures, etc. The audio explains it pretty well. Hope this helps and GAME ON! LedBlinky Custom Layouts Tutorial *Sorry for the really low audio. I thought the mic was clipping but it was BigBox audio recording issue I had mentioned above.

I have made a quick tutorial on how to make 3D PC/Windows Game Cases (as requested) in Photoshop. I have been told the Action File also works in Elements. Any size cover can be used as long as they are full size covers (not Just the front of a cover). Please note that Because the action file is expecting to save to my directory on my PC changing the save location in both parts of the Action file may be necessary. The Action file is attached. PC DVD BOXES.atn

Hi everyone, I'm trying to put the ps2 core into launchbox through retroarch, but even though I already have its core installed correctly in retroarch, it doesn't recognize it when adding the emulator. Is there any way to enter it? My goal is to only use Retroarch via Steam with all emulators, this is possible?

Here's an exploit in the new game Starfield that lets you keep getting items.

Have you ever wanted to launch the GameCube menu / dashboard using BigBox? Well now you can with this easy to follow video tutorial I made for newbies who are visual learners! Check out the youtube video link below:

Have you ever wanted to launch the PS2 menu / dashboard using BigBox? Well now you can with this easy to follow video tutorial I made for newbies who are visual learners! Check out the youtube video link below:

Have you ever wanted to launch the PS3 menu / dashboard using BigBox? Well now you can with this easy to follow video tutorial I made for newbies who are visual learners! Check out the youtube video link below:

Description: Tables for Pinball FX2 on Steam are treated similarly to DLC for other games. Therefore, the tables do not have their own launchers in Steam, and are chosen after starting up the main game. However, the following will describe how you can enter each Pinball FX2 table as an individual game in LaunchBox. Note: You may need to get a code from Zen Studios to enable command line support with Pinball FX2. There is a link within the game that will send you to the appropriate form, or you can go to it directly, here: https://blog.zenstudios.com/?page_id=5981 I don't know if this step is necessary, as I had already received a code before I imported the tables to LaunchBox. So check there first if the command line arguments aren't working. Steps: Optional: Navigate to Tools -> Manage Platforms from the LaunchBox menu bar and click the + Add... button to add a new platform. Optional: Enter the following metadata: Title: Pinball FX2 Release Date: 05/10/2013 Developer: Zen Studios Category: Pinball or Arcade Images: (See Image 1 for Clear Logo) Optional: Click the ✔ Ok button and you now have a platform for your Pinball FX2 tables. Note: The previous steps may not be necessary, depending on how you organize your platforms. The Pinball FX2 tables can be added to the platform of your choice — this is just the setup that worked well for me. Navigate to Game -> Add from the LaunchBox menu bar, or press Ctrl+N. Enter any necessary metadata in the Details section (Image 2). Since these titles do not exist as separate games, they are not currently in the LaunchBox Games DB, so I'm unaware of an easy way to scrape metadata at the moment. Beneath the Details section, within the Launcher tab, click the Browse... button next to the Application Path textbox. Note: If you see ROM File (Emulation is enabled) instead of Application Path, you will need to navigate to the Emulation tab, and uncheck Use an emulator to play this game. Navigate to your Steam install folder, select the file named Steam.exe, and click the Open button. The Application Path setting should now be set to something like: ..\Steam\Steam.exe Next, in the Application Command-Line Parameters textbox, enter the following text: -applaunch 226980 "TableName.pxp" Replace TableName in the sample text above with the name of the table you are adding (See below for the list of table names and command line parameters). This parameter will tell Steam to launch the app with the id of 226980, which happens to be Pinball FX2, and it will pass the name of the table we want to run to Pinball FX2. Click the ✔ Ok button and you should now see the game added to your selected platform. Note: Since we are passing the name of the table file to Pinball FX2 through the command line, and not the table file itself, we cannot use the usual Tools -> Import -> ROM Files... method. Images: Pinball FX2 Platform Clear Logo: Adding a Pinball FX2 Table: Table Names and Command-Line Parameters: Note: The names of the tables can be found by navigating to your Pinball FX2 directory within your Steam directory. It will be at the following location: Steam -> SteamApps -> common -> Pinball FX2 -> data_steam Ignore any of the files that are in lower case (game_cfg.pxp, gui.pxp, etc.), as well as the PTSData.dat file, as these are not table files.

Retroarch Version: 1.3.6 Mame Core: MAME 0.174 (The core labeled Arcade (MAME) in the Core Updater) Steps: Open Retroarch and pull up the Main Menu (Press F1 if you are in-game). Load the Mame Core if it is not already loaded (check the bottom left of the screen for the currently loaded core). Navigate to Main Menu -> Quick Menu -> Options. In the Options menu, turn ON the following options (Image 1): Hide nag screen Hide gameinfo screen Hide warnings screen Navigate back to the Main Menu and select Save Current Config. Now, when you play an Arcade game with Retroarch, it will begin loading the rom immediately. Note: The nag screens, warning screens, and info screens are the screens that display before the rom is actually loaded (Image 2). These screens usually require a button press before the process is allowed to continue. These settings will not remove the arcade startup screens, display test screens, RAM check screens, hard disk load screens, etc. Images: Settings to change: Nag screen and gameinfo screen example:

There is one prerequisite to playing Atari5200 games via emulator – and that’s the BIOS file. This ROM file can be found floating around the web, so it is up to you to obtain this file. It’s not too hard to find. Next up, we need to get an emulator that can make this all happen. One such emulator is Kat5200. This can be googled Now, you need to find a nice convenient place on your hard drive and create a folder for all of your Atari 5200 needs. In that folder, create a folder for all of your ROM images and another for the Kat5200 emulator. Now (assuming you downloaded the binaries archive), drag and drop all of the Kat5200 files from the archive folder you downloaded into the Kat5200 folder you made. Now, place your 5200 rom file and place it somewhere in the Kat5200 emulator folder (it’s easier to find in the emulator after this way). Now, open up the emulator by double-clicking on the Kat5200.exe file. You’ll probably get wizard that’ll guide you through the set-up process, but if you couldn’t get things to work, no worries, we’ll show you what you need to modify outside of the wizard. The first thing we need to do is get the emulator to detect the 5200 ROM BIOS file. For that, you click (or hover) your mouse on the “Machine” drop-down menu I’ve highlighted above. In the menu, you need to click on “Bios files”: In the new screen, you’ll see a line for the Atari 5200 BIOS. Simply click on browse and use their built-in browser to find your BIOS ROM file (you can either use the “Up” button or double-click on the [..] line to go up a directory if need be). Once you have found the ROM file, click on it to highlight it and then click “Load”. Then, click on “OK” to leave the BIOS “window”. Cool! You’ve now pointed the emulator to the BIOS file needed to run the games! Now, we need to find out the controls. Atari 5200 controllers, weirdly enough, look like large telephone’s complete with a number pad. This emulator will reflect that. To tweak the controls, simply click on the “Options” drop-down menu and click on “Input”: You’ll get a new window that looks something like this: To find out what each button does, click on the button on the left hand side (i.e. Top Button). On the right hand side in the line that says “PART NUM”, you’ll see a box with what key on your keyboard corresponds with the virtual controller. If you want to change this, simply click on the “Auto-Detect” button. A window will prompt you to press the key that you prefer to use. Press the key and not only will the window will disappear, but the new key will be featured in the “PART NUM” box. When you are done configuring your controller, click on the “OK” button. The next part is to find out how to save and load states. This can be found by clicking on “Options” and “User Interface”: In the new window, you’ll notice that configuring these other options is much like setting up your virtual controller. There is one thing to note, however: there is a line “Device Num” is the key that you hold. The “Part Num” line is the key you press on your keyboard. So, for loading save state 1, you hold down Alt and press “1” as per the default. See below screenshot for this: Again, use Auto-Detect to change the keys. Generally, I found the default settings to be sufficient, but that’s just personal preference. Finally, you get to load a game. Before you can load a game in the emulator, you have to make sure the game’s are not in a zipped or otherwise compressed archive. If you try to load a game in, say, a .7z archive, the emulator will simply crash after the Atari loading screen, complaining of a CPU crash. So, if your game is in an archived format, extract the .bin file in your ROMs folder first and load the .bin file instead. While the emulator can detect all of the files in the directory, it can only load certain kinds of files as a game. Now, go into your emulator and click on the “File” drop-down menu. Next, click on “Load Rom”: In the new window, highlight the .bin file of the game you want to load and click “load”. You’ll go back to the previous screen, but the game is loading. If you feel like it’s taking to long to load, move the mouse around a little. Usually, by that time, you’ll get to the Atari loading screen. When you want to exit the game, simply hit the “Esc” key on your keyboard. You’ll be taken back to the menu screen. You can go back to where you left off in the game by simply going into “File” and “Back to Game”. When you are done with the emulator, just go to “File” and “exit” That’s it! Happy gaming! FAQ I’m trying to get the game to start, but nothing seems to be working. What’s going on? Some games require you to hit a button to tell it that you are ready to play. By default, the F10 key will get the game started. This depends on whether or not you’ve changed the default keys (in which case, hit escape and look at the config file to see which of those is the Start button on your keyboard. I have a game that keeps crashing even though it’s not in an archived format. What’s going on? I found that rom images labelled “prototype” don’t do so well with this game. If it’s labelled “proto” or “prototype”, it might not be supported by the emulator. The game still crashes and it’s a regular ROM image? Could be the ROM in question. It could also be unsupported. Either find a different ROM or a different emulator in that case. The game looks really small and it’s hard to see. How do I make it bigger? In the emulator screen, go into “Options”, then “Video”. On the lower right hand part of the screen, you’ll see a pull down menu next to the word “Zoom”. I found 2x Zoom works comfortably well. #credit: Freeze

¡Qué tal! Muchos solicitan ayuda en español, por lo que estoy dispuesto a echarle la mano a quien no sepa algo siempre y cuando yo sepa acerca de ello. En esta ocasión veremos un problema normal: ¿Cómo añado un emulador que no está en la lista de LaunchBox? ¡Simple! Primeramente, nos dirigimos a la pestaña "Herramientas", y luego a "Gestionar Emuladores". Nos mostrará la lista de emuladores que tengamos vinculados. A continuación, seleccionamos "Añadir". Vamos a "Nombre del Emulador", y escribimos el nombre, en mi caso, DesMuMe, el cual usaré para emular NDS. Luego de ello, seleccionamos la ruta del ejecutable (.exe) de nuestro emulador. Luego de ello, vamos a la pestaña "Plataformas Asociadas". En la misma, en la casilla "Plataforma Asociada", ingresamos el nombre de la plataforma, en mi caso, Nintendo DS (tiene que estar correctamente escrito), y checamos con palomita la casilla de "Emulador Predeterminado". Finalmente, damos en OK, y ¡listo! Ya puedes usar emuladores no listados. Espero y este pequeño tutorial haya sido de su ayuda. Add Blog Entry Manage Blog

Most importantly, I got the idea from FASM's topic posted a while back so a lot of this credit goes to him/her. However, I noticed it only halfway functioned and didn't really do what I wanted it to. An excellent start though! I have created a video with the tutorial in the description over at but for those who just want to get into it, here as follow. TUTORIAL FULLSCREEN MANUAL SUPPORT, BIGBOX Go here http://www.mediafire.com/file/hzgyg8awfbzd8dn/SumatraPDF.exe and get Sumatra PDF. Go here http://www.mediafire.com/file/dnb7v7wdfwl31ue/Chrono+Trigger.pdf and get a test manual if you want. - Put SumatraPDF.exe anywhere you'd like, I chose a folder I named SumatraPDF inside my LB folder. - Click SumatraPDF.exe one time, it will make a txt file called sumatraPDFsettings, open this file (default should be in notepad). - At the very top is a line that says EscToExit, change this to True. This will let you instantly exit with the ESC key. - Hold CTRL + F and search RememberStatePerDocument and change this to = false (manuals will be restarted when reopened) - Do the same with DefaultDisplayMode and change it to = single page (this will fix seeing the bottom page of the next page like seen in the Final Fantasy manual in the video.) - Do the same with Window State, it's right under the last line. Change the number to = 3 (this is borderless fullscreen) - Save the document, exit. - Right click a .pdf file on your computer or use the one I included (most manuals are in this format) and click 'open with' then 'choose another app'. - MAKE SURE to click 'always use this app to open .PDF files' FIRST, even before selecting one, do that now. - click 'show more' then scroll to the bottom, click 'use another app on this PC' - Locate where you put the SumatraPDF.exe and select it. - It should either open the manual in fullscreen OR go back to the app menu with SumatraPDF added to it. If it went back to the menu, click SumatraPDF and click 'okay' - TEST it! The manual should open in fullscreen, move with arrow keys. CONTROLLER SUPPORT FOR MANUALS, BIGBOX Go here *link removed* to download Controller Companion. - Install Controller Companion where ever you like. I put it in it's own folder called Controller Companion inside my LB folder. - For the purpose of this tutorial, I am using a Wireless Xbox One controller. Connect your controller and open Controller Companion. - If it opens up on screen, close it. If not, right click the icon in your taskbar and open settings. - For right now, leave balloon tips and play sounds on. Turn on Start Controller Companion when Windows Starts Up to On if you use Big Box a lot. There will be an option later to turn it off with your controller when not using it. - Click the Bindings tab. Now this is a personal preference, I like to clear every binded button on my controller, you can do this by selecting the button icon and clicking 'nothing'. - Select the Left D-Pad button and make it the left arrow key. It is located in 'keyboard' then 'navigation and edit'. Do the same with the Right D-Pad button and make it the right arrow key. - Click Apply and close out of the window. - TEST it! Open notepad, type a few letters/numbers and use your controllers D-Pad to see if you can move between the letters and numbers with it. If it doesn't work, try again after holding the SELECT/BACK button and pressing the START button. FINAL STEPS, YAY! - Your manuals should be located in your LaunchBox folder under 'manuals' inside the system of the game. They should be named exactly as the roms name. For example, if Final Fantasy 3's rom is named 'Final Fantasy 3 (USA) then your manual for that game should be named 'Final Fantasy 3 (USA).pdf'. - Open Launchbox and go to options. Go to 'controller automation' turn this on and make the buttons as so. Hold Button = START and Close the Active Window = SELECT or BACK button. - TEST it! Go to a game, select a manual and see if it opens in fullscreen. If not, hold the SELECT/BACK button and then press the START button. To close out of a manual and any running emulator currently in Big Box, hold the START button and press the SELECT/BACK button. SUCCESS! A final note, Controller Companion can be active in every single window applicable in Windows.To toggle it between off and onat anytime, hold the SELECT/BACK button and press the START button. It can do many more things than just arrow keys such as toggle virtual keyboards and such. There are many detailed tutorials on Google and YouTube. Enjoy and support the LB BB team! Hopefully in days come a true plugin will be built for BB but for nice, this works just fine! Also, forgive me for making another topic like this a couple weeks ago, the last one didn't have a tutorial and people were asking me. I'm not trying to showcase my video on YouTube, rather, I am trying to showcase it I guess Anywho, much love and LBBBFTW!

Requested tutorial last week sorry it took so long to make it... included is exclusive Nox App PLayer PDF user guide 1. you will need one or 2 programs #XPadder or #JoyToKey for this tut I am using Xpadder because I have a wireless xbox 360 controller use whichever you prefer... Make sure the controller is plugged in and turned on... lol 2. Open any game of your choice inside of Nox 3. click the option in left panel that looks like a joystick called #controller configuration 4. if your device not there click refresh until it appears then hit connect... 5. select a game and get a feel for where you need to create virtual emulation buttons for. 6. once you have that done click upper right option in Nox panel called #Simulate Touch control 7. place the virtual d'pad somewhere on the game that won't be in the way... 8. you can either simulate your keyboard with WASD or controller with up, down, left, right on your dpad. 9. after you are completely done click the save option important! 10. this method applies to each game you play no matter what, you can even emulate buttons to navigate and use Nox easily! Nox-APP-Player-FAQ-20150812.pdf

I have worked through the tutorials on YouTube for theme creation but cannot add an animated gif to the theme I am making. despite several attempts I cannot get the animated gif to work. I have added the required line to the user control section on the view. With this line in place it will then accept and recognise the <image gif: tag. However, when I try putting image behavior after the tag it is not recognised as a valid property and neither is animated source. With these in place I get an error notification and the view does not load. Any ideas what I am doing wrong or what I have missed?

Hi im a newbie and have got my heard round most things and have bought a mic to use the voice feature so i can say opn ps2 etc, however i cant get this to work and cant find any tutorials! I have ticked the box saying activate and it says it has activated but what next? what settings? I have tried everything!! The mic works and has been tested on windows 7 and is calibrated but what now!! Thanks guys for any help at all, i really want to integrate the voice recognition feature!!! Thanks again folks

I know there are videos out there already but most of them are un clear so I did my own version. 1. first open up Dolphin emu and select a game you wish to add AR codes to 2. once you have the game right click and select properties 3. select 3rd box inside properties which is AR Codes 4. quite a few games come preloaded with AR Codes but for those that don't you can add your own. 5. click the add button botton right corner of box. 6. make sure what ever code you add is correct or dolphin will prompt you the code is incorrect. 7. once you have everything added close properties box and select the game to test your cheats 8. once game loads select tools then cheat manager in drop down menu of dolphin 9. selct the cheats you just added and hit apply but don't close the box or cheats wont work!

After an "argument" in the launchbox discord, i did some googlefu and found out that dosbox daum has the option to mount zip files. @Zombeaver promptly tested if it worked properly and surprisingly it does So here is a guide on how to run zipped DOS-Games. Download DOSBOX Daum from http://ykhwong.x-y.net Unzip (DOSBOX Daum, not yourself) Make 2 folders in the unpacked dosbox named "Data" and "Games" Copy your Games in .ZIP format into the games folder Start dosbox and type: "mount c Data:Games\YOURGAME.ZIP:/" replace YOURGAME.ZIP with your zipped game name, i'll use LBA.zip (little big adventure) here: Start your game as usual: Success You'll have to keep your isos in a seperate folder if you have to mount them for games that need them (Daggerfall, Little Big Adventure, etc.) and there are probably a few other problems and glitches but so far it works pretty good.