Lordmonkus

There's the difference then. In your Associated Platforms you don't have a Nintendo Game Boy but you do have a Nintendo Game Boy Color. Either change the name of the platform itself or the associated platforms one to match.

Is your platform that you see in Launchbox named the same as in the Associated Platforms window ? Nintendo Game Boy Color A difference in the names will cause loading problems. Check for spaces.

Thanks.

@Retro808 would mind please posting this script over in this thread I just made to collect useful scripts like this ? And if you could provide a short description of which buttons exactly on the X-Arcade Tankstick this uses that would be awesome too.

I want to have a single thread for this so please share your useful and interesting AHK scripts here. Provide a short description of what the script does put the script in the post using the code function (the <> at the top of the post box). Launch Higan in fullscreen mode since not all versions of Higan has a command line parameter to do this: #NoEnv Sleep, 3000 SetKeyDelay, -1, 110 Send {F11} Return Universal close emulator with the Escape key, useful for ePSXe: $Esc:: { Process, Close, {{{StartupEXE}}} } Hide your mouse cursor for certain emulators that don't hide your mouse, change the numbers to match your monitors resolution: MouseMove, 1920, 1080 Here is a script from @Reynbow that closes out the Higan emulator properly so that it doesn't lose your save game data. $ESC::WinClose, ahk_exe higan.exe

This indeed sucks man. I hope you don't become a total stranger around here.

The additional apps can handle this if need be. I believe (I say believe because I use m3u files) when you import multiple CDs of the same game Launchbox automatically compacts the disks into a single entry with their additional app for each disk. Another way to handle disk swapping for PSX or Sega CD is to use m3u playlist files for emulators that support it (ePSXe does not) like Retroarch or Mednafen. You can then swap the disk in the RA UI or use of hotkeys.

In most cases the most common command line parameters are auto populated but of course there are so many emulators there may be some missing. Also depending on the emulator it may just be a setting in the emulator itself and not have a command line parameter. Snes9x uses the command line parameter: -fullscreen Mame also uses: -fullscreen if I remember correctly but I just set mine to load fullscreen in the mame.ini file. Nestopia will load fullscreen if you press alt+enter to put it in fullscreen first and then just close it out with alt+f4 or your controller combo you set in Launchbox if using the premium version. It will remember that it was fullscreen the next time you load it. I just tested this to make sure since I don't use Nestopia other than testing purposes like for posts like this If you have any specific emulator questions and fullscreen feel free to ask and we will do what we can to get you the answers you need but keep in mind it can be on a per emulator basis and even version difference can change how and emulator can be loaded in fullscreen mode, Higan is a perfect example of this. We do have some workarounds for it though if required.

Well even the 2 most popular NES emulators (Nestopia and Fceux / Fceumm RA core) are only approx 83% at best on accuracy tests according to http://tasvideos.org/EmulatorResources/NESAccuracyTests.html When it comes to commercial use emulators for specific games like the NES Classic or Nintendos eShop games they use a basic emulator and hacks to get each game looking and functioning correctly. They don't care about getting accuracy, they take the same approach as emulator development of modern systems such as Cemu. Get the main games looking and functioning properly and worry about accuracy later. The only difference is Nintendo doesn't care about future compatibility and accuracy, if they add a new game they will simply patch in new hacks as needed.

Glad it worked out for you.

This is a feature of Retroarch and other compatible emulators with the retroachievements website This is not a Launchbox / BigBox feature outside of the emulator itself supporting it.

Genesis Plus GX doesn't do 32X, for that you would have to use the Pico core.

If you cherry picked out rom files you could be missing parent roms required for that specific rom to work. Those games you listed are all Capcom so it could be the Qsound bios file and the 186 version of Mame made a change to that Qsound bios so you would need an updated one.

This is neither a shocker or surprise really.

Yes

The Retroarch Mame core (the latest one without a year in its name) works just fine as long as you have a relatively up to date rom set. The older Mame cores (one with a year in the name) are still problematic. You can set a "main control" scheme that is the default controller setup and then you can adjust on a per game basis if needed. What do you mean by "actual controllers" ? What sort of errors ? It could be an incompatible rom. I bounce back and forth between stand alone Mame and the RA core for my arcade stuff. Right now they are very comparable with some very minor differences which each person may or may not care about. For example stand alone Mame is easy to have hiscore support but the RA core version I could not get working. I know @Zombeaver uses Retroarch Mame for his arcade emulation where I mainly stick with stand alone.

Jeez, well first off welcome to the forums and Launchbox where there are plenty of us here willing to help out where we can. However you are starting off with an extremely broad and open ended question. I would star first by deciding what systems you want to emulate and then figure out which emulators will work best with your GPD Win. Because of its limited hardware specs you will have to keep some expectations in check. Then you will need to decide what games you are wanting to play and obtain them and that is something we cannot help you with because of the legal issues surrounding roms. You can find lots of video tutorials on the Launchbox Youtube channel found here https://www.youtube.com/channel/UCSIht6UXIEXIgz4eXAEShxA/featured. Beyond that if you have any more specific questions feel free to ask away. We will try and help out where possible.

Nice guide. Added it to the Guides & Tutorials sticky.

I use a stand alone version of Mess for my Colecovision, version 177 to be precise and the bios go in the \roms\ folder in my Mess folder and like @DOS76 you need those command line parameters. There are a couple of ways to get this stuff working especially with Mame but this was just my way to get it working.

Yes. coleco.zip 11.0 KB colecoa.rom 313 10031-4005 73108.u2 Those are the 2 files in the zip.

Mess / Mame (I use Mess) is the best way I found to do Colecovision and I haven't touched any Intellivision stuff at all so I cannot help you there.

You are probably correct in that it's the adapter if the PS3 controller is fine. I have never used any adapters for connecting a controller so I have zero experience with them to say one way or the other.

Retroarch once configured is extremely low input latency but depending on settings can be high. Check out more on this subject in this thread here on the Retroarch forums: https://forums.libretro.com/t/an-input-lag-investigation/4407/451 Most notably look for posts by the user Brunnis, he did some amazing work testing and essentially RA properly configured is only 1 frame more input lag than a real SNES on a CRT which is essentially nothing.