Lordmonkus

Is it recognized by Windows as an actual controller or a keyboard ? If it's a keyboard go to the Options screen then Keyboard Mappings and remap your buttons in there.

Well I will just start out by saying that the "recommended emulators" are badly outdated (need to be updated) and are only a guide and you can use any emulator you prefer to use. Do your games load and work in your chosen emulator outside of Launchbox ? What emulators are you using ? It's been so long since I have seen what the recommended emulators are I forget what they actually are. The error about emulator application pas was not found tells me that Launchbox is not finding the emulator exe at the location you are telling it to be. Did you move your emulator ? The message "bad checksum" leads me to believe you have a bad rom dump. Does this rom work in the emulator outside of Launchbox ?

It's a legit program and is supposed to be very good. I have never used it though, I just use FS-UAE and it suits my needs just fine.

Ok, I don't know what version of VBA you are using but I just downloaded this version https://sourceforge.net/projects/vba/ I extracted it and in the VisualBoyAdvance.cfg I set fullscreen to 1. It loads up in fullscreen mode perfectly.

During the import wizard you should have had a section where you can pick and choose which art work you wanted or didn't want downloaded. If it grabbed nothing at all for anything then you either had really badly named roms or something else really went wrong. You can use Tools > Download Metadata and Media to have it rescrape for the selected platform.

Box art will be gotten through Launchbox's scraper and database and so will videos if you have an Emumovies account.

Ok, so you don't have something long and ridiculous. I'm honestly at a loss, it should work but then again it's been a long time since I have used a UIFX version of Mame. I have been using the command line version of Mame because it's just easier for me now. I'll tag @Zombeaver to see if he has any input, I think he still uses a UI version of Mame.

Ok just out of curiosity what is the full path of where your roms are located ? The issue is most definitely a rom path because that is precisely what the error is telling. That is not to say that you aren't telling it where your roms are or that the emulator on it's own cannot use it. But it could be the rom path is too long or something else causing it to not like the command line parameter.

Can you edit a game and get me a screenshot of the rom location ?

Are you 100% certain you didn't choose to copy your rom files during the import process ?

I took a quick look at the latest version on their sourceforge download and in the config file there was a fullscreen flag which you can set to 1. Personally though I would suggest using mGBA which is known to be the much better emulator. The stand alone is fine but if you use Retroarch at all use the mGBA core.

Honestly, you have to try them in the emulator you are using and see if it supports that format. All my games are .CDI and never tried .MDS/.MDF though I have seen other emulators support that format for its games.

CDI is the standard format that all the Dreamcast emulators support but GDI is also an option. As for stand versus Retroarch it's a question that gets asked quite frequently and people have their own opinions on it. Individual emulators are easier to setup in general but that isn't true in all cases just like how Retroarch in general is better overall for several reasons but is not true in all cases. Emulators such as Fusion (Genesis) and Higan (SNES) are fantastic stand alone emulators and are pretty easy to set up if not using a frontend. But once you throw a frontend on top of them they become a real pain in the ass to deal with. Fusion becomes a pain because of how it handles resolution changes and Higans rom manager is very unwieldy. Personally I use Retroarch for the most part but not everywhere. There are a few reasons why I use it. One being the shaders, I really love its CRT shaders and being able to apply them across all sprite based games gives me a uniform look which I really like. Reason two, the best audio syncing. Reason three, lowest input lag. Reason 4, the "Quick Menu" to manage save states and swap disks. Reason 5, constantly being worked on emulator cores while many stand alones have all but stopped development. Once you take the time to learn how to setup Retroarch it applies to so many systems and is getting better all the time. Every now again someone makes the argument that stand alone is always better but I find that argument to be baseless. For example just because the stand alone version of bSnes has a higher version number when compared to its RA counterpart it doesn't mean that RA core is not kept up to date. Many times improvements get made to the core and they just don't bother changing the version number.

Well it's definitely a missing rom issue. Does this happen for all games or just this one you are loading which looks to be the game 720 ?

