Launchbox/PS1/Retroarch Issues

[Lordmonkus]

Yeah I don't use any -c configs for anything. I was just asking if it worked when removing the -c.

[luger81]

36 minutes ago, lordmonkus said:

Does it load games without the "-c config" command ?

yes

[Lordmonkus]

Ok.

So please indulge me here for a moment. What is it exactly that you are trying to achieve with the -c "config" command switch ? If you aren't trying to do anything special then you do not even need the -c command. If you simply want a different config for each system core just turn on per config in the configuration menu.

Now if you are still trying to load a custom config make sure your file name is correct. because I noticed in your previous posts you have "mednafen_psx_libretro.cfg" when by default the file name is "mednafen_psx_libretro.dll.cfg", notice the extra .dll part in there.

The only reason I am asking what it is you are trying to achieve there may be a better / simpler way of doing whatever it is you are trying to do.

[luger81]

1 hour ago, Imgema said:

I don't know, RetroArch changed it's behavior recently when it comes to separate cfg files. Basically, it doesn't need them anymore. All you need is overrides (except one or two occasions like the gameboy example above).

 

I have 30+ systems running on LaunchBox through RetroAch. The only systems i use the -c config command is with gameboy for reasons i explained in my previous posts above. For all other systems it's useless really (except maybe GenesisPlusGX if you want different shaders on all systems it supports).

The reason why I wanted them was to program in the control scheme. Are you saying that we can just use the override instead? That's something new. I didn't know about that.

 

Also, how do you make an override file? Just by editing the core.cfg like I did to make the ps1 work now?

Edited September 3, 2016 by luger81

[Imgema]

26 minutes ago, luger81 said:

The reason why I wanted them was to program in the control scheme. Are you saying that we can just use the override instead? That's something new. I didn't know about that.

You don't need a cfg or override to save different inputs per core.

When you load a game go to "quick menu"

There you will see a "controls" menu that refers to the core you have currently loaded and is separated from the main UI input options.

Setup the controls for that core and then select "save core remap file"

That setup will automatically load when you load that core. No cfgs or overrides needed. Same with shaders.

 

Edited September 3, 2016 by Imgema

[luger81]

1 minute ago, Imgema said:

You don't need a cfg or override to save different inputs per core.

When you load a game go to "quick menu"

There you will see a "controls" menu that is separated from the main UI input options. That refers to the core you have loaded.

Setup the controls for that core and then select "save core remap file"

That setup will automatically load when you load that core. No cfgs or overrides needed. Same with shaders.

 

Nice! But what about Hotkeys? Those are my main concern. Btw, thanks for all of your help. I appreciate you taking the time to help me out!

[Imgema]

Im not sure because i don't use hotkeys.

But if you could do it in a separate cfg, i'm sure it can be done with an override.

The main thing i'm trying to say here is that the less stuff you load manually through commands, the better. Overrides, controls and shaders are all automatically loaded by RetroArch itself so all you need to do is load the core. A separate cfg should be the last option, in case anything else doesn't work (like having different shaders for different systems using only one core).

Edited September 3, 2016 by Imgema

[luger81]

I use Hotkeys all the time for save/load states and exiting RA to get back to the menu without having to use my laptop keyboard, I like to use my controller for almost everything if possible. I use an XBOX 360 controller on my laptop.

[Imgema]

Aren't the hotkeys the same for every core then? As far as i know, all these functions are handled by RetroArch, not from each individual core.

Which means you can just setup the hotkeys in the main retroarch.cfg and you are done. All cores will use the same. No need for other cfgs or overrides.

[luger81]

31 minutes ago, Imgema said:

Aren't the hotkeys the same for every core then? As far as i know, all these functions are handled by RetroArch, not from each individual core.

Which means you can just setup the hotkeys in the main retroarch.cfg and you are done. All cores will use the same. No need for other cfgs or overrides.

True but for systems with more buttons, you might need the button like R3 as a kick or punch instead of quitting RA etc.

[luger81]

Thank you to everyone that helped me on this issue. Only a couple of the platforms put up a fight. They were missing the system directory in the cfg.