SiriusVI
Members-
Posts
665 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by SiriusVI
-
I'm not so sure. If it were an api server issue, then the issue would also occur when importing a fresh set of roms. I believe that the issue is that Emumovies tries to find out if a file already exists before downloading and that process just isn't optimized. But that's just a guess. I really don't know what's going on.
-
Hey there, I wanted to use some of my days off to update metadata and media from some of my platforms and I encountered a weird issue with emumovies: Basically, when selecting games inn my platform (e.g. SNES) and choosing "Yes, but do not replace any existing fields or media (recommended)", emumovies takes a very lonng time to seach for and download new media files. I'm talking about leaving the PC on over night and in the morning it's not finished. It's roughly 1.700 games, and I'm only updating Manuals, Music and Video files, so nothing crazy. The problem is only with emumovies, the media from LB Database is downloaded very quickly. When deleting the platform and reimporting the games, or when choosing to replace all metadata and media, then this bug does NOT occur. It's only there when trying to update and choosing "Yes, but do not replace any existing fields or media (recommended)". What's I'm seeing on the progress bar on the top of Lauchbox is that emumovies keeps searching for files, then downloads a few (1-3 files) and then searches again. This process keeps repeating, making the whole process take unbearably long. Any idea why this is happening?
-
Hmm, it's just a set of No Intro SNES roms that are imported, but I wanted to update the metadata and media. It was a fresh Launchbox install, too. I don't know why this is happening. To be honest, I didn't try it again after it failed. For now I just force the metadata update first. I'll try it with another set and report back if it still hangs. Maybe it was a one-time bug. Who knows.
-
colorful COLORFUL Big Box Theme - Some additions (august 2026)
SiriusVI replied to JoffreyV's topic in Big Box Custom Themes
I remember, is this this update still happening eventually? As it stands, Colorful is not really usable for me. Te whole appeal of this theme is it's simle and consistent style. If there are too many inconsistencies, the theme loses its appeal and I'd rather use another preset where it's not so bad if there is a certain variation in how platforms appear visually. -
Thx for taking the time to answer! So yes, LB gets stuck on "Applying Metadata" when trying to update metadata and media on certain imported rom files. Forcing the metadata update manually without actually downloading metadata or media for games works. LB is installed on a local M2 SSD, v14.0.1 is installed.
-
Same issue. For as long as I can remember using Launchbox, I've been having this issue and I was never able to fix it. Also got my hopes up with the new version 14 Update, but that didn't fix the issue, either. I even set up a completely virgin version of Launchbox and only imported my platforms and emulators to try this out. But it just won't work. The new "shutdown screen" of Launchbox appears, bur then Launchbox still remains in the task manager, even after the shut down window is gone. Latest Debug file if anyone's interested: Debug 2026-09-04 09-04-45 AM.log
-
Yeah, I usually do that when I find an issue =). I'm guessing that most people don't bother with Japanese games and that's why it fell under the radar. But I can get quite obsessive, I tend to find these issues Yes, I set it exactly like with the USA and Europe games, but it doesn't seem to work on Japanese games.
-
@nonstatik, @jayjun911 This weirdly works only with USA and EUR DSiWare titles for me, but NOT with Japanese DSiWare titles (I know you have to use a region-specific NAND). USA and EU games boot directly, but Japanese games always go into the title menu first and I have to manually select the game. Is there a specific reason you can think of why direct boot mode does not work with Japanese games? EDIT: Chinese games also boot directly into the game. So far it's only Japanese games that have this issue.
-
Thank you all for the helpful info provided! I think I'll give the 4 play advanced a shot.
-
Hello everyone, I have a lot of original retro controllers at home that I would like to hook up to my computer for use with RetroArch. Up until now, I was using various different adapters and have set up different RetroArch set-ups (basically one for each controller type I own), each configured to work perfectly with a different controller type (N64; PS2; SNES; …). However, there are multiple things that bother me: I don’t want to manage / update 10 different versions of RetroArch anymore. There are still a lot of controllers I can’t find reliable adapters for. Some features, like rumble support, don’t reliably work with some of my adapters. That’s why I am considering buying the Bliss-box 4-play advanced, but I am unsure how well this works with RetroArch. Ordeing the Bliss-box 4-play advanced along with all the cables I need + shipping to Germany would be over 300€ and I don’t want to spend that kind of money if I’m not certain it will work as I want it to. At this price, it needs to be virtually flawless. Is there anyone here using the Bliss-box 4-play advanced who can give me some insight as to how this works with RetroArch? So basicaly, what I’d like to do is this: Connect SNES controllers --> start a SNES game with RetroArch --> all buttons for players 1 & 2 work perfectly out of the box. Close RetroArch --> connect NES controllers --> start a NES game with RetroArch --> all buttons for players 1 & 2 work perfectly out of the box. Close RetroArch --> connect N64 controllers --> start an N64 game with RetroArch --> all buttons for players 1, 2, 3, 4 work perfectly out of the box + rumble works with the rumble pack inserted on all 4 controllers Close RetroArch --> connect PS2 controllers --> start a PS2 game with RetroArch --> all buttons for players 1 & 2 work perfectly out of the box + rumble works. And so on. Is this possible, or is there any additional set-up required inside RetroArch? Maybe someone can explain to me how this works, because it is very hard to find good documentation online. Thank you! EDIT: sorry, there was some weirdness with the text color.
-
That is absolutely amazing. Didn't know about that. I will have to try all of this out once I get the chance. Another question: is there some kind of method for dealing with games that need a game specific boot command? I remember some games needing a version of the games name to be typed out in order to run. Also, for Apple 2 cassette tapes, I remember that each game has a special code that needs to be typed in order to run. So far I have only managed to automate this process using custom command line parameters in conjunction with AHK scrips to make such games run automatically. This is extremely demanding if you want to set this up for every single game.
-
This is such a valuable contribution, thank you! It also has potential to be expanded. There are many so computer systems that are a pain to set up so they launch automatically (Apple2 cassette tapes, electron, atom, and so on). It would be great if there were scrips like this for other systems as well.
-
This handy little tool can hide specific input devices from LaunchBox. And it's fairly easy to use. I think it's exactly what you need: https://github.com/briankendall/devreorder
-
Betas might work well sometimes, but might break your setup other times. Again, if you don't want to deal with bugs, stay away from the beta versions.
-
If you don't want to deal with buggy updates, you should not be updating to beta versions. Just stick to the stable versions and you should be fine.
-
Hey everyone, I've recently been setting up games using the retroarch subsystem menu options in various cores, for example: 1. Sameboy --> linking two games together via link cable emulation 2. Snes9x --> dual cartridge mode for sufami turbo games 3. MupenPlus Next --> N64DD What I've realized however is that when loading roms via these subsystems, retroachievements won't work. specifically, retroarch won't log into retroachievements at all: Does anyone have the same issue and can help me fix it? The strange thing is that I THINK it used to work in the past, but I might misremember. Maybe some settings are off. But launching games normally works fine.
-
Hey everyone, I've been trying to set up Nintendo 64DD within Retroarch and I've gotten most games working. Therefore, I wanted to share what I've learned along the way. I'm using the mupen64plus next core with ParaLLEl RDP and RSP. As for the N64DD games, I'm using the original Japanese dumps, no translation hacks (I haven't tested those, yet), and no cartridge conversions. Dezaemon DD and F-Zero X - Expansion Kit are expansions, which need specific N64 roms to load. The rest of the games are standalone, but still need an N64 rom to properly load. I'm using Super Mario 64 all of them, except for Kyojin no Doshin (Doshin the Giant), which for some reason won't load with Super Mario 64. I'm using Air Boarder 64 for that game. What you'll need: 1. The Japanese BIOS file version 1.2 2. The Japanese N64DD disk games 3. The Super Mario 64 (Japan) rom 4. The F-Zero X (Japan) rom 5. The Dezaemon 3D (Japan) rom 6. Another random Japanese N64 rom (I'm using Air Boarder 64 (Japan)) So here's the set up: 1. For the Japanese games, the Japanese BIOS file version 1.2 must be placed inside "RetroArch\system\Mupen64plus" and renamed to "IPL.n64" (the .n64 file extension is important, the z64 file can just be renamed, no need to convert it in any way). 2. Import the N64DD games into LaunchBox (the files can be zipped, no need to extract them). 3. In Launchbox, go to manage emulators --> Retroarch and find the Nintendo 64DD platform. Under Extra-Command-Line Parameters add: --subsystem ndd %romfile% "PATH TO\Super Mario 64 (Japan).zip" This should load most of the standalone games. 4. Go back to your N64 DD platform and find the Dezaemon DD game. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\Dezaemon 3D (Japan).zip" 5. Go back to your N64 DD platform and find the F-Zero X - Expansion Kit. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\F-Zero X (Japan).zip" 6. Go back to your N64 DD platform and find the Kyojin no Doshin game. Right-click and go to edit. Under "Emulation" enable Custom Command-Line Parameters and insdert: -L ".\cores\mupen64plus_next_libretro.dll" --subsystem ndd %romfile% "PATH TO\Air Boarder 64 (Japan).zip" 7. For Sim City 64 to be able to go past the title screen, make sure that in the mupen plus core options, the follwoing settings are set: "Framerate" must be set to "Original", "Fullspeed" causes a black screen past the initial logos. Under "Pak/Controller Options", if player 1 (and possible the other players?) has a rumble pak inserted, it also doesn't work (same as above). Memory pak works. That's it. I've not tested playing much, but as far as I can tell, this is how to get almost all of the games working. There are 2 roms, I'm still having trouble with (maybe someone can offer a solution?): 1. The Randnet Disk does launch, but once the title screen shows "press start", nothing happens. Pressing start on the controller won't do anything. I know that this isn't a game, but it would still be nice to enter the program, just out of curiosity. 2. Kyojin no Doshin - Kaihou Sensen Chibikko Chikko Daishuugou (Doshin the Giant: Tinkling Toddler Liberation Front! Assemble!) is an add-on / add-in for the Doshin the Giant disk. It does Launch, but it won't go in-game. If I understood correctly, in order to get this game to work, you'd need to be able to swap between the Doshin the Giant disk and this add-on disk, and I don't think this is possible with mupen. If anyone know of a way to do this, please share! I hope this helps someone!
-
Yeah, my thoughts exactly. For now, my go to method was to use HDD games as a default and only use disc games if an HDD versions was unavailable. I'm converting those disc game folders to .iso as we speak. I will decide later if I will switch to .iso files for the rest of my games, too, but most likely I will stick to HDD games until - eventaully - there will be a new file format that allows merging games with title updates and dlc, like you said.
-
I might reconsider switching from hdd based games to disk based games, too. But it's gonna be a long process. Especially if it's not possible to delete the HHD game, but leave the dlc and update data in tact. Ah well, we'll see.
-
I know, but for me, shaders are more important than anything else. I might switch to the standalone emulators once I find a convenient enough solution to autoload shaderglass with my shader presets when launching a rom. I think it's already possible, but I simply do not have the time to dig deeper into it, right now.
-
I might have to do it again some time, though, since I had to use the makecd command for all ps2 games, but most of the ps2 games are of course DVDs and so the makedvd command should be used. But at the time of conversion, this format was not compatible with the ps2 retroarch core, I believe. Same for PSP games. Makedvd is compatible with emulators, but retroachievements won't work with them.
-
you and me both! Haha. But chd is just too good to not convert.