Twinreaper

I'm sick of seeing these posts as well. 1. Your whole BS hacking claim is far from the truth and what actually happens. (I can and have performed memory edits, so I know whats legit and whats not) 2. Azure is not a perfect MM model, but every game HAS LAG. Deal with it. Poor connections of others, can cause your network resources to be utilized to even out the bad ones. If you bothered to read up on the Azure service, you would know this. 3. You gotta be kidding me with your completely bull**** weapon breakdown. Yeah a DMR "can" kill you in 4 shots...if all those shots are dead on in the head. In the heat of battle and with 50%-75% of battles beign heated or unexpected.....it just doesn't happen. Not enough time to react? Well if your anidiot who stands there and scouts to see where the bullets are coming from instead of moving directly to cover...then yes, you SHOULD DIE! 4. Any weapon can be overpowered with the right user behind it. You talk about camping around corners. In the good old days of halo 2 and Halo 3, you could camp behind a corner and get meleed, then 1 shotted to the head. Let me guess......we should nerf melee attacks cause they are OP? Get a grip. 5. There have been plenty of maps that are unbalanced at the start in terms or altitude. Turf, is a good example, as well as Construct. I could go on to include others like Terminal, Headlong, Lockout, etc... No map will ever the fit the bill as a perfect balanced starting ground. Only a complete cube with nothing else but 6 sides would qualify as balanced. Other than that, deal with it and learn how to use your disadvantage of map spawns into an advantage. 6. Having a multitude of additional weapons, also creates a map size issue, development time issue as well as the redundency of some of the weapons. You mention the SMG. The SMG is roughly the same firing rate and damage as the Assault Rifle. Halo 3 had the SMG yes, but it was not very favored over the Assault Rifle. Obviously you have never dealt with the pain staking process of picking a weapon set, and trying to evenly apply them to a map. Not a Forge map mind you...Forge is for wannabes. I'm talking real map making...as in HEK usage. Spend some tiem crafting a custom map from scratch, place spawns, effects, objectives etc... then come back and spout off about how easy it should be. 7. Armor is already fine. Just because you didn't like that they changed your helmet, does not mean the Armory selection poor. I used straight Hazop in Reach, but in 4, it's not my go to because of the drastic change. Changes need to be made, otherwise it gets boring. If I wanted the old Hazop helmet...I"ll go play Reach. I suggest you do the same. And btw, thats a pretty lame attack to make against the game. The armor changes nothing about the gameply. 8. Halo 4 may not have been the best Halo, in fact I was the first person to outright speek about how it fails, but my quarrels are with "actual" technical aspects...not some half ass halfed baked items that apply to only you or a select few who have the same playstyle or wants out of the game. I was gonna make 2 more to make it an even 10 things...but it aint even worth it brah. Peace out.

Most likely, the "Always On" connection is an effort to stop people from using modified Xbox's. If an always on connection is required to play, that also suggests that a connection is needed to be there when the Xbox boots up. If this feature was included, it would almost with 100% certainty, prevent Jtags of the future as well as mod chipped consoles. While this is a good thing, it can be bad as an unknown number of gamers out there, may not be able to afford Live or internet, and play strictly offline 100% of the time. As far as second hand discs go, there are a number ways to make this work, and why it would be a good thing. I don't really feel like posting a huge expo on this, so I'll just continue to watch you guys hash it out, and jump in when I finally see a response that is close enough or heading in the right direction. Think people think!

Good day fellow Halo 2 players. Today I have a few screenshots to share with you, that showcase my newest Halo 2 map edition: Powerhouse. Powerhouse is a direct take on the Reach version with minor texture and geometric changes so that the map could fit and be able to be loaded in Halo 2. Along with the map, there is a substantial amount of "Reach" weapon and tweaks added to the gameplay. Without anymore waiting, here are the shots of it. Expect more as the map develops...

Speaking of Ambiguous...what ever happened to the Alpha options? I hate switching between beta and alpha just to use stillcams...

