As long as they fix the netcode we will be good.Mr Biggulswurth wrote:I think that is also a problem, telling people that the next installment will not have that problem whenever it releases, probably not for 3 years I'm assuming, but then do we the players have to put up with this for that long and deal with inconsistent gun fights? I think that just looks bad on part of the company that made and released the game with advertisements that say the game was meant for competitive play.MIb2347 wrote:Could you at least tell us when Halo 6 is out and it doesn't matter as much?I've received a few PM's on my discovery of another cause of heavy aim. I thought about and I will be keeping the cause to myself.Mr Biggulswurth wrote:OP the thing I'm still concerned about is whether there's anything we as players or 343 as a team could do to at least help the situation more. I also respect your decision on keeping information to yourself for reasons that may cause outrage among the community and more so among gamers in the FPS genre, but don't you agree that it's a controversy in of itself that you found something that affects core mechanics of the game that could cause an up roar if the information was leaked out. I say this because, for me and maybe others too, have voraciously voiced our concerns about a lot of things that aren't being addressed and the only response we seem to get is if issues for example, like their decision to disband spartan companies from warzone causes up roar, to which, they were forced to respond back. At the very least, could we get an update on if or when 343 responds to your letter?In my last post I had stated that I suspected there was another cause to the heavy aiming. My hypothesis turned out to be true. However, I'm not going to mention what it is.MIb2347 wrote:Any ideas when we can expect an update?
There is only one fix for the cause. The fix would be taking a step backwards as far as game functionality in other areas is concerned. So much to the point that it would make halo and xbox appear last gen. The trade just isn't worth it. I fear that if I make the cause public people might act upon it. I will be writing 343 directly about it so that it doesn't happen in Halo 6.
Additionally, it isn't worth making the change because fixing the netcoding will be more than enough to make the game consistently responsive... which brings me to the "LAN"
Before I dive into this I'd like re-state that a LAN on this game really takes place online. (for newcomers) I just got back from a 60 hour LAN for competitive halo. We played on a 60 down 6 up connection in Myrtle Beach, South Carolina.
Out of all the games we played that included only the eight players in the room, there were only one or two brief instances where the game became heavy. I repeat, in 3 straight days of playtime, the aim was crisp pretty much the entire time. The game actually felt like LAN... except when an outsider joined. We had one game where someone from Florida joined the game. As soon as he joined the aiming became impossible. Later we had 2 games where someone from Cali joined. Again, the aiming became impossibly heavy. One single person influenced the mechanics for the entire game... even after it had already started.
Also, there is something seriously wrong with forge maps other than just the framerate. Anytime we tried to play a forge map everyone would be teleporting. Was very strange.
- It isn't something 343 should have foreseen.
- It isn't something that is going to be changed. Doing so would make halo and xbox look last gen. (No, it isn't resolution related)
- Absolutely nothing positive can come out of revealing it.
- It's unlikely the problem will be present on the Scorpio and halo 6.
- If the netcoding is fixed, the problem won't matter.
Heavy Aim Fix Incoming
OP IWI IUI