Mass Effect 3 SP Controller Support

[DustyShinigami]

I told you, go to tools and select check eligible mods for updates.

I've already done this. It just says 'all updatable mods are up to date'. Still can't aim or exit on a turret.

[Mgamerz]

What version of mod manager do you have, and what version of the mod does it say you have.

Copy the log to the clipboard from the help menu after you check for updates, and then post it here so I can analyze it.

[DustyShinigami]

The mod is 1.070 and the manager is version 4.2 Beta 1 Build 51.

Looks like the mod is out of date. Whoops. Downloading the latest version now, so hopefully everything will be okay. I'll report back if I continue to have problems.

Thanks for your help

[Mgamerz]

Your mod manager is also out of date. It should prompt you when you start it to update unless you declined the last one, which you can remove by going to the options page.

[DustyShinigami]

I don't get any prompts when I load it up. The 'check for updates at startup' tickbox is ticked as well... Though weirdly, unchecking the box and closing the window and the then loading it back up still shows it ticked.

EDIT: downloaded the latest version manually

[Mgamerz]

Interesting. I'll see if that's a bug. Edit: doesn't seem to show up in 4.2b2, don't know about 4.2b1.

You will only see a "skip updates until build X" if you previously skipped a build.
Maybe the soaktest already filled up for the day. Edit: It's not

You should use only 4.2 beta 2 to install this mod since you seem to be using Mass Effect 3 1.6 (and anything less than 4.2b2 don't work with it properly). I assume you're located in the UK since all the UK users seem to be using 1.06 of ME3.

You should send me your debugging log (help menu) after starting mod manager so I can see why your client is not displaying the update. It only checks on the very first startup, reloads of it don't work (so you'll need to fully close it).

You can get beta 2 directly via http://me3tweaks.com/modmanager/updates/52/ME3CMM.7z but I still would appreciate the logs so I can see what's going on.

[oziboy]

So you got the inputs fixed?

Well, sort of. Basically I've disabled the Y, Back & the Left Thumbstick buttons in the bioinput.xml. That way I can use Pinnacle Game Profiler or Padstarr to assign the keybinds to the controller. Which will allow me to use those keybinds without opening the power wheel. And coupled with my xbox one elite controller, I can use the xbox accessories app to remap the controller buttons to the paddle buttons. Its a bit of stuffing around, but hey that's the point of mods, to customise things how you like it.

Cheers for all your help.

[oziboy]

Hi,

Got another question for you. Is it possible to edit the bioinput.xml file of the controller mod coalesced file while your controller mod is installed? Because I'm using the ALOT mod together with this controller mod, and I keep wanting to make changes to the layout after I've installed the ALOT mod. So, I was wondering if its possible to modify bioinput.xml while its installed. it would save me 6 hrs of installing ALOT each time.

Cheers

[Mgamerz]

You will need to extract it using dlceditor 2 of me3explorer. It is in bio game/patches/pcconsole/patch_001.sfar. You then have to reinject it into that file. It cannot be unpacked unfortunately.

[Skyfire1356]

I have the newest version available installed and for some reason I can't choose the investigate option in conversations which makes the game unplayable. Would anyone have any information on how to fix this?

Whenever I choose the option "Investigate" all that happens is the dialogue wheel blinks and that's it. I can exit the convo just fine.

EDIT: I fixed it myself. Might have been user error? I'm not sure. I had an older version of this mod installed and the newer version installed a newer Patch_001.sfar dated 3/2/2016 inside of the patches folder in BIOGAME. I remembered reading somewhere something about it patching that, so I went in that folder and first deleted it, but the game wouldn't load, so I loaded that back in and deleted the new patch file and reinstated the old PATCH_001.sfar dated 12/22/2012 and it worked! I have no idea why though...