I can't exactly see where the spectre is it in relation to the loading zone or the end of the level itself, so I will take a guess. Seeing as how you were more than likely above the end of the level with your back facing the loading zone/cinematic trigger, I can only assume that everything was spawned to the other players location. When you spawn at a distance greater than usual Line of Site, you are not teleported inside your vehicle, but instead teleported next to the other player. Sometimes if your close enough to the other person your vehicle is teleported with you...we have seen this before many times. I can only surmize, that because the spectre was launched passed the loading zone, that it landed on the other side of the loading zone. So when the level re-loaded the new bsp, it also loaded the spectre because the engine detected the vehicle inside of it, instead of the previous bsp. It's kinda like taking a vehicle thru different bsp's of the level. Even though the level loads another section of the map, the vehicle remains. The only time this fails is if the newer loaded/post cinematic, spawns the player away from the area in which the vehicle was, making backtracking impossible. A good example of this, is the banshee on the last level. Even though a cutscene plays, the banshee is still in an area where the player spawns initially. I hope that made sense..lmao Additionally, the only reason you are able to do these kinds of things, is because the engine itself loads vehicles and weapons from the shared/mainmenu/single_player_shared resource files. In Halo 3 and Reach, if the vehicle itself does not spawn on a particular section or is located in the map file itself as a reference, you expereince losing vehicles as in they just plain dissapear when a new section is loaded. Halo 2 does the opposite and loads the vehicle and wepaons or whatever, as long as the said item is still present and in play, regardless of reference within the map file.

Not sure who you are, or when you got here but welcome. Lots of cool things to do here, liek chat, post and oh yeah...we got some crappy thing called a Community Podcast going too. You might enjoy listening to it.....

Real classy bud. Obviously fake seing as how there is no swatstika bitmap anywhere in any portion of the games bitmap files. If your gonna try to shock people, try to do so with something that waasn't Nazi original. The Swatstika is found all over the world and dates back thousands of years. Moronic loser at best....

Hmmm a bit complicated but I can try. Usually whenever you see part of another map that "overlaps", it really isn't an overlap. it's actuall just another BSP from the scenario being displayed as a glitch due to loading zones and triggers. Most of the maps you pointed out, have each's bsp located and called in the scenario file either as a playable portion of the map or part of the cinematic. So that would explain that one. The collision or more directly, the PHMO, Physical Model Collision, is a bit tricky as well. While there are times that havok proves glitchy, this is one of those times. Due to phmo and coll in general having a not so pretty and accurate shape that matches the player model, Havok sometimes cannot predict or accurately place the chief on the map with collision when doing something in a repetative function. Most of the time if you look carefully, you actually see Chief's feet, beign somewhat "stuck" in the ground. meaning that a portion of his feet always seem to be just abrely inside the map. That of coarse is simply the render model only though, not the collision. So anyway, when you jump repeatedly or do something that Havok did not predict or calculate fast enough, it will sometimes place chief on an "invisible" ledge or vertical surface. This is simply because the collision detection did not quickly enough translate chiefs position. For instance, what you describe is also similar to getting through boundaries with vehicles. The collision detection can't quickly enough keep up with Chiefs position after being forcefully rammed, and thus by the time collision detection cathes up, because your model is already on the otherside, Havok then decides that your model is the correct placement, and provides collision to that position...hence putting you safely on the otherside, instead of killing you since you didn't show up inside or against the surface with a vehicle up your bum. At least that is what and how we have always explained it away. I'm sure there is a more accurately technological termination for it...but the older I get, the more I can't remember. LMAO hope that helped?

If ya'll need an executioner....look no further.

I'm with Azaxx and Liquid on that one. I too always play on a 1 setting. But I can do one better....I play on Legacy Inverted with that 1 as well..lmoa. And I still kick ***! And once again, Aim Acceleration is not a legit name nor a feature. All controllers have a sensitivity sensing feature that increase your looking or aiming speed depending on haw far you push the stick. Are you guys really that new to controllers that you never knew that? Seriously....

Probably Grumpy. You know me...lol. maybe they changed sig sizes or the video got removed?

Keep in mind Kills, that all we would have to do is recompile the trainers or apps like Ambiguous to accomodate the change. Reality is, there is no sure fire way to stop all hacks in gaming. Bungie tried and failed, 343 tried and failed, even Valve tries and fails. Some things will just always get through. But for PC gaming, you usually see a lot less hacks consistantly. At least thats what I see from playing Halo 2 PC and Halo 1.

Another additional post from an exceptional idiot. You have no idea what you are talking about. Just the fact that you state it has bugs...which it does not..shows your level of understanding in regards to anything Halo 2 PC related. Tell you what pal, just leave the PC side of things to the professionals like me and Kills. Thanks for trying though....

I own 3 60" Samsung televisions from last year according to the mfg date listed on them. 1 of them is a plasma, the one in my sons room. he plays for about 7-8 hours a day 7 days a week, and has no IR on it. We have had the televsion for a little over a year now. Maybe just buy some better quality?

Could not agree more. Amputating the Theatre Mode ability was a bad move.

