Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
I currently use an original NES controller with a USB adapter that runs through X360CE to send X-Input commands to the game.
After you download it you just start the program, select your controller and set up the buttons that you want to mimick the 360 controller buttons. The game will then generate two files, x360ce.ini and xinput1_3.dll. You have to copy and paste those two files into the main directory of the MMLC, which is usually found at ~:\Steam\SteamApps\common\Suzy. Just drop those two files in there and you should have the game running. While the game boots you'll also hear a system sound dinging. If it doesn't it might indicate that something went wrong.
There are also two versions of x360ce, a 32-bit and a 64-bit. Depending on the type of the .exe file of the game you would need either one or the other. For MMLC, however, you need the 32-bit version of x360ce, as MMLC is a 32-bit application.
No one should have to go through all of that work just to be able to use a direct input controller. Any decently designed game will have both where it makes sense to do so, Like I beat cuphead with a USB SNES clone. Those devs clearly get it.
Yes, and the difference here is? They are western devs and probably have worked a lot with PC before, therefore those often do support direct input instead of x input. Most Japanese developers however are still rooted more in console development and will use the easiest way to get controller support in, which is X input.
Besides, downloading x360ce, setting it up for a controller and copying the files I mentioned into the folder takes about 30 seconds or less, unless you don't know how you want to configure your controller. Not really a lot of work.
Besides, I would have liked if x-input or direct input were the least of my worries, however, I have to select which controllers to connect to my computer, as if I don't and connect everything (360 controller, SNES/NES adapter, HOTAS, G13, wheel, etc.) I might not even have the right one selected in game. Again, I went ahead and adapted and now I just plug in the controller I need at that time. Sucks, but the problem runs far deeper and is rooted in the OS and the fact that it is much easier to get controller support in with x-input than with direct input, as the former only has to support the 360 controller, whereas the latter has to support all types of controllers with differing amount of axis, different types of actuanting a button press (positive or negative edge), different ways on how the signals are sent.
That is what we end up with, but luckily someone made x360ce and offered a solution for another problem in the OS.
Do the smart thing get a refund and use Roms + Emulator.
I have a SNES controller attached to my PC via a USB adaptor. Windows 7 x64 recognizes it perfectly, and it works wonderfully with many games (for example Alwa's Awakening, which is awesome btw.). But not Mega Man Legacy Collection. It isn't detected at all. And I am NOT playing Mega Man with a frikkin' keyboard! :(
I have tried to use X360CE, as many here and on different places on the internet suggested. But it doesn't work for me;
I downloaded the 32-bit program, unzipped it into the game folder (steamapps\common\suzy), started up x360ce.exe, the program asked to create xinput1_3.dll -> clicked Create, and then I get the error that "the program can't start because msvcp120.dll is missing", clicked on OK and X360CE still seems to run, which is weird. Anyway, I went to "controller settings", mapped my buttons, saved the configuration and exited X360CE. After all this, the game itself will not run and outputs the same error about MSVCP120.DLL. I did a search for that on my PC, found it from "windows\system32", copied it to the game folder, and now the game no longer complains about that file, but still refuses to run, saying "The application was unable to start correctly (0xc000007b)."
If I delete the X360CE-created DLL from the game folder (xinput1_3.dll), the game will work again, though the same problem exists with the game controller.
This is really infuriating, I am seriously considering asking for a refund from Steam because I only wanted to get the games into my steam library and not having to dig out my old Nintendo every time I wanted play them =(
Has anyone had similar issues and been able to find a solution?
Get a Refund based on the poor joypad compatibility ( its a valid reason, I just got my refund a few hours ago), then go download an Emulator and some ROMS, if you own the original games on cartridge but cannot play due to Console aging and malfunctions, downloading a ROM is not a breach of copyright law, there have been court cases siding with the ROM users.
Ya like i have my old nintendo games lying around.
Wish i did though, really miss cabal.
Just checked to which Microsoft program that .dll belongs to and it is part of thw 2013 C++ redistributable package. It might be that you have an older or damaged version of the mxvcp120.dll.
To get the newest version go here:
https://support.microsoft.com/en-gb/help/3179560/update-for-visual-c-2013-and-visual-c-redistributable-package
If you have a 32-bit Windows you only need the x86.exe File Path, if you have a 64-bit Windows you need to install download and run both the x86.exe File Path (for 32-bit compatability), as well as the x64.exe File Path. The files themselves aren't too big, only about 6 MB each.
Download and install and try again.
Also, you don't need to have the x360ce.exe in the same folder as the games executable (in the case of MMLC it is the Proteus.exe), it is enough to have the x360ce.ini and the xinput1_3.dll in the same folder.
Emulation is quite a grey area, however, if there are legally available copies of the same game on sale for a system you own (or even don't own), downloading and using ROMs while not having a legal copy of the game might still be copyright infringement. In all actuality you would need to be in possession of a legal copy even if you have a ROM 'backup' on your computer.
Naturally, with out of print games or those not available in other ways anymore you would be able to get away scott free, as there often wouldn't be anyone to pursue the copyright breach if you didn't own a legal copy, but everyone should be mindful that you are in a legal grey area when doing it.
That was exactly my point, I own the old Megaman Cartridges, but my NES is looong since dead from age and misstreatment, so personally I can Use ROMs of said games without being in breach of Copyright law ( based of previous court cases ruled in favour of the defendant ).
However not everyone is as fortunate and they would be treading into that grey area by using ROMs and Emulators, hence why one cannot directly recomend them as a solution without adding this as a "disclaimer", but lets face facts, Nintendo and Capcom are NOT gonna go to your house looking for said cartridges before pushing a lawsuit on you, so the responisibility to prove you are in the right lies squarely on the user.
That being said the Cartridge does not have to be in working condition for it to be a valid defense, so one could technically buy a fake cartridge with non-funtioning interior parts and produce your own label, to my knowledge they dpont do technical autopsies but rather take it at face value if you can produce a photo of yourself holding said cartridges and thus drop any lawsuits against you.
If you want the actual court referenced material you would have to look it up yourself since it is quite a few years I did my own investigations to determine wether I was in the clear.
For Famicom exclusive titles for instance, you would be ♥♥♥♥ out of luck getting a working copy with english translations without resorting to Emulators and Fan conversion, Armoured Fighter Patton, Bahamut Lagoon and Ogre Tactics are all in that grey area of out-of-print yet still illegal to ROM-own without physical caartridges on hand, UNLESS it is a full fan conversion, thou exceptions may apply in some cases.
Thanks a lot Schnittertm! I got my original SNES controller to work with the game now! I haven't even noticed any major input lag from using X360CE, which was a worry for me even if I could get it to work. So no need to get a refund now :)
In my original post I forgot to mention that I successfully did a repair of the Visual C++ 2012 libraries (both x64 and x86), from install files that were found in "steamapps\common\Suzy\_CommonRedist\vcredist", which confused me quite a bit at first, but alas it seems that the XINPUT1_3.DLL that X360CE creates requires the 2013 files on the system.
Such a shame that Digital Eclipse has been too lazy to give these great games the full attention they deserve. Still, I think they are now worth the ~6€ I paid for them on discount.