Aller au contenu

Photo

Separating Use/Storm/Cover - A how to guide


  • Veuillez vous connecter pour répondre
35 réponses à ce sujet

#1
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
First off I can not take credit for this, I have mearly cleaned up the thread started by Zhuinden, removing the information that no longer applies due to the 1.3 patch.  His original thread can be found <HERE>

Also if you are worried if doing this will result in you being banned, please read the following:

Thomas Abram wrote...

As mentioned, remapping keys is fair game.

To clarify - Make sure you know what you're doing when editing these files. If you do give yourself some sort of unfair advantage (accident or not) BioWare reserves the right to ban you. 

If you have any questions, concerns or comments please PM me.



This thread is to tell you how to separate the functions of the space bar, which activates Use/Storm/Cover all at the same time, often resulting in you preforming actions you did not want.  Do not attempt this unless you are comfortable with the following instructions and always, ALWAYS, make a back up copy of your Coalesced file before makingalterations.  Bewarned as well, when you patch the game you will need to reapply the changes you make as they will be writen over and returnedto default.

First off, I used ME3 Coalesced Utility which you can find <HERE>

To use it, run the program -
- click on file
- select open
- navigate to Mass Effect 3 > BioGame > CookedPCConsole > Coalesced.bin

Next find and click on the + next to the following to expand
- bioinput.ini
- sfxgame
- sfxgamemodebase

Now click on
- bindings = (multiple)

Next find this line

( Name="Shared_Action", Command="Exclusive TryStandingJump | Exclusive Used | OnRelease StormOff | OnHold 0.2 StormOn | Exclusive PressAction | OnTap 0.3 TapAction | OnHold 0.3 HoldAction" )

and replace it with this

( Name="Shared_Action", Command="Used" )

This will set your spacebar so that when pressed you will only try to use items, this allows you to capture objectives, revive fallen team mates and anything else that presents you with a use icon on it.

Next we will change an existing key command so that it will allow you to take cover and do combat rolls [if your character can use them].  The reason for this is because the 1.3 patch seems to have set it to where you can not add new command lines, however you can still change them.  The command this will change is swap weapon, bound to X by defualt, it is a key command I do not use due to the multiple other methods that can be used to switch weapons.

Find the line

( Name="PC_SwapWeapon", Command="TrySwapWeapon" )

And change it to

( Name="PC_SwapWeapon", Command=" PressAction | OnTap 0.3 TapAction | OnHold 0.3 HoldAction")

The final change I find a touch ironic because it changes the action for the walk button to storm, another key command I do not use... why walk when you can run forever?

Find the line

( Name="Walking", Command="EnableWalking | OnRelease DisableWalking" )

And change it to

( Name="Walking",Command="Exclusive TryStandingJump | OnRelease StormOff | StormOn")

Now, some of you may not like having Use set to the space bar, cover set to X and storm set to Y however changing this is very easy and can be done by the following.

Log into Mass Effect 3 and from the main menu select extras, then options then keybindings.

To change Use find Use/cover/storm which is defaulted to the space bar, click on the key binding and select a new key that will activate the use command.

To change Cover find Swap weapon which is defaulted to X, click on the key binding and select a new key that will activate the command.

To change Storm find Walk which is defaulted to Y, click on
the key binding and select a new key that will activate the command.

The changes that you made above only effect the command that is used on key press, it does not hard code it to those keys, I listed those keys in order to make the explination easier.

Again, all thanks should go to Zhuinden and all the people who contributed to his original thread.

[Edited 7/2/12 to include how to set the commands to different keys]

Modifié par thegamefreek78648, 02 juillet 2012 - 06:45 .


#2
Tokenusername

Tokenusername
  • Members
  • 11 157 messages
Storm is so 2007, bro.Posted Image

#3
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
Hey, their terminology, not mine.

#4
snackrat

snackrat
  • Members
  • 2 577 messages
Ah. So, if I wanted to keep space as roll/cover/dodge, I remove... what? And replace with... what? I would like to make either Z or X 'use', since I roll/storm/dodge/cover more than I enable/disable.

#5
himegoto

himegoto
  • Members
  • 2 490 messages
Funny how you are doing better than those who get paid.
I'll try this out and thanks.

#6
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
You can still change the key bindings in game this only changes what happens when the game recives the command. I simply used the default key bindings for ease of explanation. If you want space to be use simply change swap weapon from x to space in the keybindings under options in the extras menu

#7
Zhuinden

Zhuinden
  • Members
  • 2 480 messages

Karsciyin wrote...

Ah. So, if I wanted to keep space as roll/cover/dodge, I remove... what? And replace with... what? I would like to make either Z or X 'use', since I roll/storm/dodge/cover more than I enable/disable.


Simple, Roll/Cover/Dodge is named "TapAction", so if you want to have that on Space, then you should have OnTap 0.2 TapAction (I think that's what it was) on Shared_Action, and put Used and OnHold 0.2 StormOn | OnRelease StormOff on another command.

It's quite easy to figure it out actually, I personally have Roll/Cover/Dodge (TapAction, PressAction) and StormOn|StormOff on Space, and I have "Used" on a different key, which is key "T" in my case (I overwrote the PC_Talk thing instead, it's not like I need it). B)

