20 June 2008 Link to this update Original B.net link Return to main page

<<

17 June 2011 10 June 2011 3 June 2011 27 May 2011 6 May 2011 29 April 2011 22 April 2011 15 April 2011 8 April 2011 1 April 2011 25 March 2011 18 March 2011 11 March 2011 4 March 2011 25 February 2011 18 February 2011 11 February 2011 4 February 2011 28 January 2011 21 January 2011 14 January 2011 7 January 2011 17 December 2010 10 December 2010 3 December 2010 19 November 2010 12 November 2010 5 November 2010 29 October 2010 22 October 2010 15 October 2010 8 October 2010 1 October 2010 24 September 2010 17 September 2010 10 September 2010 3 September 2010 27 August 2010 20 August 2010 12 August 2010 6 August 2010 30 July 2010 23 July 2010 16 July 2010 9 July 2010 2 July 2010 25 June 2010 18 June 2010 11 June 2010 4 June 2010 28 May 2010 21 May 2010 14 May 2010 7 May 2010 30 April 2010 23 April 2010 16 April 2010 9 April 2010 2 April 2010 26 March 2010 19 March 2010 12 March 2010 5 March 2010 26 February 2010 19 February 2010 12 February 2010 5 February 2010 29 January 2010 22 January 2010 15 January 2010 8 January 2010 18 December 2009 11 December 2009 4 December 2009 20 November 2009 13 November 2009 6 November 2009 30 October 2009 23 October 2009 16 October 2009 9 October 2009 2 October 2009 25 September 2009 18 September 2009 11 September 2009 4 September 2009 28 August 2009 21 August 2009 14 August 2009 7 August 2009 31 July 2009 24 July 2009 17 July 2009 10 July 2009 3 July 2009 26 June 2009 19 June 2009 12 June 2009 5 June 2009 29 May 2009 22 May 2009 15 May 2009 8 May 2009 1 May 2009 24 April 2009 17 April 2009 10 April 2009 3 April 2009 27 March 2009 20 March 2009 13 March 2009 6 March 2009 27 February 2009 20 February 2009 13 February 2009 6 February 2009 30 January 2009 23 January 2009 16 January 2009 9 January 2009 2 January 2009 26 December 2008 19 December 2008 12 December 2008 21 November 2008 14 November 2008 7 November 2008 31 October 2008 24 October 2008 17 October 2008 10 October 2008 3 October 2008 26 September 2008 18 September 2008 12 September 2008 5 September 2008 29 August 2008 22 August 2008 15 August 2008 8 August 2008 1 August 2008 25 July 2008 18 July 2008 11 July 2008 3 July 2008 27 June 2008 20 June 2008 13 June 2008 6 June 2008 30 May 2008 23 May 2008 16 May 2008 9 May 2008 2 May 2008 25 April 2008 18 April 2008 11 April 2008 4 April 2008 28 March 2008 21 March 2008 14 March 2008 7 March 2008 29 February 2008 22 February 2008 15 February 2008 8 February 2008 1 February 2008 18 January 2008 11 January 2008 4 January 2008 21 December 2007 14 December 2007 7 December 2007 30 November 2007 16 November 2007 9 November 2007 2 November 2007 26 October 2007 19 October 2007 12 October 2007 5 October 2007 28 September 2007 21 September 2007 14 September 2007 7 September 2007 31 August 2007 24 August 2007 17 August 2007 10 August 2007 3 August 2007 27 July 2007 20 July 2007 13 July 2007 6 July 2007 29 June 2007 22 June 2007 15 June 2007 8 June 2007 1 June 2007 25 May 2007 18 May 2007 11 May 2007 4 May 2007 27 April 2007 20 April 2007 13 April 2007 6 April 2007 30 March 2007 23 March 2007 16 March 2007 9 March 2007 2 March 2007 23 February 2007 16 February 2007 9 February 2007 2 February 2007 26 January 2007 19 January 2007 12 January 2007 5 January 2007 29 December 2006 22 December 2006 15 December 2006 8 December 2006 1 December 2006 17 November 2006 10 November 2006 3 November 2006 27 October 2006 20 October 2006 13 October 2006 8 October 2006 29 September 2006 22 September 2006 15 September 2006 8 September 2006 1 September 2006 25 August 2006 18 August 2006 11 August 2006 4 August 2006 28 July 2006 21 July 2006 14 July 2006 7 July 2006 30 June 2006 23 June 2006 16 June 2006 9 June 2006 2 June 2006 26 May 2006 19 May 2006 12 May 2006 5 May 2006 28 April 2006 21 April 2006 14 April 2006 7 April 2006 2 April 2006 31 March 2006 24 March 2006 17 March 2006 10 March 2006 3 March 2006 24 February 2006 17 February 2006 10 February 2006 3 February 2006 27 January 2006 13 January 2006 6 January 2006 16 December 2005 9 December 2005 2 December 2005 18 November 2005 11 November 2005 4 November 2005 28 October 2005 21 October 2005 14 October 2005 7 October 2005 30 September 2005 23 September 2005 16 September 2005 9 September 2005 2 September 2005 26 August 2005 19 August 2005 12 August 2005 5 August 2005 29 July 2005 22 July 2005 15 July 2005 8 July 2005 1 July 2005 17 June 2005 10 June 2005 3 June 2005 27 May 2005 20 May 2005 13 May 2005 6 May 2005 29 April 2005 22 April 2005 15 April 2005 8 April 2005 1 April 2005 25 March 2005 18 March 2005 11 March 2005 4 March 2005 25 February 2005 18 February 2005 11 February 2005 4 February 2005 28 January 2005 23 January 2005 14 January 2005 7 January 2005 30 December 2004 17 December 2004 10 December 2004 3 December 2004 19 November 2004 12 November 2004

