CDBlue

@s9jaguar To get rid of the scanline effect on the videos, just rename the file scanlines.png to something else (such as scanlines.png.old), which is located in the CoverBox\Images\Theme folder. This will remove that effect from the videos while not crashing the theme. Not sure if any other effect is in place though, or how to edit those... but what I mentioned here will remove the scanline effect anyway

Glad I could help

You should not rename the files/folders as it may break paths that the theme is coded to look for file locations. You typically just need to just extract the contents of the .zip file you downloaded from there, and then move that folder, along with its contents, into the the Themes folder within Launchbox. Or... even easier, just download the theme from within BigBox directly in the options/themes section and it will download and put it all where it needs to be without you having to extract/do anything else

I believe the problem might be that some of the eboot files are named the same for different games. As you said, you can rename the file during the import process (on the last page where it shows you what it will be importing, you can rename the title of the game there and as long as that game isn't already in your system it should import)... or during the import process/wizard you can select the option for force importing duplicates, and that should work as well (even though the path is different, launchbox sees that the rom name/eboot file name is already in your DB and that's likely why it's not importing as it thinks it's a duplicate). Hope this helps, CDBlue

I wouldn't worry too much about SSD/HDD for storage when it comes to LB/BB and the roms. You won't see too many benefits from storing either on an SSD as they don't take long to load on an HDD. You would see benefits in speed of course, but not too much. I would focus more on the three main parts of the PC ... processor, video card and ram (ram to a lesser degree than the other two). Those will impact your experience with LB/BB and the emulators much more than the storage medium. That being said, if you do have an SSD and a mechanical HDD in your system, then I would suggest you do what you listed (LB/BB on SSD and roms on the mechanical HDD - as they can use up alot of space that you can better use for other software on the SSD)

This might be hard to narrow down. There are two things we need to know first: 1 - Can you play those games from within Mame directly? 2 - Assuming #1 works, did you import based on your romset? For example, if you do not have a full romset, you should not use the Mame Arcade Full Set option, as that will make entries even for all games, even ones that you do not have. If you only have some of the roms (ie. only games you wanted to get, or you used a all killer/no filler list to select just the roms you wanted) then you need to import the roms in LB using the older way (ie. Import Roms and make sure Mame format is selected during the import process). The most important step though is #1. If #1 doesn't work with the roms you have, then the issue is with the romset (missing files, missing bios, incorrect settings in mame, etc.). If #1 works, then the issue is related to how you imported the roms in LB, or the emulator settings in LB. Hope this helps narrow the issue down a little.

Just an FYI, while your waiting for a reply from faeran, you can do this yourself by copying and renaming a few files in the theme's folders. In the theme's Views folder there are two sub folders with xaml files you can copy/rename (those folders are TextGamesView and TextListView). In both those folders you will find an xaml file called Nintendo 64.xaml (as an example). Just make a copy of that file in the same folder and then rename that copy to the name of the platform you want to use that view (eg. Nintendo 64DD.xaml). Do this to the files in both folders so that your theme will work on all views.

I have neocd setup in my retroarch. Although I use FBNeo mostly for neocd (I have bin/img files) I have tested neocd and it worked for me. You are correct about the system/neocd folder needing to exist. For the record, these are the files I have in mine: 000-lo.lo neocd.bin neocd.srm (don't quite recall why this is in there) The best thing to do first is match the SHA1 hash values for the files you have with the ones recommended for the neocd core (as can be seen here - https://github.com/libretro/neocd_libretro) If they don't match then likely that's the issue. If they do match, then I'm not sure what else might be the cause, other than maybe bad chd dumps maybe

yeah, to me I would say it still sounds like a parent/clone thing as I mentioned above. I would assume that it works from in Mame's UI because that is likely set to only show working roms (as it scans your rom folders and figures out which files are all there to make roms work, and will not show roms that don't have all the files needed). But importing into LB will import all roms, regardless if they have all the files needed to make them work or not... and it seems like some of those don't have all the files needed. The only thing I can suggest is to check to make sure you have a complete rom set, including all the bios, chd, sample files, etc. needed for all those roms to work (parents and clones).

See below thread. It's an older thread for an older version of Cemu, but it should still be relevant.... esp. the part about the game files and how to import them into LB There's also an older video/tuturial that might be helpful as well:

Out of curiosity, can you screenshot, and paste into this thread, the edit page for 1941 from within launchbox? Wondering if maybe when you imported the games into LB it made a clone the default file that it's trying to load, and that's missing files, while the parent would work properly. When in the Mame UI you likely have it set to only show working roms, so loading from within that UI would load a working parent (maybe)?

Just out of curiosity. Where is your mame.ini file? Is it located in the root of your mame folder, or in the ini folder? If it's in the ini folder, try moving it to the root of your mame folder and see if that makes it work from within launchbox. If the games work in mame, as you said they do, it's gotta be some little disconnect with LB and the setup/folder locations I would expect.

