bundangdon

On a related note, I've just recently noticed that they also removed the long-running post "Do you like Hyperspin?" from their forums. The last time I checked (a few months ago), it was filled with (mostly) negative posts, with people complaining about the lack of hyperspin development and comparing it with the features available in other frontends. They definitely have a great "scene" with people doing some excellent work by providing artwork and themes, but if there's any progress being made on the program itself, I'll believe it when I see it

That's an excellent tutorial and after watching it, launchbox (with rocketlauncher) became my frontend of choice

Another quick update. I just added the dolphin core information to the retroarch module, which took about 30 seconds and it's working fine within rocketlauncher

You may need to change some of the configuration-settings for some of the emulators within the rocketlauncher ui, but I have the same module (1.36) and everything seems to be working fine here with retroarch 1.60. However, I haven't (yet) tried any of the newly added systems like vice, dolphin, etc.

Right! Another reason I use rocketlauncher is for the reason you just mentioned. There's so much media (bezels, fades, pause, etc.) available, that it makes the whole 'experience' feel even more complete But as it's also been mentioned here before, it's all a matter of preference. Also, the modules that rocketlauncher uses make for both an advantage and disadvantage. They make setting up an emulator relatively easier but if a module for a particular emulator doesn't exist (and there are a few) then you're unable to use that emulator unless you want to create your own module. Nevertheless, I still use rocketlauncher for nearly all of my systems within launchbox

Additionally, for almost all of the hyperspin users out there, having rocketlauncher available makes the transition to launchbox/bigbox a whole lot easier and smoother

Lordmonkus explained the features of rocketlauncher rather well and for those reasons/features which were mentioned, I continue to use it because rocketlauncher adds the "icing on the cake" to launchbox/bigbox. However, it does take a little extra time to set up and get accustomed to, yet it's simple enough for someone like me to figure out after a few attempts My suggestion would be that once you feel comfortable with your launchbox setup and are ready for more "icing" then give rocketlauncher a try

Not at the moment, sorry. I haven't set up CPS3 on launchbox yet. However, you can probably set it up (relatively) easily with the automatic playlist feature, after you have imported your mame roms

There's a standalone cps3 emulator? I believe that if you have a pretty decent system (fast cpu) then MAME would be the best choice. However, FBA and WinKawaks will also work, especially for the older, slower systems

Agreed. And if you could set this up with RocketLauncher, then you could basically use it with any frontend including launchbox, hyperspin. etc.

Thank you very much for sharing! You might want to specify whether these are for retroarch, rocketlauncher, etc.

Right! And I did it all for Scooby snacks!

No worries! I think it had something to do with me answering someone else's message (of frustration), which was stuck in the middle of one of those spam posts. I'll try not to get too involved in spammy matters again

Indeed