>>

Bungie Weekly Update: 6/20/08

Posted by lukems at 6/20/2008 5:20 PM PDT

IF YOU THINK THE BATTLE RIFLE IS COOL, CLICK HERE

The Danger of Your Rising Tide

When games have as many passionate users as Bungie's Halo games do, it's perfectly understandable - and as I've said in this space before - and appreciated that they offer feedback as often as they do. That said, there's also a tide-like behavior about the way these issues seem to surface - and for Halo 3's Battle Rifle, the moon was certainly hovering in the sky. As early as the Halo 3 beta (roughly a year ago), we talked about how the Halo 3 Battle Rifle was changed from the Halo 2 post-1.1 update. There's a number of factors to consider when you're comparing the Halo 2 1.1. BR to the Halo 3 BR and today, before we get to the sweet, sweet Chill Out/Cold Storage images (scroll down if you don't care about BR and networking techno babble) we're looking at the Battle Rifle.

Halo 2's Battle Rifle was a hitscan weapon, which is fancy terminology for "instant-hit" which is slightly less fancy terminology for "if the reticule is red when you pull the trigger (in good networking conditions) the bullet packet will hit the target." Additionally, in Halo 2's BR the "spread" for the three bullet fire package was reduced in the 1.1 patch, focusing the bullet delivery into a tighter packet than when the game originally shipped.

The result of the "tweaked" Halo 2 Battle Rifle was a weapon that functioned astonishingly well at short, medium and long range. It was utilitarian and when coupled with a mountain of button combinations, astonishingly lethal. Arguably too lethal.
Halo 3's Battle Rifle, as we've discussed before, while similar in some respects to Halo 2's - it is still the Battle Rifle, it still fires three-round bursts, has had its functionality changed and now the Rifle performs much differently from its H2 predecessor.
Admittedly, it can certainly be jarring to see the weapon look nearly identically to a previous iteration and have its performance be different from what you'd expect. That is the case in Halo 3, and it is the case for a number of reasons.

Hitscan and Velocity

