Headrush69

Not sure exactly what you're trying here. Easiest approach is run this core through Retroarch. This should install without issue and doesn't have anything to do with LaunchBox. (This mod runs perfectly fine with it)

You have to find someone who has created a layout file that has a bezel and both screens already, or create one yourself.

Like neil9000 mentioned, if you only connect a USB power source, you wouldn't have the bluetooth functionality. Dolphin can connect to a bluetooth adapter in your PC other than the Dolphinbar, but in my experience it never worked flawlessly like the Dolphinbar. Finding the specific bluetooth adapter that has all functionality isn't easy either. The Dolphine forums have some documentation on this you can check out if you want to try.

Since you are already set up with RockeLauncher, you have the option of using RocketLauncher with LaunchBox as well. (You can do only some platforms or even just individual games) I only use RL with a couple platforms, but there are some things it does better. One specific issue that relates to your type issue: some Teknoparrot games take longer to start (Mario Kart) than LaunchBox's timed startup screen, and you get those startup windows showing sometimes. Since RL actively waits for the game window before hiding the startup screen, you don't have that problem.

Just give them a different platform name when you import them, but make sure to set Scrape As to Arcade.

Run some games in window mode with task manager running to see if something else is running. Windows Defender or virus scanning apps that get enabled can do things like that.

You have to unselect the check mark on the Root level as well.

Not exactly. You assign your keyboard keys to map to this Retropad abstract controller. You can see the defaults in retroarch.cfg. I have set all mine to nul and than in a core override (which is saved in Retroarch/config), I set the keys I want for that specific core. Here is an example from my my Stella core: So now in Retroarch, you will see those keys are set to those Retropad buttons. What the remap does, is it allows you do re-assign the Retropad buttons to different emulator functionality. For example, if Retropad button A is set to punch, you can remap Retropad button B to punch. Remaps change the Retropad assignments to the emulator function, not your keyboard keys. Retroarch controller mapping does seem different at first, but once you wrap your head around it, there are lots of advantages. You also have to remember Retroarch is dealing with so many cores, while an individual emulator is only dealing with one, so they need flexibility that straight keystroke mapping can't handle. Just a heads up, I've noticed with the flycast core, it seems some things have to mapped to specific Retropad buttons. For example in Naomi racing games, whatever key I choose, (or joystick button), has to be mapped to Retropad L2 and R2 for analog controls like gas pedal and brakes to work. Hope that helps.

When you select keyboard, this represents the device connected to the emulated machine, not your keyboard. The L2 and R2 in your screenshot are Retropad virtual buttons and you do not appear to have them mapped to your physical controller yet. Once you do you will see your physical controller listed after Port 1: You haven't said what controllers you are using, or if just a keyboard, but changing keycodes (which also map to the virtual Retropad buttons), can be done in your retroarch.cfg file or added in a core or file specific override. Something like this: You can see here Retroarch default keyboard key mappings to virtual Retropad

When it comes to MAME roms, names really don't mean much, it's all about the checksum. You can always use to see the checksums for the files it expects. Then you would have to compare with the checksums for the files within your intv.zip rom. (If you have 7-zip installed, its has a right mouse click contextual menu for getting checksums)

You have to change into the directory mame.exe is in then.

Are you in the directory where mame.exe is located? Are you using Powershell or command prompt? If Powershell, make it .\mame.exe

Nah. Nothing wrong with the channel but I'm not interested in Android emulation news (which he seems to cover a lot) and basically he just reading change logs in most of the videos I have seen. Would prefer to see video of changes of improvements and updates he mentions. I just check the The General Emulation Wiki page and I can see emulation updates very quickly and research more or update if I see something that interests me.

Just an FYI, looks like MAME specifically has some improvements in 0.243 to deal with the Apple IIgs joystick issues. I'm sticking with 0.242 for a while due to some possible regressions with new developments made in 0,243 for other systems, so I haven't checked whether the Apple IIgs improvements help yet. Edit: I broke down and tried 0.243 in a separate install and some joystick issues are fixed but I'm still seeing issues in some still, especially Gauntlet. Using the Joystick Calibrator referenced in the MameTester page for the bug, it seems analog values outside the expected byte size (0-255) occur, especially on diagonals. It could be the app itself but seems input still isn't perfect for analog joysticks.

LOL Glad you got it working. When I first started with LB, similar problem drove me crazy.

In the import options did you select Allow Duplicates? Sometimes when a rom doesn't import I find it's because LB thinks it's already installed. Since text between ( ) and [ ] which are used in hack rom names a lot aren't used when importing the rom, that could be part of the issue.

To clarify, are you saying they aren't added into LB or that meta data isn't downloaded? As Retro808 mentioned, The LB database doesn't have hacks roms, so unless you are scraping using a platform that matches where Emumovies has them (and it has those hacks), you won't get that meta data added.

I've done this for several of my games, especially vector games. It's not overly hard but you'll find different layouts use different coordinate systems, so you'll have to convert if that happens and only use one type per view.

The issue is that the previous layout you were using used an overlay to "tint" the vector graphics. Your custom bezel doesn't have that feature. Your only options are find a different layout that has both (enabled at the same time), or edit you custom bezel and add the same overlay features into the view you are using.

It's not even specific to themes. Within themes, different views may work best with one or the other, so you'll have to try and pick which view you are using. So a lot of themes/views have "extra" (for a lack of better words), dynamic theme UI elements so you probably wouldn't want a theme video video which has similar UI elements embedded in the video as well.

You may get a few smaller CDIs to convert but for the most part you won't have good success. CDI format was used to reduce the size to fit on a CD, so original data was changed or removed and conversion to CHD isn't usually successful. I always found it was easier to just find GDI versions before converting to CHD and you're assured you have a complete and working version.