k_rollo

This is also a good option, but he is reluctant to repeat the downloading process. It will depend on what OP is willing to invest his time in haha.

Thanks for confirming, I knew that was the problem. I also think it's not "faulty" CUEs either, because they work when you pointed LB to the CUE in the XML, so that tells us your CUE files do work but just don't convert. This is correct. The GDI to CHD conversion is everything you want and what I am also enjoying now. I can even convert fanmade Dreamcast ports such as Dolphin Blue from GDI to CHD. I wouldn't say your library is completely sh*te though. You effectively solved your original problem with the XML solution, but you just had an additional requirement of converting to CHD upon your discovery of the format. I don't blame ya. In my case however, it was faster to re-download the GDI because I don't exactly take entire romsets making them easier to manage on mishaps (such as this). You are now struggling with the "Sunken Cost Fallacy" where you are reluctant to abandon a strategy because of an initial heavy investment on it (i.e. 2 weeks worth of download), which I don't blame ya for either. However, this can keep you stuck. As I see it, you have these options: Pick only the games you like when re-downloading GDI rather than the whole romset. You give up the "completeness" factor. Results are certain. Retain BIN/CUE format and point LB to CUE as you already did. You give up CHD compression. Results are certain. Keep looking for a way to batch convert CUE to GDI (I haven't seen a method that worked). You get completeness and CHD compression. Results are uncertain until you convert CUE to GDI first. Re-download romset directly in CHD format if available. You repeat the download process (to a certain extent). Results are certain. Personally, I picked #1 when I had this problem. Not only did it save me a lot of time but also even much bigger space in addition to the CHD conversion. Time and space were more valuable to me than completeness. Hope this helps you decide, it will be up to you. Also, I'm a girl haha. Good luck OP!

Hi @sundogak how do I filter for Sega Model 3? It doesn't have a BIOS I believe. Edit: Figured it out.

Exactly. I don't even use MAME itself, I use MAME files in other standalone arcade emulators like Flycast and Supermodel, then just get the game I want from the set. Those emulators don't even care about versions. Now I'm happily playing with my curated Atomiswave, Model 3, NAOMI, NAOMI 2 games using my fightstick, gamepad (for racing games). and mouse (for lightgun games). Granted, this is Sega-specific but then again, that's only what I'm interested in so this method is pretty lightweight and effective with what I want.

Thanks for the screenshot. Couldn't find where to put the BIOS filter.

Convert disc-based games (i.e. PS1, PS2, DC) to CHD and don't zip them.

Aww too bad, the CHDs are required to make the games run. At least that's what I confirmed to work 100% for NAOMI 1/2. No worries, I got around it. NAOMI 2 romset isn't very big, it was easy to pick them off as long as I had a list of what to look for.

Thanks man, saw this too. I use it for Flycast and Supermodel and they needed the CHDs.

Nice. Thanks for the additional info @faeran 🙂

CUE will convert fine on PS1, NOT on Dreamcast specifically as I mentioned before. People assume PS1 BIN/CUE and Dreamcast BIN/CUE behave the same in CHD conversion (which I also assumed previously), but they don't. Don't ask me why, I just know that reddit post saved me a lot of trouble haha. He already tried converting the CUE files anyway and failed as I had predicted so that supports the theory. He can keep repeating the same process that failed or try a different solution that I can confirm also worked for me when I had this problem. Good luck to OP!

I picked them off the lastest 0.245.

I just had the joy of picking off NAOMI 2 ROMs from the MAME set (merged) + CHDs based from the list above. Spot testing of Virtua Fighter 4: Final Tuned and Wild Riders worked. Thanks for the list.

Did you follow these as instructed? I assume you still converted the CUE? As mentioned, conversion from CUE to CHD in Dreamcast does not work. The ROMs must be in BIN/GDI before conversion. CUE and GDI are not compression formats. They are nothing but text files and can be opened with Notepad. The files list the sequence of tracks in a disc media.

I always assumed it was talking about this: If I'm right, you're lucky.

OP particularly said he used the "CUE or GDI to CHD" and that specfic script is popularly downloaded from the internet along with chdman binaries. He can delete the CUE or edit the script to remove CUE, whichever way he is comfortable. Point being, you don't want chdman using the CUE instead of the GDI.

Last time I checked, converting the CUE file specifically for Dreamcast ROMs does not work. You need to convert the GDI file. I got Dreamcast ROMS in BIN/GDI instead and the CHD conversion worked. If your ROM download comes wth both CUE and GDI (like it does from Vimm's Lair), delete the CUE files first before running the .bat script.

Can you post a screenshot when this happens? I don't recall this from the top of my head.

What format are you using (e.g. BIN/CUE, GDI, CHD, etc)?

To those interested, this is Microsoft's technical documentation why they made the monicker change from .Net Core to simply .NET - https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-5

Which emulator?

Ah, .NET was Microsoft's attempt to eliminate the need for .NET Framework and .NET Core. They started doing this in .NET 5 but .NET 6 is the LTS version like 3.1. Microsoft will officially end its support for 3.1 on Dec 2022. Hence, updating to the new .NET 6 LTS is a good consideration if looking into the future. I recently updated my dev env from 3.1 to 6 at work and none of the code broke, so that looks promising haha. Microsoft release cycle - https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

.NET 6 is backwards compatible with 3.1 is it not? Technically, the runtime doesn't necessarily have to be the same with the SDK it was written on.

Ah yeah, that wasn't mainly pointed at you but to tell people in general what the error message is about. Nonetheless, manually installing the runtime should be a universal solution for Win10/11 regarding this issue. Still, would be cool to know what exactly the OP did. I did say I would "personally" pick the SDK because I do code in C# (which I didn't imply the first time lol). For most end-users, the runtime is enough. Thought I'd tell the newbies the difference.