Agent47

You're correct that the latest modules and module changes have been done by the community but even in open source projects someone has to manage, test, and ultimately implement them. Emulator changes that break the modules are pretty infrequent but add that to the fact not all emulators play nice with fade/bezels and require special attention and spread that across a few hundred emulators which could change things at anytime, it adds up. The fact that LB is closed source and Jason is the sole developer means the troubleshooting, implementation, debugging, etc. is all on his shoulders and the community can't really help at all there. So add the initial implementation and testing of the new features and the emulator changes that will require attention to everything he already has to maintain, bug reports, and the never ending stream of new requests and tackling a bunch of RL features becomes a larger task than most people realize.

FYI: It's ~$14 in a Humble software bundle atm here.

Judging by the titles of the Drive folders [EM %Date%] they're just EmuMovies vids.

Colons can't be used in directory/file names that's why you don't see them used in anything that corresponds directly to file names, apostrophes are fine. The colon is a normal character in xml and the apostrophe can be used literally also but needs to be escaped if an attribute is enclosed using apostrophes/single quotes and the attribute value contains an apostrophe.

The twitter link in the website footer is using the Facebook logo. Just something I happened to notice when scrolling that irked me

It sounds to me like for whatever reason the command line you have set for the emulator in LB is trying to execute the actual rom file rather than pass it as an argument to the emulator. That's why you get the 7z file manager when it's zipped and the open file dialog when it's unzipped (because Windows doesn't have a program association for those file types) just like if you were to double click the archive/rom through explorer. Are you using RL for those systems or are you using an emulator directly? I ask because if they're working through RL the only thing that should make it not work from LB is a bad command line and even then if it was something weird there are some RL checks that would usually throw errors at you. FWIW, I've never heard of your situation happening on the RL side of things. If you are using RL for those systems you can enable logging in RLUI and I may be able to figure out the problem from the log.

Have LB send "Panasonic 3DO" to RL as the system name or rename your system as that's the official name RL uses for it. From your screenshot you currently have it as "3DO Interactive Multiplayer" which I'm guessing is the standard LB naming.

You did everything correctly, whoever added GC to the module didn't. Try this one https://pastebin.com/tVJSnXtX

You don't do anything with the example ini, and even if you did it would literally do nothing. The RetroArch.ini file is the one that holds your settings, but you do NOT have to touch that either. What you need to do is replace the module itself, which is found at Modules/RetroArch/RetroArch.ahk. Backup the current one and replace it with the text in the pastebin. That's it, you don't need to set any module options.

The module dictates which systems appear in that list. If it's not showing there it means the module you're using doesn't support that system. Grab the latest module from the RetroArch Module thread on the RL forum as that should support it.

It's still random and arbitrary, but I imagine most people who have these included in their setups are (former) HyperSpin users or used HyperList as a reference as it's included there. It's one I never added simply because I'm not really into those casual games and it shouldn't have been included on HyperList IMO, or at least had a separate section for playlists/collections which that would've fallen into but quality and organization of HyperList went to virtually non-existent many years ago. It was probably added after someone seeing it in some drive seller's setup since they subdivide everything as many times as possible to pad their system count.

I see the problem. When you're running it through LB you're forcing the cue extension by passing the file path. Phoenix can't load cue sheets, it needs the actual iso or img due to the way it works which is why it just goes to the bios. When running directly from RLUI it takes the game name and checks against valid extensions, finds the iso, and works as it should. You should be able to fix this by having LB send just the rom name, instead of the entire path, to RL.

Let me know if you need better instructions or run into problems. If you're still having issues launching games through Phoenix after changing the plugin (or you decide you want to stick with your current method) post a full RL troubleshooting log here or create a thread on the RL forums with it and I should be able to figure out the problem.

The reason I ask.ed is because typically most frontends just send the rom name, not the entire path with the -r switch. The LB plugin prob handles that correctly because it was designed to. Not to mention from what I recall if youre using the rlui plugin you have to replicate all your xmls into the rlui directory. I dont use LB so idk. if there are any extra things to setup or if there are things that dont work properly. To set the LB plugin you should just have to go into the rlui/frontends tab and add LB and choose the plugin or double click to modify it if you already have it added. Then change the -p switch from rlui to lb in your lb rl emu args. Prob not the best description but im on my phone at work lol.

Is there a reason youre using the rlui plugin instead of the one for launchbox?

If you set your RL logging level to Troubleshooting, run a game from LB, and check the log it will tell you what args LB is sending to RL and what RL is sending to Phoenix. Between the two you should be able to determine the problem.

You may also want to try posting here, https://www.reddit.com/r/tipofmyjoystick/

I'm not home atm but there is a setting to specify the amount of time the fade in appears. Check on the fade - general tab and if you can't find it I'll reply with the option name when I get in front of my pc.

If memory serves, that error is a result of sending incorrect arguments from your frontend to RL.

I havent looked at it but I guarantee 200+ of those are series, arcade systems divided into boards and system genre playlists similar to how all those drive sellers do it to pad the number of wheels. Having that many, especially if theyre all top level, has to be a complete nightmare to navigate. If you want to he able to say "I have this many platforms" thats all ts good for, not usability.

I don't know what plugins you're referring to. If you're referring to the plugins mentioned in RLUI options and when people mention the "LaunchBox plugin" they're frontend specific plugins that pull metadata, media, system lists, game lists etc to be used with RL and RL features. The RLUI plugins are what populates your system and game lists in RLUI.

The Fade_Rom_Info_Description on the wiki page describes how to do what you want. To do it in RLUI: Select the Settings -> Fade - Info tab Set "Show Description As" to "image" Change the x and y coordinates for the "Text # Options" (where # is the position of Description in the Game Info Order. Description is position 1 by default)

There is no "correct" set, they'll all work fine. The audit won't be accurate for MAME no matter which merging option your set uses since not all files match the rom name, but everything will run.

Yes, the system name must match. RL looks for media, settings, etc based on the system name so if you have stuff under a different name it won't be found.

No problem. This is a prime example of why you should use the plugin, it would eliminate the possibility of a mismatch caused by manually adding systems. Go to the RocketLauncherUI tab and select the Frontends tab. Click the green cross and fill out the fields to add LB as a frontend. After doing that make it the default and active frontend by clicking the corresponding buttons (in same row as green cross).