I believe the only emulator at the moment that does any decent job in emulating the Sega Naomi 2 boards is Demul (stand-alone/closed-source emulator)

It's been a while since I used Desmume stand alone, but if I recall this might be a bug/issue that's been reported many times to the Desmume team. I believe most people suggest patching the code with a line that forces it to go black and then compiling the code (if I recall that is). which for most people is not likely going to happen. In the end I ended up using the Retroarch Desmume core which the last time I used it (a while ago) didn't suffer from that bug/issue.

Hmm not sure there as I don't use the MAME core in retroarch as I prefer stand-alone MAME. However, it might be related to a newer option that was added recently (around version 1.7.7 I believe) which made it so you could select to have retroarch only close when you pressed escape twice. Check your settings and disable that option and see if that helps. Here's a video on where to set it:

Hello fellow emulation junkies. Thought I'd post this here in case people don't stay on top of their emulators like some of us do... Retroarch just released its latest version, 1.8.2. Here's a link to the release notes page. https://www.libretro.com/index.php/retroarch-1-8-2-released/ One item of note, which I've been waiting for a long time for them to implement, is the following: CORE UPDATER: Add option to update all installed cores Now with one press of the button Retroarch will look at the cores you have in your cores folder, check the buildbot site, and if there's a newer version of that core available it will download and update your core file. Anyway, enjoy

It really depends on what your system can handle. Unfortunately, PS emulation can be demanding when it comes to upscaling etc. I have a decent system and I have no issues with the below settings for the Beetle PSX HW core (I believe these are the only settings I changed in the core options): Renderer - Hardware (will only work with Vulkan or OpenGL video drivers - if your card cannot do these it will fall back to Software rendering, in which case upscaling is likely not going to work well, if at all)) Internal GPU resolution - 8x Internal Color Dept - 32bpp PGXP Operation Mode - Memory Only PGXP Vertex Cache - Off PGXP Perspective Correct Texturing - On The Libretro docs page has good information on the different settings and what they do. Worth a read if you're looking into tweaking the core options, etc. - https://docs.libretro.com/library/beetle_psx_hw/

More importantly. do they run from within Retroarch directly? If not, then it's a bios/retroarch issue that needs to be looked at. If they run in Retroarch, then it's a config issue in LB/BB. You need to narrow it down first before looking to see what needs to be fixed

I recommend trying to use the Bettle PSX HW vs just the Beetle PSX core if you can (unless you're going for a more authentic experience and not upscaling, etc.). The HW version of the core adds features such as PGXP Operation Mode, PGXP Vertex Cache and PGXP Perspective Correct Texturing that you can play with to make some major improvements with how the image looks (things line up better, less texture popping, etc.).

They were correct. The K in the intel processors means that the cores are unlocked... meaning you can overlock them easily (as long as the motherboard supports it) But, overlocking is a tricky question to answer easily. Some games/emulators are single-core/thread bound, in which case having more speed for that core can make a difference if the stock speed of your processor is not allowing the emulator to run at 100% speed. However, that being said, the main thing to consider though when overclocking a processor is to make sure you have adequate cooling for the processor, as overclocking it can significantly increase the temperatures it generates. The stock processors coolers for intel for that era (and even now really) are not good for anything other than minor overclocking, which likely won't do much benefit for the most part. So, unless you have an aftermarket air cooler on your processor, or a AIO (water cooler) then I would not suggest tinkering with overlocking the processor as the tiny overclocks you might be able to get won't affect anything for the most part. Getting a decent GPU will benefit you much more than overclocking a processor

For your specs any of the modern generation, or previous generation cards, should work fine. AMD and nVidia are the two front runners when it comes to dedicated GPU's. Personally, I'm not a huge fan of AMD cards for retro gaming, as alot of the modern emulators seems to have issues unless they support Vulkan as an API, which some do, and some are moving towards that. The ones that rely on OpenGL as an API of choice though, AMD's fall behind due to poor OpenGL driver support. For those emulators I find you need to rely on the devs to come up with hacks and/or graphics packs to bypass AMD's OpenGL shorcomings/issues and even then they are generally slower than their nVidia counterparts on that API. Therefore, I normally suggest going with nVidia because it just works and you don't need to fuss as much to get good performance. So, long story shot, nVidia 1000 or 2000 series cards (ie. this, and last generation) should be more than enough to run most of the emulators. Just a heads up though, a decent gaming-grade GPU can be pricey. I would suggest looking to see what a decent middle of the road, last-generation, nVidia card is going for... maybe a GTX 1060 or even a GTX 1050Ti. Those are likely to get you the best bang for you buck. Keep in mind though, if you do plan on doing modern-era PC gaming, the higher the card is (spec, and price normally) the better the performance will be in those titles. If you're just looking for retro gaming, up to PS3 for example, then GTX 1060 levels should be more than enough to get you going. As always though, always do some research before purchasing something like a dedicated GPU. They are pricey, and you want to make sure you get what fits your needs... don't always just go with the first recommendation you see... even mine hehe