Unlike the Halo 2 Battle Rifle, the Halo 3 Battle Rifle is not a hitscan weapon. There are technically no hitscan weapons in Halo 3. The closest a projectile is to hitscan in Halo 3 is the Spartan laser, which instantly checks for a collision within the weapon's maximum range (that range is the largest of any weapon in Halo 3). The Sniper Rifle bullet is a high velocity round and covers that same distance in somewhere between two and three ticks. What that means, is that at a certain range, the Sniper Rifle behaves like an instant hit weapon, but at longer ranges it takes two to three frames for the bullet to arrive. Keep in mind that the initial range for the Sniper Rifle is huge.

On the contrary, the Halo 3 Battle Rifle's bullet velocity is significantly slower than both the Sniper Rifle round and the Spartan Laser beam - this was a decision made by design because the high level goal for the weapon included it requiring players to lead their targets at range. Just like the Sniper Rifle in the example above, at certain ranges, the Rifle will behave like an instant hit weapon - this would be at distances at or inside the range that a three round burst can travel in a single frame. Outside of that relatively small distance - the Battle Rifle changes considerably from its Halo 2 predecessor.

Support and Networking

Halo 2's networking model gave clients a distinct advantage against the host with the Sniper Rifle (See: Any number of swipe-sniping clips on the Internet from H2). In Halo 2, when the client aimed at the host (and hits on his screen) the data is packed up and delivered to the host saying "I shot, and here is where I hit this player." This allows hits to occur despite minor differences between player location in the gamespace (i.e. on my box you're directly in front of me and on your box, I'm ever so slightly to the right, [see: fig.1]) and still correctly register the hits on and off host. The system was imperfect (which isn't to presuppose that Halo 3's is perfect, there's always stuff we're going to be improving on) and those imperfections were exposed with the Sniper Rifle, giving the client sniping advantages against the host.

When rebuilding Halo 3's networking model, alleviating that advantage was one goal.


In Halo 3, a similar networking model is used, where regardless of where the client and the host are to one another on the monitors the host and client are looking at in their living rooms, the client and host are still transmitting data back and forth. In the example below, the top player is moving to the right (indicated by the black dotted arrow) and the bottom player is firing the Battle Rifle at the trajectory marked by the black and red arrow. The black part of the arrow is the distance that the bullets will travel in a single frame and the rest of the shot is marked by the red arrow.