If you could tell us what kind of errors you are getting that would be much more helpful. Screenshots of the errors and your edit emulator window for your Mame emulator in Launchbox.

Can you post some screenshots of the edit emulator and associated platforms windows in Launchbox ? Specifically these 2 windows.

NullDC might be fine on it but the compatibility list drops off with it.

There was an article written over on the Dolphin website that talked about how I see GPUs being truly implemented into emulation of more modern consoles going forward. While it certainly is somewhat technical I think it is fairly understandable. https://dolphin-emu.org/blog/2017/07/30/ubershaders/

No. It wasn't really until the N64 when you started to see proper dedicated 3D hardware, the PS1 and Saturn had rudimentary 3D at best. I'm not sure at what point you got what would be considered something comparable to anything modern until the Gamecube and Wii, maybe the PS2 and Dreamcast.

I cannot speak as a programmer or a dev of any kind whatsoever, I can only speak as someone who's been a "power user" of PCs for 20+ years and gaming for 35+ years. It's my main hobby and I do a lot of reading so I do have a bit of an understanding of how things work in general terms. I don't see the emulation itself being pushed on to the GPU (but its is possible I guess). I see it more a case of since these newer systems have dedicated GPUs themselves the emulator devs will push that specific functionality of the emulator to the GPU of the PC. It will be more of a 50/50 deal, both will be equally requires for the more modern systems.

The GPU for the most part has little to no effect on the actual emulation itself. I say for the most part because the only emulators that even use that all for anything would be Dolphin, PCSX2 (hardware renderer), CEMU and certain hardware rendering cores in Retroarch such as the N64 and PSX HW ones. Even though those cores make use of the GPU it is still only minor and only for the graphical enhancement functionality such as the internal resolution scaling or effects like anti aliasing. One other place where a dedicated GPU does come in handy is with Mame and Retroarch's shaders but that does not require anything too powerful by todays standards. In my HTPC I have an old Radeon 7800 series card with 1 gig of gddr5 vram and it can handle even the heaviest of RA shaders without issues. The CPU does the bulk of the grunt work while the GPU puts the fit and finish on the final output. This could change going forward with more modern systems however as the Dolphin team have recently discussed passing some of the Wiis GPU functionality (shader cache) off on to the PCs GPU. If and when this happens then the GPU will become more important with the more modern emulation like with Cemu and RPCS3 and beyond. Also when this happens I doubt it will ever outpace the CPU requirements though like how with modern PC gaming the bulk of the time the bottlenecks are in the GPU, not the CPU.

Ok, I generally don't give a rats ass about startup videos and even though I won't be using this or any other one this is easily the most creative and cool one I have seen so far. Good job.

Feel free to submit a bitbucket ticket using the "Help & Support" menu at the top of this page and clicking on "Request a Feature" That is weird there is no 2560x1440 resolution option there since there was a pretty big list for me including the 4:3 aspect ratio of 1920x1440 which for made my BigBox stuff still look good and clean but with black borders on the sides.

There is no way to do this within BigBox on its own but I took a few minutes to see if I could find something. I think I found something that will do what you are looking for. I tested it out on my 16:9 2560x1440 monitor and I created a custom shortcut to start up BigBox @ 1920x1440 and it worked, it loaded up BigBox in that 4:3 aspect ratio with black bars on the sides. Here is a link to the program called Reso http://www.bcheck.net/apps/reso.htm simply run it and point it at your BigBox.exe, input the resolution you want it to run at which would be 2560x1440 for 16:9. Then click the create shortcut button and tell it where to create that shortcut, the just load up BigBox using that shortcut file and you should be good to go. I hope this does what you are wanting it to do.

Just because some roms work with Mame 173 and others don't does not mean your rom set is 173. Roms from older romsets can often work with newer Mame builds. Why so many wont work though is because over the years rom dumps have changed due to older ones being bad dumps and getting replaced with proper dumps. Or in some cases like recently with the Capcom CPS2 they finally emulated the encryption chip which is now included in the newer roms.