Lordmonkus

Try downloading and installing this https://www.microsoft.com/en-us/download/details.aspx?id=48145 Missing .dll files don't go on your desktop, they usually either go in the folder of the program you are trying to run that needs it or in C:\Windows\System or System32 folder. Installers though will put the files where they belong.

If your emulators are working outside of Launchbox then you probably have a paths problem with Launchbox, either to the emulators themselves or the roms.

My best guess off the top of my head is probably a missing rompath setup in Mame. You can check out my Mame tutorial here

no problem

Well if you aren't sure then yeah feel free to ask here on the forums or even on the Discord channel, always someone around willing to help out. Discord https://discord.gg/X3Cwsyw

Well here's a quick tip, when you get error messages like the ones you posted a quick google search for those specific messages will give you the answer. But I don't mind helping out where I can.

MSVCP140.dll is a Microsoft Visual C++ library. https://www.microsoft.com/en-us/download/details.aspx?id=5555 All of those errors are common Windows files that a great many programs require and are not directly emulator related. On a new install of Windows programs tend to be missing those but over time installing stuff installs them.

That's a Visual C runtime dll. You need to reinstall Visual C++ https://www.microsoft.com/en-us/download/details.aspx?id=48145

No problem.

Yup, just a missing direct x dll, reinstall direct x and restart your computer. https://www.microsoft.com/en-us/download/details.aspx?id=35 Also you don't need to upload pics elsewhere to upload shots to the forums, just dragging the picture file into your post will upload and post them in your post

If you can tell us what dll files you are being told is missing that would be a big help, it's probably something easily fixed with a download and install and probably not even directly emulator related.

The Vulkan core unfortunately is not very good, it may be good in the future but for now it is not. I have had really good luck with the GLupeN64 core though and I like it more than PJ64 and the stand alone Mupen but I did make a separate install of Retroarch just for it since it was only with a nightly build could I get it to work.

Been suggested and is planned. Hopefully sooner rather than later, I have pushed Jason for this feature more than I should for this feature as it is. lol

GLupeN64 isn't Vulkan but you may need to install a nightly build for it though. Weird about PJ64 not going full screen for you, should be just an option to have it load full screen in the settings.

Check the xml file in the error message and see if it has read and write permissions or just read.

Unless you got a backup like on another drive or a cloud backup I have nothing.

It's probably ok there. Out of years of habit I never install anything to that folder, in fact I rarely install anything but basic programs to C:\ drive. I tend to install big things like games and stuff to another hard drive all together. Just habit from the old days Windows 95 and 98 and its awfulness and how often it would need to be reinstalled made it good practice to keep important stuff off C:\.

It looks like your Launchbox folder is set to read only. Go to where you Launchbox folder is, right click the folder and then properties, then go to the security tab and change the settings in there to allow writing. I also highly suggest not having Launchbox in the Documents folder, put it on another drive if possible or right on the root of C:\ drive if that is not an option.

It depends. If you are unplugging and plugging in different controllers all the time this may make things more complicated depending on the version of Retroarch you are using. Apparently they are working on making this easier but the way I understand it right this moment (and I could be completely wrong) is when you are unplugging and plugging in controllers it messes with their ID number that Windows assigns them. Now if your controllers are always plugged in things become much easier. I have 3 controllers (2 for emulation) plugged into my system at all times, flight stick, xbox 360 controller and a hori fight commander. My 360 pad and Hori FC are my emulation controllers, I use the 360 for anything that requires and analog stick like N64 and PS1 analog games. Using the stable 1.3.6 build of Retroarch I have "per core configs" turned on and each core is setup with a specific controller. I simply loaded a game for the core and configured the controller for that core and Retroarch saved that configuration for that core.

With emulation the technically better an emulator gets the more processing power it requires. As emulators get more accurate which means the more games that run with fewer flaws you need more and more CPU power to achieve this accuracy. Look at Super Nintendo emulation for example, take ZSnes, Snes9x and HiGan (BSnes). ZSnes will practically run on a toaster (200 too 400 MHz Pentium) but it only runs about 50 games without issues. Then you get the Snes9x which requires way more CPU than ZSnes but way more games run properly on it. And then we come to HiGan which is virtually 100% accurate and requires a modern 3 GHz CPU to run it full speed but it runs every single game at or near perfection. This is why NullDC runs faster, while it runs better on lower end hardware Demul is the more accurate emulator and runs more games without problems. Your system should be able to handle Demul though, it runs fine for me with higher internal resolution. My system is an AMD 8350 @ 4 GHz, 16 gigs ram, GTX 970.

