Exactly why is this not making it into the game? It can’t be that difficult to implement (or can it?) and it would put a lot of complaints to rest.
Based on what the available layouts are, I’ll probably be using Recon.
My only problem with that particular layout is that X is Sprint and LB is Armor Ability.
I just thought it would be nice to switch the two. In Reach, the AA I’d choose the most was Sprint so having that at LB would feel familiar and comfortable. Additionally, having the AA button as X would be slightly similar to activating equipment in Halo 3.
Anyways, that’s just me nitpicking. Just thought I would share.
I would guess 1 it would be extra coding for a feature that I think comparatively few would use.
Plus I dont want friends defiling my setup when drunk, I’m cool with birthday changes on facebook and them renaming songs on my computer, but button remapping? It sends a shiver straight through me and the possible discrepancies.
Plus what to stop Mr.Smith from changing both triggers to shoot and essentially changing a DMR/Pistol/Carbind into an auto.
My ten cent is that its due to the complexities raised.
343i would have to test and program every possible button combination to avoid glitches and bugs; and they don’t want to because they can use the resources for other things.
And I completely agree with what you said about Recon. In fact, I even suggested it in the “A Quick Note” thread.
As AAs are now more like support, and Sprint is an important, default ability, let Sprint be on the easier accessable button. X works fine for AAs, I can already imagine bringing up a hardlight shield using it.
I don’t see myself fluently using X to Sprint though…
> 343i would have to test and program every possible button combination to avoid glitches and bugs; and they don’t want to because they can use the resources for other things.
This.
But OP, we all want customisable controls. But I’m still fine with the layouts that we’ve got.
As far as I know, there hasn’t been an official statement from 343i on why there will be no custom button mapping. We just know that it wont be in Halo 4.
343i did say that the controller layouts are subject to change.
Word on the street is that custom button mapping would increase the number of possible button combinations (i.e. BXR), but I can’t see how that’d be true, nor can I find any official statements to back that claim up.
AFAIK when you’re dealing with button inputs, you generally have two pieces of code: you have a chunk of code that’s hooked directly to the button press, and you have any other code you would need to run from there. So you might have an “B button pressed” function, which checks your control setup and calls a different piece of code (i.e. a weapon-reloading function).
Now, if you want to prevent button combinations, the best way is to check for bad combinations in that second piece of code. If you don’t want a player to throw a grenade while they’re still reloading, then you modify the code for throwing grenades – not the code for the grenade button – to check if the player is still reloading.
So custom button mapping shouldn’t cause issues with button combinations, because they should already have taken measure to prevent mutually-exclusive actions from occurring at the same time within the code for those actions. Custom button mapping should only affect the button-press code, and 343i shouldn’t be doing any combo-related checks there.
> Plus what to stop Mr.Smith from changing both triggers to shoot and essentially changing a DMR/Pistol/Carbind into an auto.
Hard fire rates enforced within the code that makes you fire your weapon.
> Plus what to stop Mr.Smith from changing both triggers to shoot and essentially changing a DMR/Pistol/Carbind into an auto.
Well, it wouldn’t work that way. If you tried to map the shoot button to the left trigger, it wouldn’t disable the grenade function, it would just map it to the original shoot button (right trigger). Most games with button mapping just switch functions instead of duplicating them.
> > Plus what to stop Mr.Smith from changing both triggers to shoot and essentially changing a DMR/Pistol/Carbind into an auto.
>
> Well, it wouldn’t work that way. If you tried to map the shoot button to the left trigger, it wouldn’t disable the grenade function, it would just map it to the original shoot button (right trigger). Most games with button mapping just switch functions instead of duplicating them.
Let’s not forget there is a wide market of 3rd party controllers that allow you to switch the function of buttons, or duplicate, or even put in full macros (rapid fire) and stuff. Since MS are quite slow/unwilling to ban these, I guess it’s easier for the devs to have set functions for all buttons and then just check for any false responses or something like that.
Maybe it just comes down to equality, everyone should have the same choices to make, no one gets any advantage over someone else by using a super good layout. Maybe it’s just easier to copy-past the finished (and bug free) code for all the default controllers from other games, saves time and money.
