Printable View
Some emulators are command line only, others have a basic GUI, whilst others have detailed menus with information on each game.
I was wondering if there was a launcher style application that allows me to launch games for any console/emulator from a single place? It would also be great if I could configure my controller in one place, so I don't need to configure every controller in every emulator.
Does such an application exist?
Yeah they are called fronts ends. Check out quickplay.Quote:
I was wondering if there was a launcher style application that allows me to launch games for any console/emulator from a single place?
The one controller config for all games is not so realistic.
OK thanks.
I would be very interested to know if there is a controller configurator - it wouldn't need to be much more than a nice GUI with some simple regular expression search and replace on the config files. Once the config file containing the controller set up for each emulator had been identified, that should be a piece of cake.
If there really isn't anything out there then I might consider writing one.
Most emulators each deal with their controller options differently and every emulated machine had a different controller with the buttons set out differently and then most people using the emulators will in turn be using different controllers with different layouts and variable methods and drivers.
There's no universal front-end that will automatically map your controller to every emulator as there are just far too many variables to make it worthwhile considering how quick and easy it is to set them up per-emulator.
Its about 10 minutes work to go through the various emulators and set your controllers up with them. Hardly worth the hassle of trying to automate it.
There are applications like Joy2Key and X-Padder that you can use to standardise your controllers output that convert the controller signals into a specified keypress. Handy for emulators that don't allow you to define your own control layouts.
Other launcher front-ends to look at are Mamewah, Mala, GameEx, Maximus and loads of others too.
Here's a few example pics of my setup using mamewah and a couple of PS2 dual shocks.
http://img255.imageshack.us/img255/8597/dsc0233uv7.jpg
http://img367.imageshack.us/img367/5797/dsc0250hd4.jpg
http://img515.imageshack.us/img515/7329/dsc0234fy6.jpg
http://img515.imageshack.us/img515/8759/dsc0235zf8.jpg
I am familiar with MAMEWAH - I have it installed on an arcade machine in my living room too.
My main interest is in the controller config. It would be fairly straightforward to create one. Not everyone is as technically minded as you are, and it would take them a lot longer than 10 minutes to set up a controller in a dozen different emulators.
TBH for the vast majority of emulators its a simple case of selecting their controller config option and pressing the button you want to use for each control (up, down, left, right etc). There's really no technical skills or prior knowledge needed. Granted there are a few that are a little technical and require manipulation of a config file or in the case of Mame awareness of the TAB menu, but for the vast majority its all menu driven and very, very simple.
I'm not trying to put you off, if you have the necessary skills to investigate every emulator (and related plug-in where appropriate) and write an application that will recognise any controller and map its buttons to work in a logical order on every emulator automatically then go for it. I just think given the number of different emulators, controllers, and controller types, it is massive amounts of work for very little return based on the time it takes to simply define your controller per-emulator in the first place.
Dont see how you arrived at that notion. You first would need a globe UI, could be drop down to pick each controller and set up a config for it or an ini file for each and every symbol and button there is on all controllers. Then you have to iterate though all the ini files for each emulator ( many, not even remotely the same as the last ) and hack the registry when its used instead of a ini file. Then you have conversions to deal with. For example nes a and b map to snes x and y. Lets not forget about emulator updates. Dolphin changes it ini layout like women does her mind. By the time you think this all out you could have set up 7 emulation boxes! Its just not practical to do it. Sure it could be done, but you would have to have a motive to do such a thing.Quote:
It would be fairly straightforward to create one.
FatTrucker: I don't disagree that it's fairly simple but most users are (in my experience) pretty clueless. The point is that in every emulator it is slightly different and in most cases the controller that is being emulated is slightly different. For a novice user, going into 12 different applications and entering 10+ buttons each time doesn't sound like a 10 minute job. I think it would be useful to have a single place where you can configure your controller, just like you think it's useful to have a single location from which to launch games for any emulator.
ulaoulao: I don't know what a globe UI is but it wouldn't be difficult. It would be a simple GUI with a set of regular expressions to patch the config files. Editing the registry programatically is also very simple.
I think you are making a couple of assumptions that make what I am trying to do seem more complex. I would not need to detect the controller being used. I might have default profiles for popular controllers (e.g. XBOX360) but I wouldn't have 1 click set up for every controller under the sun.
If there really isn't anything else out there then I'll have a stab at writing one when I have finished with the updates I'm making to another software project.
Write one. You will see what I mean once you do.
Thing is you only need do it once for each emulator. Once the controller is set up you're good to go for the future.Quote:
Originally Posted by davejuk
As far as a universal configurator is concerned, I don't think specifically that its necessarily complex from a coding perspective, more from the fact that, that code will need to address multiple different emulators that all configure their controls in different ways some coded internally, some via config or text files, some via drop down menu and some via external plug-ins. Then there's the fact that from emulated system to emulated system you don't necessarily want your controller set up in the same way, dependent on what controller you're using with the emulator and what the original controller was like for the system you're emulating. At that point you're into the territory of having multiple controller profiles per emulator, which not only defeats the object but is already supported in Joy2key and X-padder.
There are just lots and lots of variables and IMO it will be virtually impossible to automate it in a way that people will find user friendly or convenient across lots of different emulators and they'll end up going into the emulator config anyway to tweak the settings they want.
By its nature the emulation community attracts gamers of a certain type, and while some greener users can struggle with some of the more modern emulators for systems like the Wii and PS2, I think you'll be hard pushed to find many that don't have the basic technical knowledge required to go into an options menu and select 'Controller Config' then press their controller buttons to correspond with the on screen prompt to 'press the button for up' for example.
The whole point of a game launcher front-end apart from the obvious aesthetic improvements with screenshots and the like is that it allows quick and easy perusal of a gamelist and one click launching, its not the same thing as a global controller configurator at all.
From a more general standpoint, the emulation community has always been made up of a minority of interested enthusiasts, you have to ask the question should it really be made easier and more accessible for the casual crowd whose primary interest is simply in playing pirated games. Surely such things only serve to draw unwanted attention and counter productive PR to a community that currently receives a fair degree of unofficial support from the development community.
Taking Mamewah as an example, its incredibly convoluted and complicated to learn how to set it up initially, seeing off the vast majority of people who want to exploit it for gain or casual piracy. This prevents it from proliferating to a point where companies with commercial interests see it as a threat and kill it off.