Oh, I thought with the save states you would still need the original rom. Ahh, I didn't know about that emulator but then again the 800 is something I don't even think about let alone worry about

The converted rom shouldn't won't ask for the mapper and I don't like to bother with save states plus this way it's a converted set of roms so if for whatever reason the save states get lost or corrupted like save states tend to do you still have a set of roms. As for the Atari 800 I don't know, I don't have any 800 games to try it out with.

What issues did you run into ? The emulator asking for which mapper to use ? If you got asked which mapper then you were still loading the original rom, you need to load the new rom that got generated. I converted my full 5200 set last night (90+ games) and re-imported them all and what I have loaded to test out works just fine.

Honestly I have no idea, personally I would recommend the GLupeN64 core in Retroarch over Mupen64plus for Nintendo 64 emulation anyways.

Let's get the first thing out of the way. No matter which way you to choose to emulate the Atari 5200 there are going to be issues. There are 3 choices of emulators, Kat5200, Mess (Mame) or Alitirra and each of them have their own quirks making each less than the perfect choice. Kat5200 is probably the easiest to get up and running and setup but it is ugly and it changes your monitors resolution when loading and exiting a game which people can find off putting and if you are on a multi monitor setup it moves windows around on the monitors. It also has terrible to non existent shader support. While it does have some screen effects to recreate an old TV look that is pretty much all it has, there are no CRT scanlines or anything else. See update #2 below. Kat5200 is now my recommended way to emulate the 5200 for most people. Mess (Mame) is the next easiest to setup and for the most part it is pretty good, it has good CRT shaders and easy to setup controls. There is a catch however which makes Mess (Mame) kind of suck, certain games have controller issues and this is baked into the emulator until it gets fixed. I have not tested every single game to figure out all the games with this issue but I can tell you that Moon Patrol and Pitfall have controller issues. Altirra is widely considered to the best way to emulate the 5200 but it is also the most complicated to get setup. The controller configuration is annoying but I did find a short how to on the Atariage forums here https://atariage.com/forums/topic/242107-altirra-26-xbox-360-controller-5200-mode/ Unfortunately the controller setup is the least of the problems when it comes to Altirra. The bigger problem comes when you want to load a game, when you load a game a popup window will appear asking for a mapper. If you don't pick the right mapper the game won't work and obviously in a frontend you don't want to have to pick a mapper each time you load a game. There is a way around this mapper problem however but it does involve some work converting your roms so they have a header with the information needed by Altirra to auto load the rom with the mapper bypassing the popup window. One option is a java program a user over on the Atariage forums made which lets you drag your rom files into the window and convert them and here is the link to it https://atariage.com/forums/topic/235118-atari-rom-maker/ I did find this to not be 100% though and not fully automatic, you had to pick the mapper for each game and if you don't know which mapper each game needs you still need to load the game in Altirra to find out. The defaulted recommended mapper was not always the correct one. There is one other way which also takes some time but it works. You can load your rom into Altirra and then using the Altirra UI you can save out a new rom file headered and ready to go. Once you generate all new roms you can then import those into Launchbox and they will load directly into Altirra without the mapper window. Here is the link to the Atariage forum where I found this information http://atariage.com/forums/topic/259866-help-with-altirra-271-and-pop-up-box-of-select-cartridge-mapper/#entry3648699 This is the process you have to go through: 1) Boot a ROM image in Altirra 2) Manually select the correct cartridge mapper in the pop-up dialog box 3) Once the ROM is running, use: "File" menu / "Save Firmware" / "Save Cartridge" 4) Save the cartridge image with header as a new file I found the best way to deal with this was to make a new folder to save your games out to after loading them in to Altirra. Converting all of my roms, about 97 of them, took me about 2 hours. Update: Altirra has been updated, as of version 2.90 it now has a built in database reducing the need to guess the chip type which should remove the need to go through the above steps. http://atariage.com/forums/topic/267797-altirra-290-released/ Update #2: Kat5200 has been updated and no longer messes with resolution, it also now has some support for some Retroarch GLSL shader files. I tested some of the CRT shaders and found Lottes is the one that plays best with it and looks as intended.