Tornado, anyone can dominate someone with ANY gun. using a gun is up to YOU. The gun you use does not dictate whether or not you will emerge victorious. How many times have you seen people with rockets, get completely decimated by someone with a magnum or even an assault rifle. Just because you get killed by the same weapon being weilded, does not mean that particular weapon is OP or unbalanced. Everything has a counter in the game...you just need to find it and use it effectively. Instant respawn had been widely accepted. Don't try using those population figures to try to say that instant respawn is the sole reason why there is any fluxuation in population. that's just you "trying" to prove your opinion as fact. FACT is, no one can say exactly why or how the population is fluxuating the way it is. It's all to easy to point to somethign and say "Look at the population! it must be (insert claim here)". Please try to formulate a better rebutle. And since when am I known as beign Mr Niceguy? People like this OP only understand one thing...low level straight to the point replies. I see no reason to be nice or even play nice to anyone, and I will continue to not do so. Tough love is my style...you should be used to that by now.

Aim Acceleration does not exist in any Halo games in the naming convention you are using. If it did, there would be data in the tagset to point to this. What you are talking about, is the amount of time it takes for sensativity controls to overide the base biped turning and looking settings. Why do you think "3" is the default? It's because that is the biped tags own default setting equating to the controls. This 'Aim Acceleration" as you call it, has been part of Halo since the beginning. For all intent and purposes what you are describing can also be seen by only putting your joystick slighty to one side, and you turn slower than you would if you jammed it all the way. And what are you crying about? By your own words, it was largely unoticed..meanign a split second or even maybe 0.01 of a second. And your really crying about it? Get a clue man, your the first and hopefully last person to bring up such a ridiculous claim, and try to say that it is hurting multiplayer. I can't help but laugh the entire time I am writing this....

You have to complete SR which is level 50, then you can choose Wetworks or Operator, or any other specialization you may have unlocked.

If you want an even more amazing multiplayer experience, pick up Halo 2 and an old xbox and run XBC, or get Halo 2 pc.

Why do you need an updated version? I'm assuming everyone who wants it, simply just wants the rank system. I have yet to read one compelling argument that showcases why an updated version is good or warranted. Grumpy is the only one to date, who has even properly argued why it is a good thing. The rest of you are just following along like lemmings, trying to act as if this is a new or great idea. Show some effort and reason please...

(I touched up your grammar errors) ^^This, just discredited your entire post. Who are you to say that play time equates to knowing how and why things are bad? Very arrogant my friend. Armor abilities are an extension of equipment pick-ups from Halo 3. Furthermore, things like Promethian Vision, Jetpacks and Sprint, were all planned and half coded items still found in the Halo 2 tag structure. So that point is moot. Get over it. The weapons are fine. I'm tired of hearing all you guys crying about how the Assault Rifle is OP. Why is it OP? Oh I get it..because you can't pick-up your one trick pony precision weapons and dominate every player? Again, get over yourself. Precision weapons by every crybaby's standard, are the only weapons that should be able to kill at any range 100% of the time. On the topic of the BR...if you really believe the spread of it is the worst of the series, show some extracted tag data to prove it. Otherwise, keep that kind of guess work crap to yourself. It isn't the worst spread, and it is exactly the same as it was in Halo 3. The only thing different that makes the player assume it is greater, is the contrail they added to the bullets. The spawn system was an honest attempt to get more people playtime..instead of the constant waiting around in camera view to respawn. Granted yes, it could have been tweaked to work much better. But in the end, a larger majority of players would rather respawn instantly, rather than wait at an increasing rate depending on how or why they died. This is purely up to your own preference and cannot be argued properly with any fact or reasoning. Maps have always sucked since Halo 3. Construct was the only good map out of the bunch. Certain Affinity does the multiplayer maps, so you directing that hate towards 343i is unwarranted. Ranking systems don't make games great btw. The players and their individual playstyle and imagination make a game great. I'm confused. You blast 343i for murdering the series and want a more classic Halo return. But then you go onto say that Halo CE spawn system sucked as bad as Reach and Halo 4? Obviously classic means something different to you, than it does someone else. You don't want to play Halo 4 or even buy Halo 5? Fine, then don't. Quit crying about it already. You really want the developers to listen to your **** filled statements and take the community seriously? Have you re-read anything you have written, or others have written directed at 343i? And you really, really want them to listen with a serious ear? My god...just stop. Here's a tip. next time you want to start post here about something like this, I suggest you phrase your opening statement as follows...

You obviously know nothing about Blam! if you really think the 4 engine can't load or handle Forge World within Halo 4. Forge World was not the biggest map in terms of file size for Reach. Loading and playing Forge World within Halo 4 is quite easy and 100% doable.