Lordmonkus

That is in BigBox mode if you bought the premium license.

It will give you some extra features like loading fade screens which can be nice for larger games that take a few seconds to load or if you have them compressed and you need to wait for them to decompress. You also get universal save state management and bezels across all emulators. You certainly don't need RocketLauncher at all, I don't use it myself. I find it adds an extra layer of complexity and source of potential problems and isn't worth the effort. As far as your screen issues are concerned you could just need certain command parameters set in your emulator settings in Launchbox depending on the emulator.

Instead of adding a new line for SNES, edit the one that was there already to use the new core. The default emulator check box is only there for the import process.

I have had very few issues with most games. Of the 100+ games in my collection the only ones I have run into any issues with are the Cotton games which could just be my disk images and Burning Ranger which has some minor graphics glitches and slowness.

It's set in BigBox and works with almost all emulators, ePSXe is one of the few notable exceptions that I can think of off the top of my head. In BigBox mode go to the Options > Controller Automation and set a key combo in there.

There is a need for certain people to use SSF, it runs better on slower hardware. Mednafen and the Retroarch core have higher CPU requirements to run than SSF but you gain better accuracy. Options are always a good thing because you never know when someone is going to have a special case where the general rule of thumb does not apply.

Yup, in the controller settings in BigBox, you can set a button combo in there.

Ok yeah you still need Daemon Tools, forgot about that. I haven't given 2 shits about SSF since Mednafens Saturn emulator got released.

Launchbox plays fine with SSF with a simple batch file if you must use SSF for some reason.

Using the bulk edit tool for your NES games to set the emulator to Retroarch should work unless there is some oddball bug that I have not run into or heard anyone else reporting this bug (if it is a bug).

You can install everything within the Launchbox folder if you like for easy backup and portability.

Answer 1: In a recent build Jason implemented the ability to have LB start at the last platform and game but I am not sure if you can set exactly where it starts on load, this might be something @Jason Carrcan implement soon. Answer 2: I am fairly certain you can do this, though you may have to use something like Xpadder or AntiMicro. Answer 3: You can upgrade for 30$.

Put this in the Auto Hotkey Script tab of your ePSXe emulator config in Launchbox: $Esc:: { Process, Close, {{{StartupEXE}}} } I am taking no credit for this one, this was posted by a user here on the forums and I use it on my HTPC and it works for me.

Glad you got is figured out, weird it was your driver cause I have an 970 and updated my drivers recently as well without causing issues. If you are looking for a guide on the settings and what use and suggest check my guide I did.

Not sure if this will help but if you don't have Hard GPU Sync set to On try it out and see what happens. This should be set to On in any case but is Off by default.

Yeah 64 AUdio Latency and 0 Frame Delay is standard settings and you really shouldn't be getting any sound glitches with your system. I know Snes using the BSnes Accuracy core and the Mednafen Saturn can be taxing on lower end hardware but Genesis and NES is very light weight. Did you change your audio driver in the driver settings by chance ? Xaudio is the default. Are you using the stable 1.3.6 or a nightly build ?

There's a couple of things that could be causing stutter and crackle in the audio. Did you change your Audio Latency setting ? Setting it too low can cause crackle. 24 is generally the lowest I can go on my system here before encountering issues, sometimes I can get away with 16 depending on the core and game. Did you change your Frame Delay setting in the Video options ? Setting this too high can also cause some issues. Here I can generally go between 5 and 12 depending on game and core. Heavier cores such as BSnes and Saturn may be lower.

Progress is good

Setting up different controllers is easy enough, at least in my setup it was. To start I have 2 wired controllers hooked up, 1 Xbox 360 and 1 Hori FC pad. What I did was for each core I loaded up a game and then brought up the RA menu and the in the Input settings I selected the controller I wanted to use for that system. Example: Genesis to use the Fight Commander and N64 the Xbox 360 controller. With per-core config on these cores just remembered to use these controllers. But again I believe this works more with the fact I am using wired controllers and I think Retroarch may not be so nice with wireless controllers as it auto-configs when the controller is turned on.

Not sure if the inputmapper is necessary or not. For the 1 night I was tinkering with my PS4 controller on the PC I was using DS4Windows http://ds4windows.com/ I was trying to get the gyro sensors to control the mouse but I had no luck with it and then I just plugged it back into the PS4 and forgot about it again.

Make sure in your Retroarch emulator settings in Launchbox that you have the correct core in your associated platforms command line parameters setup correctly. My first guess is that you have a mismatch in the core set in there and the core you actually have. Here is a screenshot of mine for reference, though you can edit the command line parameter to change to the core that you want to use.

BigBox is easy to setup but when it comes to the theme stuff I can't say anything about it because I don't bother with any of the themes at all, the standard theme suits my tastes perfectly. Something you may want to look into for your controller issues though is look in the autoconfig folder. In there you will find several folders, look in the folder labeled hid and in there the config labeled Sony_Computer_Entertainment_Wireless_Controller.cfg might be the one for your controller. You might be able to edit that to your liking, just a thought, no idea if it's what you are looking for or not.

I think you're the only one with friends who want to play with you The rest of us either have no friends or use wired controllers that don't grab a controller ID when turned on.

I think the problem comes when you start dealing with multiple wireless bluetooth controllers and the way Retroarch auto detects and configures controllers.