The blue line is the distance from the moving player to where the bottom player is shooting (that player is accounting for the top player's movement when lining up the shot). In this example the blue line is critical, that distance, which is calculated on the client box (the distance from where the player is aiming to where the player is moving from), becomes key information on both the host and client box.

If the projectile hits the enemy within the black line, we can send the message, "I fired, and here is where I hit" (so with the Halo 2 BR this happened all the time). In Halo 3 clients send "I fired, here is who I was aiming at, and here is how far in front of the enemy I was aiming." The host lines up the shot using the blue line transmitted from the client, leading in front of him just like the client did and fires. What results is that two ticks (frames) later, the bullets hit the enemy on the host just like they do on the client. But we don't send a "I will hit the enemy in two ticks" message from the client. We just try and line up the shot and let the host recreate what is happening.

If the host finds that yes, the player aimed at this distance from me, but I'm not at that point when the bullets would arrive (via the red arrow), no hit is detected.

Bulletology

In Halo 3, each bullet from the Battle Rifle's three-round burst is networked individually under the cases outlined above. Additionally, each bullet has a different margin of error, with the first round from the Battle Rifle being the most accurate of the three bullets. The first bullet can have an error between 0 and .15 degrees off of the true aiming vector. The third bullet is between 0 and 0.38 degrees, the second bullet falls somewhere between the first and third. It is a mistake to look at where the third bullet lands and assume all three bullets are that inaccurate. The outliers (0.15 on bullet 1 and 0.38 on bullet 3) are the absolute worst-case scenarios. In that context those numbers don't mean a whole lot - but in the grand scheme thing of how the Battle Rifle operates, they are pretty meaningful.

The Battle Rifle works this way because after Halo 2 it was retuned to be a reliable headshot and anti-sniper weapon (in terms of pinging Snipers at distance from their scoped-in state). The first bullet in the burst fills this role - it is quite accurate (identical to the Halo 2 BR, but with a travel time), and will kill an unshielded unit with a headshot or ping a sniper.

Another design goal with the Battle Rifle in Halo 3 was to bring the kill-range closer. One way this was achieved was by giving bullets 2 and 3 from the BR a wider error, which makes them less likely to land outside of the BR's intended effective range. Summarily, this reduces the BR's effectiveness AND damage output at those ranges, without compromising its ability to finish a target at the same range.

This change allows the Battle Rifle to be competitive in terms of damage output at closer-than-Halo 2-levels, without being so effective at longer range, that players caught in the open are gunned down too quickly (that task in Halo 3's sandbox belongs to the Sniper Rifle. If you need to control a space 30wu [world units] away, use it instead).

Math Class

Over distance, the three BR bullets spread further than they are during the black line (see: fig 2) in the initial burst. In order to solve for how much a bullet's flight will vary over distance - the aforementioned margin of error are used in this equation:

SIN(Bullet's Margin of Error)xDistance to Target in WU(world units) = Actual margin of error from target

For the first, and most accurate bullet coming from the Battle Rifle here's the equation:
SIN(.15)xDistance in World Units = Error margin for a given bullet at a specific range.
In the case of the Battle Rifle on Guardian, the approximate distance from Snipe 2 to Gold 2 is roughly 18 world units. Plugging those numbers into the equation yields a value of .047 world units in the absolute worst case scenario for that bullet. Since one world unit is equal to 10 feet, the variation on that bullet is 0.047 world units, or roughly half of a foot. Considering that the Spartan model is 0.75 world units (the Chief is 7 and a half feet tall) you can get a pretty good idea of what kind of variation will come from that bullet, that works out to roughly a half a foot of variation at that distance. The Chief's helmet is approximately 0.094 world units wide, so if the shields pop, that bullet - aimed and fired accurately - under reasonable network conditions yields a kill.

Special thanks to Jon Cable, Tyson Green and Luke Timmins for answering about a million questions of mine this week regarding the iterations of the BR.

Denouement

Aesthetic similarities aside, the Battle Rifle in Halo 3 is a far different weapon from its Halo 2 predecessor. Despite what segments of the player population believe or want to believe, it is no longer a mid-to-long range killing machine. It is an anti-long range weapon with a focus on mid-range combat that ends up being utilitarian and functional, but not optimal at close range. The reasons for this are obvious - there is no designed one-weapon-to-rule-them-all in Halo 3 and that is a decision made by design to encourage all of the aspects of the sandbox to be used in gameplay.

Much of the fervent debate comes from players who simply want the weapon to perform differently than it was designed to perform. The bullet variation in the Battle Rifle's three-round bursts is a design choice that further defines the weapon's role in the Halo 3 sandbox.



The Bungie Weekly Update

Welcome to the June 20th edition of the Weekly Update. The update is a short stack of pancakes, but it has pictures - and if we're not announcing a project, pictures are the next best thing.

And no, we're not announcing a project.

San Diego Comic-Con

We have no plans to have a Bungie presence at the Comic-Con down in San Diego in July, but our lil homies from Microsoft - Frank and company - will be down there holding a panel on Halo fiction and introducing Tobias S. Buckell, author of upcoming Halo novel The Cole Protocol.

Additionally, they'll be peddling Halo bobbleheads. Have Frank sign yours!


Save the Dates

August 29-31, 2008, here in Seattle. Be there. We will be.


7/7...
... is 17 days away.

Dude You Really Need to...

Last weekend, Shishka and I put down the banhammers and bullying of Bungie.net users to head over to MLG's event in San Diego (there's a briefly exhaustive write-up here) with the main purpose of the being a live exhibition of Cold Storage, a remake of Halo: Combat Evolved map Chill Out.

Next week we'll have a bit more about Cold Storage, but for now, just take a look at the map you've known as Chill Out, and more recently knew "Smuggler."


Finally, Waaaaaaaaaahmbulance

After a thread on the BR got accidentally nuked by yours truly, the creator of said thread had a full-on four-wheels-aflame-sirens-blaring meltdown.

We screenshotted and repurposed it for posterity and eternium.