I would have placed Storm on a completely different seperate button from Cover, but I realized I then would have to be pressing so many buttons that I end up confused and just forget to storm when I need to. :P

#8
AmicusHumaniGeneris

AmicusHumaniGeneris
  • Members
  • 446 messages
Makes you wonder why they couldn't implement it in the first place.

#9
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages

AmicusHumaniGeneris wrote...

Makes you wonder why they couldn't implement it in the first place.


Had to account for console controlers I guess.

#10
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
I included how to set the commands to different keys for those who want different keys to activate the various commands

#11
Zhuinden

Zhuinden
  • Members
  • 2 480 messages
Except the console controllers also have unused buttons while pressing "A" seems to kill people off as it never does what they would want it to do.

#12
Kem1995

Kem1995
  • Members
  • 669 messages
Good post MP. I use to use that method until it stopped for me for some reason so my friend showed me a different way. It lets you bind any key, but you need to remove said key function from the actual game such as F from melee for example.

bioinput -> sfxgame -> sfxgamemodebase -> bindings

At the bottom you just need these 3 lines.

( Name="E", Command="Exclusive Used" )
( Name="LeftShift", Command="Exclusive PressAction | OnTap 0.3 TapAction | OnHold 0.3 HoldAction | Exclusive TryStandingJump" )
( Name="SpaceBar", Command="OnRelease StormOff | OnHold 0.2 StormOn" )

As you can see, E is my use, LeftShift is my cover and Spacebar is storm as usual.

#13
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
I use to use that but it stopped working after the 1.3 patch

#14
Mandalore313

Mandalore313
  • Members
  • 1 957 messages

AmicusHumaniGeneris wrote...

Makes you wonder why they couldn't implement it in the first place.


They're not getting paid for it, therefore they don't care.

Keep that in mind next time a bioware appreciation thread pops up.

Also keep in mind that their first reaction to these tweaks was the banhammer.
They were then forced to listen to reason and let it be.

#15
ebls

ebls
  • Members
  • 187 messages
You know... I'm already quite used to one button for all actions (I'm not saying it's good, actually, it's horrible), but definitely worth trying. Thanks.

I would like to test something like this: sprint/storm - left shift; cover - space; use - button E.

#16
Mandalorian444

Mandalorian444
  • Members
  • 268 messages
Thank you. This has been frustrating for me ever since ME2, and now that I can fix it, it's wonderful. Thanks for fixing my #1 complaint about ME2-3.

#17
Zhuinden

Zhuinden
  • Members
  • 2 480 messages
Bumpity for great justice.

#18
atum

atum
  • Members
  • 1 422 messages
If only we could separate dodge and cover.

I'd give up my throne to the Hynerian Empire if we could separate dodge and cover.


Still, this is good info so bump +1

#19
dorbeetle

dorbeetle
  • Members
  • 9 messages
While configuring, this key binding list might be handy.

Modifié par dorbeetle, 28 août 2012 - 04:48 .


#20
thegamefreek78648

thegamefreek78648
  • Members
  • 1 447 messages
Thanks for that

#21
Zhuinden

Zhuinden
  • Members
  • 2 480 messages
Oh by the way, did you know you can assign FOV setter commands the same way?

( Name="NumpadNine", Command="FOV 120") and you'll have 120 fov instead of 70. It's surprising.

#22
Arppis

Arppis
  • Members
  • 12 750 messages
You should give this guide to Bioware devs, so they would know how to do this! ;D

#23
Zhuinden

Zhuinden
  • Members
  • 2 480 messages
That sounds like it could work :P

#24
Blind2Society

Blind2Society
  • Members
  • 7 576 messages

Zhuinden wrote...

Oh by the way, did you know you can assign FOV setter commands the same way?

( Name="NumpadNine", Command="FOV 120") and you'll have 120 fov instead of 70. It's surprising.


Is it that simple? Are there any issues?

#25
Zhuinden

Zhuinden
  • Members
  • 2 480 messages
Minor. The weapon zoom doesn't really work as intended in that case, which can be cumbersome with missiles.

This, however, can be fixed, if you modify either
- The right mouse button to be ( Name="RightMouseButton", Command="FOV 0 | Shared_Aim | OnRelease FOV 120" )

or

- the Shared_Aim command to be ( Name="Shared_Aim", Command="SwapWeaponIfEmpty | TightAim | FOV 0 | OnRelease FOV 120 | OnRelease StopTightAim" )

As far as I know, the second one is guaranteed to work, the first one wasn't tested but it also should work. Afterwards, there are no issues of any kind whatsoever - you just have to press the right mouse button at least once to make the FOV alteration come into effect, or just have a key assigned for it and press that after the game starts, either is fine.

The default value for FOV is 70, I use 120, someone said that's waaaay too much for them so a good number is around 100.