Yes of course you can, there was a issue with beta 2 that meant it didnt automatically update, beta 3 fixes that but you will need to instal it from the updates folder as it wont auto update (thats the issue with beta 2).
The Nostalgia theme is one of the heaviest ones we have in the download section, so yes that could certainly be a performance issue rather than a controller issue.
Im not sure what line it is to edit, maybe @Lordmonkus can help there, but im not sure how much closer you could get it or want it, as you can see in my image the platform names are already very close together, any closer and they will just merge into some sort of horrible text block thats unreadable.
You can add both file types, first just high-lite the .cdi games and drag them into the launchbox window to start the import wizard and import everything. Then go back to the folder with all the game folders with .gdi games, and in the search bar in the top right of the explorer window type in *.gdi that will list all the gdi files, just high-lite them all and drag them onto the Launchbox screen again and import to dreamcast again.
Well im assuming your nuc didnt like running in Vulkan at all, thats a much newer API. D3D has been around for a long long time though and everything should support that, try, D3D 9 first as that should be the most compatible, all be it older version.
OK to things here,
1. its been known for a long time that the old interface was going away, Jason has mentioned it many times. Progress is good only having next to code for is going to make things much easier going forward.
2. Launchbox next can be themed much like Bigbox can be, so you could close up those spaces you dont like if you so desire.
That sounds like something that should be handled by MAME itself rather than a frontend in my opinion. Its also a very niche thing that would take away from regular development of features that the masses want.
Yeah, basically the update packs include the new/altered files only and not the full roms, there is no need to include the full roms as you are updating a existing set, so it keeps the update size down by just including the new/altered files. CRLMAMEPRO will scan your romset with the latest mame list and copy the new/altered files into your existing rom zips to make them correct for the new MAME emulator.
Yeah it works well for me, Launchbox and all my roms are on a 5TB HDD, but all the images that .Next and Bigbox use are loaded from the faster cache on my SSD.
I dont believe there is a way for users to add new platforms to the database, @Jason Carr would have to do that if he deems the platform applicable, personally i haven't heard of either of them before though.
As does redream also, the reicast cores do support CHD but not the latest version of CHD, i cant use my CHD's with those cores at all, but demul and standalone redream play them fine.
We dont close topics around here, we leave them in case someone else is searching for the same issue.
Glad you figured it out, it had to be a option in Bigbox because as i said they read from the same files so games choice is the same in both Launchbox and Bigbox.
Bigbox and Launchbox use the exact same .xml files so they will show in both. The only thing i can think of is you have some of the "hide games missing certain media" options checked in Bigbox that are not checked in Launchbox, as they are separate and need to be activated/deactivated in both.
Correct, so if he was importing the .ccd files only and also having Launchbox move/copy them in the import wizard, then it will only move/copy those .ccd files so they wont work as they need the other files also.
Yeah but what im getting at is if you had launchbox copy/move the files at import, it will only have the .ccd files in the folder its looking in, so the games wont work. When importing system roms that have more than one file associated you should leave them where they are, or move them all into the Launchbox structure first then import them.
Just to add, i would make a copy first, just in case you do a typo or replace something by accident, then you can just move the copy back.
EDIT: lol, i should of read @DOS76 whole post first,as he already mentioned making a copy first.