The Infinite Zenith

Where insights on anime, games and life converge

Tag Archives: Beta

Call of Duty: Modern Warfare II- Reflection on the Open Beta

“Nobody knows what anticipation is anymore. Everything is so immediate.” –Joan Jett

The excitement surrounding Call of Duty: Modern Warfare II (I’ll refer to the 2022 iteration using roman numerals to differentiate it from its 2009 predecessor) is quite tangible, and during the past weekend, the Modern Warfare II open beta was running, allowing me a chance to try the game out for myself: after building a new desktop machine and acquiring a RTX 3060 Ti, I’ve been itching to see how the latest iteration of Call of Duty would handle. The open beta represented the best opportunity to try things out, and while I spent only a few hours in-game, I now have a better sense of what the game requires from a hardware standpoint. On the average match, my machine effortlessly maintains 120 FPS with everything cranked up, and while I have played a few matches where latency was an issue, causing some rubber-banding, the game was smooth overall. Modern Warfare II handles extremely well; movement is crisp and responsive, while the gunplay is immensely satisfying. I never had any trouble moving my character precisely to where I needed to go, and Modern Warfare II‘s firearms feel consistent. While the beta only offers a small hint of what’s to come, Modern Warfare II is stable and performs well. Matchmaking was relatively quick, and once I got into a game, individual rounds were very tight and focused. For classic modes, new maps retain the classic Call of Duty arena-style design, offering fast-paced combat encounters where close quarters firefights and swift reflexes win the day. Modern Warfare II also sees the return of Ground War (a smaller version of Battlefield’s Conquest mode) and a sandbox-like mode called Invasion, which pits human and AI players together in a team-based battle on larger maps, which in turn provides a larger environment for experimenting with Modern Warfare II‘s longer-range weapons. The range of game modes seen in Modern Warfare II‘s open beta is a fraction of the full title, and while I historically have not enjoyed the smaller modes of Call of Duty, Invasion proved unexpectedly enjoyable, giving me a chance to get familiar with the weapons before hopping into a more frantic round of domination with a better idea of how to best use the tools available to me. Surprisingly, this time around, I found myself performing with some consistency: while veteran players and folks with a great deal of spare time will run rings around me, in more matches than I’d expected, I was also able to top the scoreboard.

While skill-based matchmaking meant I was more likely to pitted against players of a similar skill to myself, one aspect of Call of Duty returned to me in full during the course of Modern Warfare II‘s open beta. By default, the voice chat is enabled, and this meant, moments after slaughtering an entire team because of a bit of beginner’s luck on my end, I was screamed at and branded a cheater. In this instant, I immediately recalled why I typically don’t play multiplayer games with voice chat on. I endured the banter befitting of youth and young adults with far more time, and far fewer responsibilities than myself, for the duration of the round. After listening to another player on my team complain about how no one on the team besides himself knew how to play Modern Warfare II, I exited the lobby, dug around the settings and after a few minutes, located the options to completely disable voice chat. The remainder of my open beta experience was more peaceable, although it became clear that Modern Warfare II‘s UI is unintuitive and difficult to navigate. I’ve grown accustomed to Modern Warfare‘s UI, which, by comparison, is very clear and easy to use. The menu system in Modern Warfare II makes it difficult to access one of the game’s most anticipated features: the revised and updated Gunsmith. Modern Warfare II has streamlined the experience by developing a progression system in which one unlocks attachments for a weapon platform, and then these attachments are shared amongst all of the different receivers (weapon types) for that platform. This approach is intended to cut down on grinding, and shared attachments mean one is able to immediately kit out newly-unlocked weapons to bring their handling characteristics closer to what one already has for a previously-unlocked weapon for that platform. On paper, this means using new weapons will be a more enjoyable experience because one won’t need to go through the entire unlock process again. The Gunsmith upgrades are fantastic and cut down on time spent just unlocking stuff, allowing one to experience more of Modern Warfare II. This approach is quite welcome: contemporary titles often drag out the progression to encourage replay, but this makes for an exhausting experience, so seeing Modern Warfare II adopt a more streamlined approach is encouraging. For someone like myself, someone who’s got limited hours to game, a reduced grind means there is incentive to play occasionally without worrying about an overwhelmingly long journey to unlock everything; seeing this in Modern Warfare II does make the game’s multiplayer modes more enticing.

Screenshots and Commentary

  • I decided to start my open beta experience in the Invasion mode and immediately found myself netting a few kills about human foes. The larger size of these maps, coupled with how players are spawned into things, means that one isn’t likely to die instantly after spawning in: this is something that had dissuaded me from playing Call of Duty, and even in bot-only modes, I’ve found that the small map sizes and relative lack of sightlines means that sniper rifles and marksman rifles are less useful in more traditional modes.

  • However, in Invasion, larger maps and the inclusion of AI bots mean that players have a chance to orient themselves and blend in. I started out with the M4, and this jack-of-all-trades assault rifle proved to be a perfect choice for combat at short to medium ranges. Throughout the open beta, the M4 became my go-to weapon choice for most maps and modes, and I ended up getting it to level sixteen before the beta ended. The fact that I could almost reach the level cap for the M4 over the course of two days shows that Modern Warfare II, at least in the beta, has a reasonable progression system.

  • If the pacing is similar in the final release, Modern Warfare II would be a game that works with my schedule: lengthy progression pathways dissuade me from gaming because I don’t have the same time I did back in the day, and games that allow me to play at my own pace usually have the most longevity in my books. Back in Modern Warfare II, after giving Invasion a go, I decided to return to the modes that I typically have the most trouble with. Close quarters environments mean map knowledge is vital, and in Call of Duty, I’ve not learnt the maps anywhere nearly as well as I had say, Halo 2‘s Lockout (which I can still draw from memory).

  • However, in the beginning, Modern Warfare II‘s skill-based matchmaking (SBMM, a means of matching players into servers based on their relative performance) system put me on a server with average players, and after spawning in, I achieved a feat that would not be seen again for the remainder of the open beta: I scored a Killtacular (in Call of Duty terms, a “quad kill”) after four of the enemy team’s players ran around a corner and surprised me, causing me to empty my entire magazine into them in a moment of blind panic. This ended up being the play of the game, and even though my team ended up losing, I ended up at the top of the scoreboard on my team.

  • Domination is basically a scaled-down version of Conquest, in which players must capture and hold points to score for their team. The way maps are designed, there are many flanking routes and plenty of cover around some objectives, giving defenders and attackers a fair chance at doing their part. The maps in Modern Warfare II are intricately designed and features a great deal of clutter, giving them a lived-in aesthetic that stands in contrast with the sterile maps of Battlefield 2042. While Battlefield traditionally excels with larger scale maps, ever since Call of Duty entered the battle royale market with Warzone, their large-scale map designs have improved dramatically.

  • While I don’t play Warzone and generally are not a fan of battle royale, I don’t mind admitting that Warzone is probably the best-designed battle royale game out there. Call of Duty‘s approach to the genre is skill-based: firefights can be turned around if one knows their map and weapons, and the game keeps things simple in its inventory management. Moreover, while Warzone does have weapon cosmetics, the emphasis on having cosmetics is reduced compared to the likes of Fortnite. Seeing MrProWestie and JackFrags in Warzone has piqued my curiosity for the past two years: ever since the global health crisis began, Warzone has offered players a novel experience to immerse themselves in.

  • I sat out Modern Warfare and Warzone in 2019 because my desktop wasn’t able to handle it, and while I don’t feel that I’ve missed out on Warzone, watching people play it did get me interested in giving Modern Warfare a go. Here, I managed to get a five-streak in a match of TDM. I rarely strayed from the basic M4 loadout during the beta because it had been so reliable, and in fact, the only limitation about the starting M4 loadout was the fact that one “only” gets a 30-round magazine. Against individual foes or a pair of enemies, 30 rounds is more than enough, but handling multiple foes in a spray-and-pray situation is quite tricky.

  • Unlike the Call of Duty: WWII open beta five years ago, where I fared extremely poorly, my performance in Modern Warfare II was somewhat improved to the point where I was having fun during my matches. The only exception to this was early on, when I hadn’t figured out how to disable the voice chat, and therefore, was privy to some of the nonsense other players were spewing. The Call of Duty community is known for situations where middle school-aged children play alongside adult players, and their actions on the voice chat have become quite unwelcome.

  • While I didn’t encounter any middle school-aged players, it turns out that the older players are equally as immature: when I joined a TDM round and got a few lucky kills on the opposing team, I was met with screeching and expletives. When I die in a given game, usually, I’ll either handle it quietly and move on (if I was legitimately outplayed), or laugh at the results (especially if I lost in a way that was unexpected or hilarious). Games are about having fun, and I’ve never felt that my sense of self-worth was determined by my KDR or W/L ratio in a given game.

  • Once I blocked out the voice chat in the Modern Warfare II open beta, my experienced improved dramatically. While a squad of friends would definitely find squad channels valuable, playing with what are colloquially referred to as “randoms” (basically, people one doesn’t know in real life or have any sort of online friendship with) means that little is to be gained by using voice chat, especially if said randoms are being immature and spamming chat with juvenile comments. Playing Modern Warfare II with just the in-game ambience and dialogue is more than enough, although on the flip-side, it does show that Modern Warfare II‘s voice chat system is working as expected.

  • The same couldn’t be said about Battlefield 2042‘s open beta: while the game was still functional and mostly stable, the beta from last year was nowhere nearly as smooth as Modern Warfare II. It is clear that, from the state of their respective open betas, Modern Warfare II is in a much better position for launching in October. Here, I’ve switched over to another domination match on what would become my favourite of the maps during the open beta: Farm 18 is an abandoned cement plant turned into a live fire training ground, consisting of a kill house surrounded by flanking routes.

  • In most of the games I’ve played, matches end up being quite close, and I found that while there were times where I ended up losing, my performance would never be so bad as to be demoralising (as I had experienced during the WWII beta back in 2017). I’ve heard that SBMM for Modern Warfare II‘s open beta was very aggressive – when watching MrProWestie, he’d remarked that after doing moderately well in a game, he was subsequently matched into a “sweat” lobby, one where everyone was try-harding to the point where even a full-time content creator was having trouble keeping up.

  • There were a few occasions where I did feel that SBMM put me into a game with players far more skillful or determined than myself, but even in these games (which were rare), I would eventually get into the swing of things and manage to hold my own. In the worst matches I played, my team still ended up losing by a few points, and similarly, in the best matches I played, my team won by a small margin. I did find that during games against tougher foes, I would always gain a sudden burst of performance and mow down foes one after another – while not enough to single-handedly turn the tide of battle or turn my KDR positive, such moments were fun and encouraged me not to drop out of a game mid-match.

  • Breenbergh Hotel was another map I particularly enjoyed. For domination, two capture points are located inside the hotel (one in the restaurant, and one in the lobby). The last capture point is located outside. The corridors and clutter in the hotel meant that long-range weapons aren’t viable here, and for this particular match, I spawned in with the base M4 without any attachments; I levelled up far enough to unlock custom loadouts, and as I worked on ranking up the M4, I eventually picked up the 45-round extended magazine for it.

  • Between the extended magazines and suppressor, I suddenly found myself much better equipped to score back-to-back kills before needing to reload: while tap-firing works well for medium range combat, in close quarters, the sheer chaos means that automatic fire ends up being the norm. Having fifty percent more ammunition to work with increases one’s survivability in these situations, and while the tradeoff is a longer reload time, reloading when out of combat offsets this particular disadvantage.

  • The new gunsmith has a similar UI to the gunsmith from Modern Warfare, but the largest difference now is that players can change out the weapon’s receiver. I didn’t get quite far enough to unlock the M16 receiver, but this approach represents a significant improvement over the original Modern Warfare, which had separate weapon unlocks for each individual weapon. Modern Warfare II allows players to unlock attachments for a weapon family, and then unlocking receivers grants access to some (or most) of one’s existing attachments. In my case, had I actually reached the M16 receiver, most of the attachments I already had for the M4 would carry over, allowing me to instantly start using the new gun without needing to work my way back up from the iron sights.

  • For kicks, I ended up equipping a slow-firing marksman rifle and got the first kill of that match. Such a weapon is unlikely to work out in the close-quarters environment that makes up the domination mode, but it was quite amusing to score kills in this way. The nature of Modern Warfare II‘s more traditional maps and modes mean that most players will prefer automatic weapons. To level up and experience longer-range combat, one must either play Ground War or Invasion, both of which provide a larger-scale match which changes up the play-style.

  • Prior to Modern Warfare, Call of Duty was known for valuing speedy reflexes above tactical play. While I’ve fared moderately well in these ranges as a result of preferring close-quarters combat from my Halo days, after I made the jump to Battlefield, I slowly acclimatised to more tactical, methodical gameplay at medium ranges. The maps in Call of Duty don’t always cater to this style, but I found that, rather than dying to a bad flank, I ended up suffering most at the hands of campers, who prefer remaining concealed in an area and scoring kills by ambushing unsuspecting players.

  • Camping will become a more popular approach in Modern Warfare II, since the minimap now hides all foes unless they’ve been spotted by a UAV or other equivalent means. The result of this is that the UAV became one of the more popular score-streaks, since it allowed one to reveal the position of enemies on the minimap for their entire team so long as the streak was active. In the absence of the UAV score-streak, I ended up using my grenades more generously, tossing them into a room and letting them detonate before I entered for myself.

  • One map I ended up playing a great deal of was Valderas Museum, which is a complex of corridors and rooms surrounding a large, open central area. The combat flows very rapidly on this map, so unsurprisingly, the M4 was my go-to weapon for this map: it fires fast enough to deal with foes at close quarters, but is accurate enough to pick off foes from across the courtyard. I ended up trying out the SMGs, and while they’re fantastic at close ranges (like their counterparts from Battlefield, they’re reasonably accurate even when hip-fired), larger maps with long sightlines make them a little less viable.

  • Besides the killtacular I got early in the open beta, I would end up scoring several double kills and triple kills once I found my flow – my customised M4 and its extended magazine proved to be an invaluable tool for clearing out capture points from attacking foes, while the ACOG sight gave me better clarity at longer ranges. Since Modern WarfareCall of Duty has done a fantastic job of ensuring all attachments have their pros and cons. While I cut my teeth in the Battlefield camp and prefer the larger-scale all-out warfare of Battlefield over the close-quarters chaos that characterises Call of Duty, recent Call of Duty titles have shown me how Infinity Ward is catching up in terms of engine sophistication.

  • After nearly a decade of being on the backfoot, I feel that Call of Duty has now matched DICE and their Frostbite Engine in terms of sophistication, and moreover, Call of Duty appears to be using their engine more effectively than Battlefield uses the Frostbite Engine – Battlefield 2042‘s beta suffered from performance issues that endured even into the game today, whereas Modern Warfare II was very smooth. DICE has worked tirelessly to fix these issues, although in my case, I’ve found that the massive upgrade in hardware is what allows me to play Battlefield 2042 now.

  • While the open beta was a fantastic way to ascertain that my machine can handle Modern Warfare II, what I’m most excited about is the campaign, which is the main reason why I play and enjoy Call of Duty. Call of Duty campaigns vary in size and scope, but they always offer an engrossing story that gives me a chance to discuss topics that I otherwise wouldn’t talk about – the political aspects in first and third person shooters invite conversation surrounding these matters, whereas most of the anime I watch tend not to cover such topics. I have found that anime tends to use politics to convey very specific messages, whereas Western entertainment is a bit more open-ended.

  • In earlier Call of Duty games, the “overkill” perk allows one to carry two primary weapons, and the default loadouts in Modern Warfare II‘s open beta similarly have two primary weapons. Here, I swapped over to the shotgun and promptly downed a foe defending one of the capture points. I don’t play the multiplayer extensively, so I don’t know which perks are the most effective for different scenarios, but I have heard that Modern Warfare II changes the way perks work: besides two base perks, players will automatically unlock two special perks to change the game dynamic.

  • I ended up returning to the Invasion mode so I could do some sniping, and en route to a good vantage point, I ended up being ambushed. The sniper loadout comes with the Signal 50 by default – this was the only long-range weapon available in the open beta, and it was obscenely powerful. However, being a sniper rifle, players are left at a disadvantage if they’re in close quarters. Fortunately, the sniper loadout comes with an automatic pistol which works in a pinch. Battlefield 2042 recently introduced the PF51, which fulfils a similar role.

  • The Signal 50 proved to be a remarkably fun weapon to use, and I ended up going on killstreaks with it. Here, I unlocked the Cruise Missile, which lets one drop a missile onto a target similarly to how Battlefield V allowed players to call in a V1 or JB-2. While higher kill streaks offer powerful bonuses, I found that overall, the best score streak unlock is the UAV owing to its ability to instantly reveal enemy positions on the minimap. The removal of enemies on the minimap after they discharged an unsuppressed weapon became a point of contention for long-time players. Some argue that this encourages camping, while others hold that this means players can equip other attachment besides suppressors.

  • One of my favourite moments during the Invasion game mode came when I managed to score a kill at 295 metres. Unlike Battlefield 2042Modern Warfare II retains a means of showing players the distance of a particularly impressive kill, and I admit that it was quite satisfying to land this kill. During this match, I ended up climbing onto the water tower at Sarrif Bay and spent the better half of the game sniping foes from afar.

  • Towards the end of the beta, I unlocked a battle rifle. Although I’d initially struggled with the weapon, after getting a few kills with it, I ended up hitting my stride. During this game, my team was outmatched, and I don’t mind admitting that I was more interested in trying out the battle rifle than I was in playing the objective. However, despite losing the match, I led the team on the scoreboard: I was finding that I was regularly finishing first or second in spite of my generally poor knowledge of Call of Duty mechanics.

  • Overall, I found myself having a great deal of fun during the Modern Warfare II open beta, significantly more than I’d anticipated, and considerably more than I did during the WWII open beta. I had sat out the Modern Warfare and Cold War open betas in previous years because I’d modified my previous machine in a way that prevented it from being updated to Windows 10. Last May, I ended up merging the user profiles back together and then updated my machine to Windows 10, but by that point, the i5 3570K was beginning to show its age. With my new desktop, I’m looking forwards to having the hardware needed to run games for the next six to eight years.

  • I’ll wrap this post up with one final kill from the Hurricane SMG and remark that I’ve just finished Modern Warfare‘s campaign. I’ll write about my thoughts on this come October, and in the meantime, I’ve got one more post lined up for September – I’ve finished Spy × Family‘s first season and found it a remarkable anime, so I look forwards to sharing my thoughts on why this anime is universally acclaimed, as well as some of the things that Spy × Family does especially well from an espionage and surveillance perspective.

With the open beta in the books, I now have a much better sense of what Modern Warfare II entails. Beyond my usual reasons for keeping an eye on a Call of Duty title, I know that Modern Warfare II now offers a fantastic alternative to the close-quarters combat of the usual maps, and the unforgiving environment of Warzone, which requires a squad and time commitment to yield maximum enjoyment. Invasion has proven to be a surprisingly enjoyable change of pace: maps are significantly larger than the typical maps for domination and TDM, giving one a chance to snipe and use vehicles, but at the same time, the allowance for respawns means that there is tolerance for making mistakes, and applying learnings from said mistakes immediately. The last time I played a Call of Duty open beta, it would’ve been five years ago, when WWII was released. Back then, the multiplayer gameplay proved underwhelming and clunky. However, it is plain that Activision has improved their game considerably since then: Modern Warfare II looks incredible, and for the first time, I see myself playing a Call of Duty game’s multiplayer component. In conjunction with a campaign that looks excellent, there is a very good chance that I will be checking out Modern Warfare II shortly after it launches. Between a promising title and the hardware to do so, I am presently leaning towards picking the game up after I’ve had the chance to to preview the campaign’s content and see for myself how things handle following launch. I’ve traditionally picked up Call of Duty games for their story missions and therefore don’t get much replay out of the games, but in the case of Modern Warfare II, between the presence of multiplayer modes that interest me, in conjunction with a Spec Ops mode and the fact that I’ve enjoyed all of the Call of Duty campaigns I’ve previously played, I am reasonably confident that Modern Warfare II would be a game that engages me. All that’s left now is for the early-adopters to give me a bit of additional insight into what I’d be getting into, and then I’ve got enough to make a decision as to whether or not Modern Warfare II is worth the full price of admissions, or if it will join my library at a later date.

Battlefield 2042: A Reflection on the Open Beta

“This strength test is all about what Battlefield 2042 does to your computer, and not what your computer does to Battlefield 2042.” –J. Neilson, Forged in Fire

Entering the Battlefield 2042 open beta, the biggest question on my mind was whether or not my aging rig would even be able to run DICE’s latest Battlefield title at passable frame-rates. The minimum requirements had called for an Intel i5-6600k, which overall, has about a five percent edge in terms of performance over the nine year old i5-3570k I’m currently running. The open beta represented the best way to, without charge, test whether this CPU stood any chance of opening Battlefield 2042, and after I finished my preload in Tuesday night, I went about the remainder of my week as usual. When I was granted access to the open beta on Friday, I promptly opened my client after the day’s work hours ended, and immediately found myself faced with sluggish, choppy performance: after joining a match and parachuting over to the rocket hangar at capture point bravo, I came under fire from some enemy players. I ducked away into cover, then got the jump on one of my pursuers as they turned away, and after aiming down the M5A3’s iron sights, I dumped the magazine into my foe to earn my first kill of the beta. All of this happened at around 24 FPS, and it became clear to me that my eight-year-old machine had hit its limits. I subsequently headed over to a remote corner of the map, away from the combat, set all of the visual effects down to medium, and was met with a surprising result: Battlefield 2042 began running at a still-choppy, but playable 40-50 FPS (dropping to about 30 FPS on a small handful of moments). I thus finished my first match and went on to unlock a range of weapons to experiment with. During my play-testing, I found that my GTX 1060 was at around 60 percent usage, but my CPU was struggling the entire time in-game: Ivy Bridge processors have a feature called “Turbo Boost”, which kicks in whenever the CPU requires additional horsepower. The hardware automatically overclocks the CPU, raising the clock speed to give this extra performance while at the same time, keeping the assembly within safe temperatures. However, running Turbo Boost for prolonged periods still places a bit of a strain on a CPU that is eight years old, and it is clear that either this build of Battlefield 2042 still needs to be optimised before launch, or the time might be approaching where I will need to build a new rig. While my machine did encounter difficulties with the Battlefield 2042 beta (I suffered two blue screens in total), I was otherwise very impressed that the beta ran at all, with the frame rates that it did. Overall, my rig survived: this is equivalent to a blade taking on a few rolls during the infamous strength test on Forged in Fire, but otherwise, remained intact. My machine passes the strength test, although whether or not it will KEAL is a different matter entirely (albeit one that I’ll have to wait until after launch to find out about).

Because of periodic performance drops, my own experiences with Battlefield 2042‘s open beta are not complete or wholly representative of my performance in the game. Lag led me to miss shots, fail to respond quickly enough in a firefight, or even waste ammunition on what I thought was a player (but was actually a player model that hadn’t been updated properly). In spite of this, the beta was still immensely enjoyable. The first thing I noticed was that the scale of battle is larger than ever. It makes sense as to why Battlefield 2042 would require more CPU power to fully experience: the chaos of 128-player maps is a massive step up from the 64-player maps of previous games, corresponding with an increase in the processing power needed to calculate and keep track of everything. Moreover, gun-play was satisfying, and weapons handled very consistently: after getting used to their recoil patterns and learning to position myself better in firefights, I began rediscovering my old enjoyment of tap-firing down a distant foe. Every kill is satisfying, and Battlefield 2042 appears to have altered things so the kill system is more similar to Battlefront II’s, where dealing appreciable damage to an enemy is rewarded the same amount of points as scoring the kill itself. Similarly, the movement system was relatively smooth: features from Battlefield 1 and V, like crouch-sliding and vaulting return, creating more options for moving around the map and escaping otherwise deadly situations. The core mechanics of Battlefield 2042 appear to work well for the game. However, it is clear that this is a three-month old build: the UI is unwieldy, and critical features did not work in the beta. I was unable to issue squad commands, thank players for reviving me or open the map at all. These issues are something the team indicates that the release build will address. The specialist system is a larger issue for Battlefield 2042: during my games, I noticed that teamwork was practically non-existent: the lack of dedicated medics and support players meant no one was topping off health or ammunition, and there was no incentive to do so. The lack of restrictions on weapons and gadgets allows a sniper to constantly top off their own ammunition, and assault players can easily heal themselves. One possible fix for this would simply be to restrict gadgets to certain specialisations, and similarly, every specialist should have access to one unique weapon class, and subsequently, there can be all-class weapons, much as how Battlefield 3 and 4 had done so. The specialist system is ingrained in the game, but if these minor adjustments aren’t too tricky to implement, their addition would define specialist roles more clearly and return team-play elements to the game. One element that currently is a deal-breaker is player visibility: this was an issue in Battlefield V and favoured campers. Battlefield 2042 has not addressed this issue, but this time, players can blend into their surroundings even when actively moving. Moreover, the lack of clear team indicators introduces new problems: I found myself shooting at teammates in some firefights because there hadn’t been anything to show they were teammates. While I’m very much in the minority who thinks this way, I find that the return of 3D spotting would be helpful. Players should always be able to spot for themselves, and then recon players can spot for their teams as a class perk. The inclusion of 3D spotting would reward players for thinking tactically ahead of a firefight, and force players to consider how they move around a map, as well. Overall, while Battlefield 2042 shows promise, it is still early to be determining if DICE has properly learned from the aftermath of Battlefield V.

Screenshots and Commentary

  • If there were a single screenshot to sum up my experiences with Battlefield 2042‘s open beta, this would be it: a stunning view of the Guiana Space Centre as a storm rolls in. Battlefield 2042‘s theme is climate change and its impact on conflict, but unlike its predecessors, which featured a single-player campaign, Battlefield 2042 will launch without a campaign, with its story being told by the maps’ design. The large-scale effects of climate change means that Battlefield 2042‘s maps can be set across the world and need not be tied to any one region, as with previous Battlefield maps.

  • The first kill I got in Battlefield 2042 came with the M5A3 assault rifle, a fictionalised version of the SIG MCX series that is chambered for the 6.8mm SIG cartridge. I ended up choosing a different screenshot for my first kill because that moment had been too dark, and because I am a little superstitious in games, I believe that I’ll have a better experience in a given open beta if I get my first kill before my first death. In practise, the M5A3 has a good firing rate and high accuracy, especially when equipped with the extended barrel, Cobra vertical grip and the Maul Hybrid 1.5-3x sights.

  • I didn’t have too many opportunities to play armoured vehicles in the open beta; pilots were being much too aggressive, and the lack of teamwork meant that shoulder-fired anti-air weapons weren’t too effective at taking them down. Land-air balance has always been an issue in Battlefield games: good pilots can single-handedly control entire matches, and some design choices in previous Battlefield games, like the Ilya-Muromets, were downright broken. Modern settings means a wider range of anti-air options, and Battlefield 2042 will need to give players more options against air vehicles in order to balance things out.

  • The infantry combat is generally my favourite aspect of a given Battlefield game, and here, I help the team to defend against capture, capitalising on the high-ground to mow down a player running along the catwalk below. Orbital is the map featured in the beta, and despite being a very large, open map, there’s enough variety in the map design so all weapons can be effective, depending on where one is. The M5A3 is probably the most versatile weapon available in the open beta, having enough accuracy to pick off enemies at range (especially if one tap fires and runs the right attachments) and enough firing rate to react quickly to someone at close quarters.

  • During matches, the rocket on the launchpad will sometimes launch, creating a particularly impressive visual spectacle for players, comparable to the rocket launch of both Five Centimeters per Second and Hathaway’s Flash. I’ve seen my favourite Battlefield YouTubers attempt to board the rocket, and they ended up phasing through the geometry before learning that the rocket tops out at an altitude of five kilometres. This resulted in many laughs. For me, I didn’t have anything quite so exhilarating: I witnessed two rocket launches during my run of the Battlefield 2042 open beta, and after dying to a sniper during my first launch, I decided to take cover so I could view the second launch in peace.

  • Battlefield 2042‘s hitmarker system is quite unlike anything I’d previously seen: they appear to be much more subtle and difficult to spot. However, every kill was satisfying to earn, especially those longer-range shots. One nifty feature about Battlefield 2042 is that the Maul Hybrid optic has an integral red dot sight attached to the main optic, making it easy to switch between 1.5x magnification and 3x magnification with the push of a button. The dynamic attachment system reminds me a great deal of how Crysis handles things, and I imagine in the completed game, players will unlock multiple attachments, and then pick four they want to carry into battle at any given time.

  • Since we’re now back in the modern era, a wide selection of effective LMGs are finally available again. The only LMG available in the open beta was the LCMG, a fictionalised version of the Knight’s Armament Company LAMG; in reality, this was meant to be a lightweight and modular LMG that could adapt to a variety of situations. Despite its promise, the LAMG never saw any military use, although I have seen this weapon before in The Division 2, where it is called the Stoner LAMG and was one of my favourite weapons in the endgame, at least until the Hunter’s Fury gear-set became available.

  • I’ve always had a fondness for LMGs in Battlefield: early in every Battlefield game I play, I am not so familiar with the recoil patterns on assault rifles, and tend to waste my ammunition hitting air in firefights. However, with their larger ammunition capacity (offset by a longer reload time), LMGs are a bit more forgiving and allow me to lay down sustained fire. More rounds in the air means an increased probability something will hit my foe (i.e. “spray and pray”). The LCMG can be customised with AP rounds to increase its efficacy against light vehicles: one of the stranger design choices in Battlefield 2042 is the fact that weapons can have different ammo types. While cool in theory, I’ve actually never felt any need to switch out the standard ammunition.

  • Here, I score a kill with the Kriss Vector, known as the K30 in-game. The K30 resembles its counterparts from other games in that it has a high rate of fire and therefore, is particularly well-suited for CQC. The base K30 comes with a 20-round magazine, but DICE was nice enough to provide the extended magazine option, which allows for a total of 40 rounds per magazine. I ended up scoring a pair of kills in the rocket hangar with it while making my way to the top. The scale of the buildings in Battlefield 2042 are immense, and capture point bravo is a particularly fun one to fight over, since the rooftop is open to helicopters, and the team holding it must be cautious of players sneaking in from below, as well.

  • Ribbons finally make a return in Battlefield 2042: DICE had gotten rid of them in Battlefield V, but they had been present in earlier Battlefield games as an incentive for teamplay, as well as rewarding players for doing well. I’ve had a fondness for ribbons, since accumulating them gave insight into what kind of tendencies I had as a player. Medals were also fun to earn, although I also remember that the big frustration with them comes from being killed while attempting to take a screenshot after earning one: because of the way my key mappings are set up, I need to either take my hand off the mouse or keyboard in order to capture said screenshot.

  • While I’d never been effective with anti-armour weapons in Battlefield 3 and 4, after Battlefield 1 and V, I’ve become much more comfortable with equipment in this category: a little bit of teamwork can mean that, even on foot, vehicles are not unstoppable threats. Battlefield 2042‘s brings back the M2 Carl Gustav Recoilless Rifle from Bad Company 2 as the main anti-vehicle option. It has a very slow reload, but can devastate light vehicles and even take a third of a tank’s health away in a single shot. I imagine that more anti-vehicle weapons, like the RPG-7, SMAW and AT4 could be available in the full game.

  • Here, I score a kill on someone calling themselves “Shizuka_hiratsuk”, evidently named after Oregairu‘s Shizua Hirasuka, using the DM7 (the Daniel Defense DDM4 V7 in real life) marksman rifle. This semi-automatic rifle reaches out a little further than the M5A3 and is a solid precision weapon that fits my play-style. Although the ACOG sight and its chevron reticule was a bit tough to use, the weapon can nonetheless deal excellent damage at range, making it a solid option. Players with anime names have always stood out to me in multiplayer first person shooters, especially when they get the upper hand over me.

  • However, this never happened once in Battlefield 2042: normally, after dying to another player, their name is clearly displayed for me to check out, and Battlefield also indicates how many times we’ve gotten one another. However, the UI meant I never got around to seeing names in prominence, and moreover, I never found myself antagonised by a single player because of the fact that maps are so large. Rather than facing 32 players, I’m now facing 64, so it’s less likely to run into the same person twice. The larger player count has had one additional side-effect on my gaming, and I’m actually a lot more relaxed when I’m being beaten by different people.

  • I’m not anywhere as competitive as I was seven years ago, which was when I was really getting into Battlefield 3, but a part of me still enjoys getting back players who got me. In one entertaining moment during the beta, I was killed by a sniper at capture point alpha. Realising he was chilling on one of the geodesic domes, I promptly changed my kit out for the SWS-10 and managed to shoot him in the head. I’m rocking the recon specialist here, which comes with a spotting drone, C4 and my personal favourite, a passive radar that indicates whether or not there are any hostiles nearby.

  • The assault specialist is equipped with a grappling hook for getting around quickly: like the Q-Claw from Agent Under Fire, the grappling hook is a fantastic tool for ascending buildings and gaining a vantage point quickly. If memory serves, the assault specialist’ perk is being able to have more mobility compared to the others. This high-mobility play-style means that one might actually be better served running with a PDW or shotgun for close-quarters dominance. On the topic of Agent Under Fire, Thanksgiving Long Weekend has proven to be the perfect time to dust off the old GameCube and enjoy some old-fashioned humans vs AI bots on Town and Castle. Unlike yesterday’s blue skies and sunshine, today’s been grey and snowy, making it perfect for gaming, and since the global health crisis kicked off, I’ve been doing a lot more with the GameCube, so we actually ended up faring moderately well against the AI bots on maximum difficulty.

  • Had the open beta come out in October 2018, I probably would’ve been happier for it: by October, the Xamarin project had been deemed ready for release, pending a few bug fixes and tests. Conversely, back in September, the Xamarin project was in dire straits; there’d been a large disagreement about what constituted as HIPAA compliance, and it was put forth that HIPAA compliance demanded a 26-digit alphanumeric code that was given to users on sign in. In the end, the firm’s CEO stepped in, determined that the 6-digit code I was proposing was still compliant and allowed me to continue with my work. The resulting sign-in and onboarding became an order of magnitude simpler for my troubles, and I returned home just in time to spend a few days on the Rotterdam map in Battlefield V‘s open beta.

  • My experiences in Battlefield V‘s beta led me to pick the game up in November 2018, and by that time, I’d received an offer for a new iOS developer position, allowing me to leave behind my first start-up’s woes and its connection to the computational oncology firm in the US. That time period was characterised by relief to be setting aside work that was beginning to tax me more than it excited me. Out of vain curiosity, I decided to take a look to see what became of the app I finished, but as it turns out, the app has been stricken from both the App Store and Play Store.

  • While the computational oncology firm has advertised that mobile app would be a major part of their ecosystem, it is a little disappointing to see no advancements on the mobile side of things in the past three years. Reminiscing about these moments makes me immensely thankful that with the Battlefield 2042 open beta, I am afforded time to enjoy the beta without worrying about whether or not the JSON responses coming from the backend would arbitrarily change without warning: this time around, my main concern was whether nor not my machine could even run the open beta, speaking to its age.

  • One of the most exhilarating and terrifying moments I had during the entire beta was when I saw my first tornado: I had spawned on a squad mate, but the tornado changed direction and immediately headed for us. The tornadoes that strike Battlefield 2042‘s maps appear to be EF0 (or EF1s at most): while they’re capable of lifting vehicles into the air and easily carry players, the tornadoes don’t do any appreciable damage to the map’s buildings, creating a bit of inconsistency (a tornado capable of throwing vehicles would also uproot trees and shred roofs from houses, which is EF3-level). However, as a gameplay mechanic, I’ll let this one slide and note that here, as I seemingly glide towards my death, a bolt of lightning also strikes very close to my position, creating a surreal moment.

  • Lightning strikes in Battlefield 2042 have EMP effects and will disable vehicles, as well as scramble the player’s HUD; this is a clever effect that speaks to the dangers of how relying on complex electronic systems can leave one in a tough spot should said systems go down. Fortunately for me, I ended up steering myself away from the tornado, which also changed course at the last second, and after landing on the ground, I immediately set about trying to help my team turn around a losing match even though it’d been too late.

  • In a different match, I’ve switched over to the support specialisation and are running with the PBX-45, a copy of the LWRC SMG 45 that actually proved to be unexpectedly effective and fun to use. The SMG 45 was first introduced in 2015 and entered production in 2019. Firing .45 ACP rounds, the SMG 45 is a newer weapon and accordingly, has not appeared in many games. Battlefield 2042‘s PBX-45 marks the first time the SMG 45 appears in Battlefield (previously, the SMG 45 was in Call of Duty: Modern Warfare as the Striker 45).

  • In the days of Battlefield 3 and 4, PDWs and SMGs were hipfire machines whose small size made them laser-accurate and perfectly suited for close-quarters combat. In fact, during my Battlefield 3 days, once I unlocked the MP5K, it became my default go-to weapon: with the laser sight and extended magazines. Battlefield 1 featured SMGs as the primary for the assault class, and by Battlefield V, SMGs were the default weapon for medics. Although their applications have changed, all Battlefield SMGs (and PDWs) retain excellent hipfire performance.

  • The PBX-45 is a remarkably entertaining weapon to use, and one more thing that I’m particularly fond of its the reload animation: if one isn’t reloading from empty, the operator will pull the old magazine out and swap it for a new one, but keep the old magazine in hand to stow it. However, if reloading from empty, the old magazine is discarded. Cool reload animations have been a part of Battlefield since Hardline, where DICE really began having fun with the reload animations, but in Battlefield 1 and V, DICE upped their game by providing unique reload animations based on a weapon’s ammunition state.

  • I managed to capture this beauty of a lightning bolt while a tornado was tearing up the far side of the map here. In reality, taking stunning lightning photos is a skill and requires familiarity with the techniques. Professional weather photographers like Warren Faidley have taken some of the most iconic pictures around, and as a child, I was always fond of checking out weather books from the library to admire these images. In games like Battlefield 2042, lightning lingers on the screen for a fraction of a second longer than it does in reality, and that means so long as I hit the screenshot button quickly enough, I’ll have myself nice photo.

  • The weather patterns in Battlefield 2042 aren’t anywhere nearly as disruptive as the snowstorms of Battlefield V, and while visibility lowers whenever a storm blows in, it’s not bad enough to interfere with gameplay: even though the screen does get covered in water droplets from the rain, visibility isn’t severely degraded. Having said this, the tornado can be quite disruptive, and once the novelty wears off, it’ll become something that can negatively impact a match for players: the tornado locks down a large section of the map, and under the right circumstances, might even disrupt things enough for the other team to mount a comeback, meaning that the outcome of a given match can come down to chance rather than skill.

  • Here, I quickly reload the G57 pistol after drawing it and scoring a kill to save myself from certain death. Modern shooters tend to provide players with a sidearm as their secondary, a weapon to switch over to it when their primary runs dry. I imagine that the G57 is modelled after the Heckler and Koch Glock G17 (evidenced by the grooves on the slide’s rear. Battlefield has historically treated the Glock line of pistols as a fast-firing, moderately hard-hitting and reliable pistol. Pistols can be customised on the fly, as well, although during the open beta, there was no option to attach a suppressor.

  • While I only had six hours in the open beta, I did put in enough time to unlock the M44 Revolver, which looks like the Model 44SS6 .44 Magnum. Unlike the G57, whose strength lies in its accuracy, ease-of-handling and rate of fire, the M44 kicks like a mule and hits like a truck, dealing massive damage when it lands a successful hit. During the height of my Battlefield days, I used to run with the MP-412: this revolver still dealt excellent damage, but had a slightly faster firing rate than the .44 Magnum, meaning it could be counted on in a pinch.

  • Altogether, I played twelve rounds of conquest during the open beta, and of these twelve rounds, I only won three of them. I’m not sure what the story is, but even though I was playing the objective each and every around, I was more likely to wind up on the losing team than the winning team. However, I will note that 12 games is too small a sample size to draw meaningful data from. During earlier Battlefield games, some days, I’ll go on the most ridiculous lucky streaks where I’d play three winning games in a row, and then after a break, come back to play two more victorious matches.

  • Then, on other days, I could go and play three losing matches in a row. The law of large numbers states that over time, my victories and losses will trend towards an average and approach 50 percent from either the left or the right. However, my tendency to play the objective meant that in general, I always won slightly more often than I lost. In Battlefield 2042, outside of determining if my machine could run the game at all, my other goal had been to try as much of the infantry firearms as I could. Because of the way the Battlefield 2042 beta worked, I was able to get a very good idea of what the different weapons handled like, and here, I’ve brought the LCMG back out.

  • Owing to the haste of my deployment, I dropped right into a firefight and didn’t have time to change out my optics or underbarrel options. In spite of this, I managed to score a few kills while pressing forwards with my team into the hangar. In modern military shooters, I’m fond of equipping optics right away, since having a red dot sight or ACOG can make target acquisition much easier. However, I found that in moments where I only had iron sights, I was having considerably less trouble with them than I had before. This is like a consequence of the fact that playing so much Battlefield 1 and V in the past five years has meant that I’ve become accustomed to using iron sights for tracking targets.

  • Back in Battlefield 1, most weapons were actually better off without the crude sights available in a WWI setting, and some weapons had highly clean posts that made finding targets straightforward. Similarly, some weapons in Battlefield V had decent iron sights that could be used without much trouble. Since iron sights no longer bother me, when I play through other games like Call of Duty, I can be comfortable trading off the sights for other attachments. Of course, where sights are available, I’ll still use them: here, I’m running the PBX-45 with the K8 holographic sight, which is clear and easy to use.

  • Just for kicks, I ended up switching over to my M5 Recoilless rifle and shot a player with a rocket, since they were out of my PBX-45’s effective range. Had I attempted to engage them at this range, they would’ve noticed me throwing rocks at them and ducked for cover. Conversely, by expending a M5 round on them, I was assured of the kill, which I’m sure would’ve been a shock. I used to do something similar in Battlefield 1: since the assault class’ SMGs didn’t have much reach, I would use the AT rocket gun to pick off foes that I couldn’t otherwise reach without alerting them to my intentions.

  • Here, I managed to headshot a player calling themselves Gryphin2004 (a Family Guy reference, perhaps?) using the PBX-45, at a range that I didn’t think the weapon would work at. This particular player had killed me several times in a row by camping in the building, and it was with great satisfaction I managed to get him back one before the match ended. There weren’t many frustrating moments during the beta, but if I had to name one, dying to this camper was one of them. I’ve long disliked players who camp, since it shows excessive concern for one’s KDR over the team results, and in fact, campers are only second to cheaters in my books, when it comes to players who shouldn’t be in the game.

  • Here, I managed to score a double kill with the M5 Recoilless Rifle on a tank below: by the end of the beta, I was right at home with the M5. Players also have access to an anti-air weapon similar to the FIM-92 Stinger, and while I never got much use out of these weapons, developers have indicated that to balance them, they might make them a one-hit kill against air vehicles. If this is true, this would be a boon for folks on the ground: air vehicles are an annoyance, and in every match I played, enemy pilots went unchallenged, while for the most part, pilots on my team were not anywhere nearly as effective. Knowing that anti-air weapons could swat them out of the skies in a single hit would force pilots to play more cautiously: aircraft are equipped with countermeasures, but they have a cooldown, so a part of the skill in flying would include knowing when to back out of a fight.

  • Out of curiosity’s sake, I also ended up giving the AK24 a shot. This weapon appears to be the AK-12, a modernised AK-47, and in Battlefield 2042, hits harder than the M5A3. On the flipside, it also has a much larger recoil: I found the weapon to be quite uncontrollable when the Maul Hybrid sights were equipped. On the other hand, the iron sights, K8 and Fusion Holo sights don’t accentuate the recoil too much, making them my preferred choices for combat. Overall, however, I did prefer the M5A3 over the AK24: the M5A3 is laser-beam accurate with the right attachments, and I’ve had success with this rifle at ranges I didn’t think possible: one of my most exciting moments was burst-firing down a foe at over a hundred metres with the M5A3.

  • My experiences in the beta suggests that weapons of Battlefield 2042 are going to handle in distinct ways, and then the attachments will further accentuate a weapon’s strengths (or mitigate its weaknesses). The ability to switch attachments out on the fly is actually a pretty clever mechanic, since players with foresight can add to their inventory the attachments that they feel will work for them, and then in between matches, they might be able to customise their inventory to fit a particular play-style. Unfortunately, because of where this beta was, no deeper customisations were shown.

  • Since DICE has advertised that Battlefield 2042 will have a deeper progression system than that of Battlefield 1 and V, I am hoping this translates to something that was more similar to that of Battlefield 3 or 4‘s: Battlefield 3 had the perfect amount of unlocks, while things in Battlefield 4 felt a bit overwhelming. Documentation from DICE indicates that players will have unlocked everything they need to be successful by level 100. At the time of writing, I have no idea how long this journey would take: with earlier games, it took me about a year to get everything unlocked, and this was assuming an average of two to three hours of play every week.

  • During one match, I spawned onto the hangar rooftop at capture point bravo and decided to equip the SWS-10 for some sharpshooting. This is the TRG M10 in real life, a bolt-action rifle manufactured by the Finish company SAKO. Chambered for the .308 Winchester round, the TRG M10 can also fire .300 Winchester Magnum and .338 Lapua Magnum rounds, as well: the M10 is an upgraded, modular design that was introduced in 2011, and one of its most noteworthy features is that the toolbox for changing out the rifle’s barrel, bolts and handguard is built into the weapon itself, allowing it to change between different calibres with ease.

  • In Battlefield 2042, veterans have reported that the sniping is a little off, but during moments where long-range shots connect, it is immensely satisfying: I managed to pick off foes on the ground below from up here, and it felt incredible to fire a shot, watch it sail over to the target and strike them in the brainpan. Unfortunately, Battlefield 2042 doesn’t display the distance a headshot was made from in its beta, but these shots were incredible to land. It took me a few shots to get a feel for how the SWS-10 handled, especially with respect to bullet velocity and drop, but one thing I did find strange was the fact that the weapon appears to already have a straight-pull bolt, removing the need to scope out and chamber a new round in after one round was fired.

  • In a later match, I ended up running into a player called “not_alexus_marie” and promptly pasted their pate several times into the ground: curiosity got the better of me after I collected these screenshots, and I’m now wondering if this is the small-time Twitch streamer from Illinois that I wasted so casually. Battlefield 2042‘s lack of scoreboard, and an unusual UI in the death screen meant that during this beta, I remember those whom I’ve felled more vividly than those who outfoxed me in combat. While some gaming journalists are suggesting that some players are already using cheats in the beta, I never once felt that my foes were using software to gain an unfair advantage over others. Any time I died was a consequence of my own lack of spatial awareness, poor positioning, or the fact that my reflexes are no longer what they used to be.

  • On occasions where players looked like they one-shotted me or shot me through walls, it became apparent that my aging hardware might’ve created that discrepancy. Indeed, when I began playing more cautiously, I found myself staring at the spawn screen with a much lower frequency, and here in the beta, I do not believe I’ve run into any cheaters during the course of my six hours. DICE has stated that Battlefield 2042 will use Easy Anti-Cheat, a well-known and robust system which, in conjunction with its in-game reporting system, and an implementation of both an IP and hardware ban, should be enough to deter cheaters, which have run rampant in games like Battlefield V and Call of Duty: Warzone.

  • Cheaters were responsible for my increasing disinterest in Battlefield V, more so than any other shortcomings of that title (whether it be the poor enemy visibility, inconsistent TTK/TTD decisions, decision not to visit iconic WWII Theatre in favour of obscure ones), and what was baffling was the fact that players on my own team would adamantly refuse to acknowledge that they were playing against a cheater, despite said cheater going 120-1 five minutes into the match. In this day and age, the desire to cheat in a multiplayer game is a consequence of a desire for notoriety, for a bit of extra internet fame.

  • By yesterday evening, I’d become quite familiar with all of the open beta’s weapons and had a passable idea of how the mechanics had worked, enough to be scoring consistently well. In the last full game I played, I ended up 19-19 despite having fallen into a 2-10 hole early in the game. The team I was with was still defeated, but my own personal performance suggests that, if the time allows for it, I could probably still have a good time with Battlefield 2042‘s main game modes. Towards the end, I began running with the engineer specialisation, which brings with it an automated turret for locking down certain areas by creating a distraction.

  • During the chaos of one firefight, I ended up accidentally switching off my M5A3 for a SWS-10, and since players were swarming the capture point, I was able to pick a few off with headshots. Observant readers and players who participated in the open beta alike will have noticed that Battlefield 2042 has sectors that must both be held before it can be considered to be under one team’s control. This approach would be a fantastic way to improve team play, although speaking truthfully, the lack of a working command system meant that in the end, I lone-wolfed things for the entire duration of the beta.

  • While my approach means that any squad will make short work of me, I was a little surprised to find individual players running around the map without any support, such as this individual here. I found them on their lonesome and proceeded to make short work of them before they even got a single shot off. In a squad with good communications, as soon as one member is fired upon, the squad can move in to defend one another, secure the area and revive anyone that was downed. I’ve only ever played Battlefield once with friends during an office team building event five years earlier, but I still remember how effective we were: we topped the scoreboard, was the best squad and ended up carrying our team to victory despite none of us being particularly exceptional FPS players.

  • One of the biggest challenges I faced in the beta was with the gunner seats in vehicles: they were extremely jittery, and it was nearly impossible to get a good shot off on a target. During one of my final matches, I spawned into an Apache attack helicopter’s gunner seat and manned the 30 mm cannon with gusto, helping to clear the ground for my team in a round my team had no hope in heck of winning. I’ve never been much of a pilot myself, but I do have a fondness for manning the gunner seats in vehicles. With a good pilot, I am able to really do damage in the gunner’s seat.

  • It suddenly strikes me that the more recent Battlefield releases have all coincided with a milestone in my life: Battlefield 4 launched after I graduated from the Bachelor of Health Sciences programme, and Battlefield 1 released after I finished graduate school and begun the transition over into industry. Battlefield V launched right as I got a new job, and Battlefield 2042‘s launch date is going to be very close to my possession date. At the time of writing, there’s a few more things I have to tend to ahead of this, but I am very excited about things.

  • Truth be told, I am surprised that things had happened as quickly as they did; even back in August, I’d only been house hunting and never thought that a property meeting all of my requirements would become available on the market this soon. A lot can happen over the course of a year, and while 2021 saw its share of challenges, the year also saw numerous positive changes. I’ve been incredibly lucky in many regards, and this is something I am immensely thankful for. If I were making decisions on the basis of emotion alone (as opposed to reason and logic), Battlefield 2042 would be an easy purchase simply for the fact that it coincides with a major life event, much as how Battlefield 41 and V did.

  • However, this isn’t how I roll: instead, whether or not I end up buying Battlefield 2042 will be determined by how well the game runs at launch and whether or not Battlefield Portal fulfils my requirements. Provided the game can run well, and Portal offers what I am looking for, then Battlefield 2042 will be worth the cost of admissions. The game has most certainly been fun during the open beta, and here, a solitary kill with the LCMG marks the last one I got before the servers shut down; I had just started a match, but it was getting late, so I decided to call it quits after getting one more kill.

Having put a total of six hours into the Battlefield 2042 beta, the main deciding factor now as to whether or not I’ll pick up the game after it launches, or if I will wait, is determined by a few things. The first is whether or not DICE does indeed optimise the game so it’s not pushing my CPU to 100 percent utilisation for extended periods. I’ve heard that people with more recent CPUs still experienced the same issues, so it is possible that building a new PC might not be the solution to this. Waiting to hear from early-adopters who buy the game will allow me to gain more information before making a decision. Similarly, the open beta has only shown one game mode (Conquest) on one map (Orbital). Battlefield 2042‘s biggest feature is Battlefield Portal, a full-scale sandbox mode that allows players to have full control in designing games for themselves. On first blush, this mode appears even more enticing and immersive than Battlefield 2042 proper. Depending on what is available and possible within Battlefield Portal, this alone could be worth the price of admissions (assuming my machine can run things smoothly). Finally, the open beta evidently is an incomplete build of the game that is not production-ready: numerous issues do need to be addressed, from UI layout, functionality and performance before DICE can have a smooth, satisfying launch. Historically, DICE’s records with launches are mixed: Battlefield 4 was a disaster, but Battlefield 1 was exemplary. Overall, my position now is simple: I will wait until around the holiday season to determine whether or not Battlefield 2042 joins my library. Building a new PC is straightforward enough, and my current machine still runs Battlefield 2042 in a satisfactory manner, so the main deciding factor now is going to be primarily seeing how well Portal works in practise. The prospect of being able to play bots on a private session to experiment with outrageous scenarios (like how well a single M1A2 fares against 20 Tiger I tanks), or join servers with outlandish game modes designed for relaxation rather than competition, is most enticing. Similarly, I am getting up there in the years to be squaring off against youth with faster reflexes: the ol’ fingers and brain no longer move as quickly as they did when I was a university student. Gone are the days where I could survive a firefight against an entire squad, so on days where I don’t feel like fighting real players, having the choice to mess around in Battlefield 2042 maps and modes at a more relaxed pace would also be welcomed. As such, this Battlefield 2042 open beta has been very informative for me: I know my rig can (just barely) run Battlefield 2042, the setup is still fun enough for me, and once I have a little more information on things like features and Battlefield Portal following the game’s launch, I’ll be able to make a more informed decision on things.

Halo Infinite: A Reflection on the Open Beta

“This is my last fight; a true test of legends! Our story…will outlive us both. Set a fire in your heart, Spartan! Bare your fangs! Fight hard! Die well!” –War Chief Escharum

Originally set for launch in November 2020, 343 Industries ended up making the decision to delay Halo Infinite‘s release to December 2021 to ensure that their latest instalment of Halo was functioning as expected. While at launch, Forge and co-op will not be available, 343 Industries decisions demonstrates the level of commitment to quality that is expected of developers; in recent memory, games like Cyberpunk 2077 and No Man’s Sky had illustrated the price of launching games on schedule even in the knowledge the game was incomplete, with inevitable results. For me, since I’m in no particular rush, these delays are acceptable: in fact, as far as gamers go, I’m quite unconventional in my habits, and news of Halo Infinite‘s launch date, as well as the presence of a technical test, drew my attention primarily because I am running a machine that is now eight-and-a-half years old. As such, the concern for me was a matter of whether or not Halo Infinite would even run on this machine: the game requires an Intel i5-4400 and GTX 1050 Ti at minimum, along with 8 GB of RAM. On paper, my machine’s GTX 1060 and 16 GB of RAM should be sufficient. Moreover, the i5-3570k is supposed to be around eight to fifteen percent faster than the i5-4400k under real-world conditions despite being older. However, it isn’t until one actually attempts to run a game that performance can be tangibly ascertained: this was my primary goal with Halo Infinite‘s technical test, and after around four hours of gameplay spent in the open beta, playing against both AI bots and other players have given me a much clearer picture of what the way forwards looks like. On my aging setup, Halo Infinite is generally very playable at 1080p, maintaining a consistent 60 FPS with the visual settings set to the “high” preset. There were frame drops on occasion, although I did not find that they occurred as a result of activity on the screen (e.g. entering a crowded area with many players, or the result of visual effects resulting from weapon fire and explosives usage). The client testers were provided with was generally stable, although I did experience a two separate instances where the build did freeze or crash to the desktop as a result of bad memory access. Outside of these issues, I have satisfied myself with the fact Halo Infinite appears to run with reasonable smoothness on my machine.

Looking beyond the fundamental matters of performance and stability, Halo Infinite‘s technical test gave me a chance to try out the gameplay mechanics for myself. Trailers had shown that Halo Infinite would feature the return of equipment that had previously been employed in entertaining ways during combat, including a grappling hook and shield wall. However, the most critical element in any Halo game (or shooter, for that matter) is the movement and weapon system. Halo Infinite delivers on both. Player movement has been refreshed to be in line with more modern games; besides the return of a sprint system, players have slightly faster movement than the Spartans did in the original Halo titles, and there is now a vaulting system that allows players to grab ledges, making navigation through maps easier than before. Altogether, modernising movement in Halo Infinite means maps can similarly be updated to utilise creative elements that weren’t previously possible. The gun-play in Halo Infinite is similarly excellent. Weapons feel powerful, and the time-to-kill is reasonable. Players being shot at have enough time to react and get out of a situation. Keeping cool under pressure will allow one to win a firefight even if one did not start shooting first, but players who start a combat engagement with a sure aim and utilisation of the right timing and equipment will come consistently out triumphant. The weapons themselves are fun to use: the basic assault rifle has come a very long way from the Halo: Combat Evolved incarnation and is now reliable, while the Halo 2 battle rifle returns as the BR-75. Players are given feedback in response to landing shots on an enemy, and scoring kills. While quality-of-life adjustments in Halo Infinite makes every successful kill more visceral than in earlier Halo titles, the core gameplay largely remains untouched: everything still feels like it did with Halo 2. Overall, the gameplay mechanics of Halo Infinite are satisfying and consistent, retaining all of the elements that made the original Halo games great, while simultaneously bringing some of the best features in contemporary shooters into Halo.

Screenshots and Commentary

  • While I’ve had two weekends to try the Halo Infinite beta out, these days, I’m don’t spend the whole of that time in game: the weather of late’s been gorgeous, and I’ve been greatly enjoying all that the autumn weather has to offer. I ended up spending the afternoon yesterday walking out to a grove of trees that turned golden-yellow, and then swung by an overlook at the park’s southern end. Shortly after spawning into my first-ever match on Live Fire, the original map that August’s Halo Infinite technical test featured, I immediately snapped up the S7 Sniper Rifle and got a double kill with it against the bots. My intention in this open beta was not to see how much gameplay I could experience, but rather, to see if my machine could even run Halo Infinite, and so, having the option of playing against AI bots was most refreshing.

  • One of the drawbacks about open betas are that some players deliberately use their vacation time to experience the beta, and consequently, have put in upwards of eight hours before I even finished downloading the client. Playing against these individuals means being annihilated in the blink of an eye, which would’ve degraded my ability to run the game for longer periods of time. Conversely, with AI bots, I was able to stay alive for extended periods and properly stress-test my machine, as well as see what happened whenever many grenades were thrown and equipment deployed.

  • On the whole, Halo Infinite runs very well, and there were no player actions that seemed to cause any performance issues. However, during one match, my client began stuttering and then outright froze, forcing me to quit (and incur the early quit penalty). After I finished and quit another session, my machine suffered from a blue screen of death, with the error code indicating my GPU had been overtaxed. DOOM Eternal has done this to my machine on occasion, where the computer would display a blue screen and force a restart after I’d quit the game.

  • These sorts of things happen infrequently, but I imagine that it is a driver problem more than anything; even people running more recent GPUs, like the RTX 2080 Ti, have reported this issue on some occasion. However, as noted previously, these events are infrequent enough so that they’re not super-disruptive. Here, I’ve switched on over to the Recharge map, which is located inside a hydroelectric plant. I’m armed with the basic MA40 Assault Rifle, a capable all-around weapon for close to medium range combat, and the MK50 Sidekick as my sidearm.

  • The MK50 is more similar to the M6C line of pistols, being a compact and lightweight weapon compared to the hard-hitting magnum pistols of earlier Halo games. In most matches, I discard this weapon straight away for a different secondary weapon: here, I’ve got the VK78 Commando, an automatic tactical rifle with a twenty-round box magazine. Accurate and reliable at range, the VK78 replaces the DMR, reaching further out than the battle rifle, but firing more rapidly than the sniper rifle. This weapon very quickly became a favourite for me; while I used to be a big CQC person in Halo, my experiences in Battlefield has meant that medium range engagements are something I’m more comfortable with.

  • This strange-looking weapon is the Ravager, a Banished weapon that fires arcing plasma rounds that can deal damage to vehicles and infantry alike. The weapon is not reloadable and utilises a battery, but built-up heat is not automatically dissipated, so players must use the reload button to vent the weapon. During the open beta, I found that the UNSC and classic Covenant weapons proved to be the most reliable and consistent in firefights; the new Covenant Pulse Carbine, for instance, is a burst-fire plasma rifle with the Carbine’s form factor, although its behaviour was a little difficult to get used to, so I ended up ditching it. Conversely, the Plasma Pistol and Needler still work just as I remember, making them excellent secondary weapons.

  • Bazaar is a map set in Old Mombasa and therefore, is reminiscent of Halo 2‘s “Outskirts” mission in terms of aesthetic. This arena-like map is laid out in a manner most similar to Counterstrike‘s classic Dust and Dust II maps, featuring a central open area and two “bases” that make the map suited for two-team battles, like CTF. These sorts of maps bring back the memories I have of playing Halo 2 on Windows Vista: back then, I had considerably more time than I did today, and I remember (with a twinge of regret) that I spent the most of my summer, prior to starting university, playing custom games in Halo 2‘s multiplayer.

  • In retrospect, I would’ve been better served spending that time with a summer job, specifically, at one of the local bookstores: while the work experience here wouldn’t be relevant to the undergraduate research experience I did end up picking up, and the pay isn’t anything to write home about, it would’ve been nice to get out and do something constructive with my time. Once I did enter university, I spent my summers doing research instead: this was both relevant and engaging. On the flipside, I also remember that most days, I also went for long bike rides on the best of days.

  • The new CQS48 Bulldog is a combat shotgun fed from a rotary magazine. Compared to the old pump action shotguns, the Bulldog has a much faster reload and can fire faster, but does considerably less damage than its predecessors. Here, I used it to decimate an AI bot at close quarters, earning myself a Running Riot spree in the process. The bots in Halo Infinite‘s training mode can have their difficulties adjusted, but during the online matches where I teamed up with other players against the AI bots, said bots appeared to have had their difficulties set to the easiest level: every match I played was a blowout (or, in Halo terms, “Steaktacular”).

  • Here,  I stick a bot with the plasma grenades. The keen-eyed reader will have spotted that the evergreen trees in the background look a little blocky and low-resolution; I originally wondered if this had to do with the fact that I was running Halo Infinite on the default low settings, but even after turning the settings up, the trees remained of a low quality. It is probably the case that not all assets or visual effects have been finished at this point in time: 343 Industries sent out a stable build to test their server capacities and see how things handle under load for this test flight.

  • After switching over to higher visual quality, I did not notice any appreciable improvement in the visuals. Fortunately, there was also no degradation in performance: 343 Industries intended this test more for their servers rather than for us players, and I imagine that the build we were given, while ready for play-testing, is not optimised yet. Assuming this to be the case, it could mean that I’ll have no trouble running the launch version with reasonable settings.

  • While some elements of Halo Infinite are still works-in-progress, others are remarkably polished and look production ready. Here, after scoring a double kill on some AI bots, I made to reload my weapon and happened to capture a screenshot of the reload, which highlights the level of details that went into the weapon models. Reloads have come a very long way since the GoldenEye 64 days, where the animation simply involved ducking the weapon off screen and raising them once the reload finished.

  • The HUD in Halo Infinite has been modernised so that its layout is identical to that used in contemporary shooters. Previous Halo games put the ammunition display counter on the upper right of the screen, and the grenade inventory on the upper left. However, more popular shooters like Half-Life and Counterstrike had their ammunition counters on the lower right. Call of Duty and Battlefield follow the same layout, as do other well-known shooters, so it made sense to migrate the ammunition counters over to the lower right.

  • The shield indicator firmly remains at the top of the screen, and players will have noticed a small health bar underneath that also recharges. This bar was originally hidden in Halo 2 through Halo 4, only returning in Halo 5 to provide a visual indicator of how much health a player has once their shields are drained. Health can be depleted very quickly if the shields are dropped, and players traditionally can fall to a single headshot if their shields are down, so as soon as the upper screen flashes red in response to shields being low, one’s first move is to get to cover as soon as possible (or finish off a foe and then get away when safe to do so).

  • During the beta, I had a plethora of double kills, but owing to the map and team sizes, I never got around to getting any triple kills despite coming close on a few occasions (teammates would finish off the enemies before I could). It has struck me that 4 on 4 matches mean that the coveted Killtacular would be exceptionally rare. Back when I was a secondary school students, some of my friends were absolutely determined to get a killtacular and so, hosted LAN parties every other week. Since graduating from university, everyone’s gone their separate ways, although right up until the global health crisis started, we were still able to gather on some occasions for LAN parties.

  • A big part of the fun about LAN parties was that, since we didn’t do them often, they always took forever to setup, as we fumbled with wiring all of the Xboxes together using Ethernet cables. This was one constant that remained with us no matter how many times we did the LAN parties, but we never minded; while waiting for setup, conversations would turn towards all manner of topics. Of course, during LAN parties, the folks with Xboxes back home would tend to do the best, and the remainder of us would be lucky to get a few kills here and there. This never mattered, though, since LAN parties were always fun.

  • Here, I’ve finally come upon the BR-75 Battle Rifle: a burst-fire weapon that was introduced in Halo 2 and subsequently became the most recognised MLG weapon in the games. With its three-round burst, the battle rifle was a reliable four shot kill at medium ranges (three bursts to strip the shield, and then a headshot), making it a highly consistent and dependable. On consoles, I’ve never been able to make use of the weapon properly, but with the mouse and keyboard, the battle rifle has very much become my favourite starting weapon in Halo.

  • I’d like nothing more than to have fun and relive the glory days of the old LAN parties in a comfortable chair at home. However, when I returned to The Master Chief Collection‘s multiplayer last year, I found that the design paradigm behind Halo‘s multiplayer today is completely incompatible with what I am looking for. I expect to be able to drop in and out of matches without penalty and play in a relaxed fashion, but 343 Industries have a quit penalty, and players in the so-called “social” tier are still aggressively competitive.

  • In conjunction with the fact that players will universally plug in a controller to capitalise on the fact that controller have full aim assist and increased bullet magnetism, playing with the mouse and keyboard set up leaves me at an immense disadvantage, so I ended up calling it quits by the time Halo 3 joined The Master Chief Collection. Here, I managed to swipe the SPNKR rocket launcher and blew up an enemy. Playing Battlefield and Call of Duty has changed my usage of explosive weapons somewhat: in modern military shooters, anti-armour weapons don’t have enough splash damage to be effective in an anti-infantry role, but in Halo, the rocket launcher is meant to be a power weapon, possessing limitations but otherwise, remains highly effective against personnel and vehicles alike.

  • For Team Slayer matches, the AI bots are more than fine, but it turns out that the bots are also present in smaller games of CTF and Territory Control: the very fact that the bots do work suggests to me that it would be possible to include a mode with bots only so players can get used to the maps and weapons without affecting their stats. For players like myself, bot-only matches would also represent a nice way to simply go mess around for ten minutes and play at my own pace: the days where I could dedicate a few hours towards ranking up my character and items are long past, and I prefer games where I can pop in and drop off whenever I wish.

  • Towards the end of the open beta, my old skills began returning to me, and I managed to get a double kill off the bots with the battle rifle. The bots, while far easier than human players, still have the same shields and health as players do, making them a great way to get a feel for the TTK against human players. I elected against playing real players for as often as I could for the open beta, since the aim of this exercise had been to test the game. I won’t have this luxury during the Battlefield 2042 beta; DICE had announced their beta to start on October 8 and will run through the ninth.

  • However, players who preordered or have EA Access will be able to start their test on October 6. Preloading begins on the fifth, and here, I will note that while I am a Battlefield fan, I’m not so dedicated as to preorder the game yet. Instead, I will sit down for a few sessions on Friday night and throughout Saturday where I am able. Similarly to Halo Infinite, my goal will be simply to see how well my machine can handle Battlefield 2042. Unlike Halo Infinite, however, Battlefield 2042 won’t have a campaign, and what determines whether or not I end up buying it will be how extensive Battlefield Portal‘s AI bots are.

  • Back in Halo Infinite, I start a match on Behemoth, a larger map more suited for Big Team Battles rather than infantry-only matches. Vehicles are available, and this makes the match particularly suited for the larger matches of CTF or territories. I’m actually not too fond of these larger maps, since the vehicles disappear almost the moment the match starts, leaving me to hoof it across the map. Conversely, the smaller, arena-like maps are my favourite, since their focus is on infantry combat. In Battlefield, maps are designed so players can spawn onto points allies have already captured, on squad-mates who are out of combat, or on special beacons, so larger maps aren’t a problem.

  • The Volt Piercer (informally, the Shock Rifle) is one of the most exotic weapons I’ve seen in a Halo game and would not look out of place in something like Planetside 2 or Tribes Ascend. Firing an electrolaser bolt with a range of up to 300 metres, the weapon functions similarly like a sniper rifle and can kill with one headshot. However, it can also arc off nearby enemies, and two shots can temporarily disable a vehicle. I’ve not had the chance to try the plasma pistol’s overcharge against a vehicle, but in Halo 4, the overcharge could disable a vehicle and render it vulnerable to boarding.

  • Overall, the modes against AI bots were fairly compelling, and I had a great deal of fun here: the weapons of Halo Infinite definitely retain the handling and feel of the classic weapons. Of course, the most fun for me will be seeing where all of these weapons come into play during Halo Infinite‘s campaign. Towards the end of my time in the open beta, I hopped on over to Fragmentation for a Big Team Battle match up, marking the first time I’d fought human players during this open beta. I admit that I was a little reluctant to join such a match: back when 343 Industries was flighting Halo 3, I ended up with a miserable experience owing to the fact that the game openly favoured controller players.

  • However, when I joined my Big Team Battle match, I was fortunate in that the size of the map meant that players were spread out enough so that I did end up with a chance to explore the map and get a few kills here and there, as well as work out where all of the weapons were. I’m not sure if Halo Infinite will bring back the old loadouts from Halo 4, which allowed players to spawn with a primary and secondary (non-power) weapon of their choice. If given the choice, I’d almost always pick the battle rifle and magnum in Halo 4. However, since the battle rifle and Commando tactical rifle are found on the weapon racks as pickups, I imagine that Halo Infinite could be going back to the basics.

  • For some reason, Halo Infinite describes the Commando as a light machine gun: while the Commando is automatic, its smaller ammunition capacity and description as a precision weapon means it doesn’t satisfy the definition of what makes a light machine gun: LMGs don’t necessarily fire full-sized cartridges, but their function is to fulfil an infantry support role (e.g. providing covering fire). The small magazine on the Commando is too small for the weapon to be used in this role, so I am wondering if 343 Industries are going to continue referring to the Commando as an LMG once the game launches.

  • I managed to pick up another Shock Rifle and began firing on distant enemies, but because the weapon’s handling is unlike the UNSC weapons, I wasn’t able to place the best shots on my opponents, who were trying to steal our flag. However, I did land two hits on two different foes, and my teammates astutely picked them off. This match ended up being a game of attrition: players were very much focused on defense and felt reluctant to go on offense, which makes sense, since everyone is still new to the map: I did make one attempt to take the enemy flag, but died instantly, since half their team was hanging back.

  • As the match drew to an end, I ended up picking up the Heatwave, a Forerunner hard light weapon designed for close-quarters combat. The weapon is most similar to a shotgun, and in its default mode, fires a horizontal pattern of projectiles. However, it can be altered to fire in a vertical pattern. The former sounds good for crowd control, and the latter has proven to be excellent against individual targets. The weapon resembles the UNSC Rail Gun (Halo 4), and indeed, when I picked it up, I was expecting the weapon to handle like the Rail Gun.

  • During this final map on Fragmentation, I ended up going 13-16 and helped my team to win the game with a score of 1-0, and to cap things off, I’ll show that it is possible to get kills with the Sidekick even though it is a sidearm meant for use if one’s starting primary weapon is out. All things considered, this wasn’t a bad first time playing against real players, and I did have fun just running around on the map and engaging lone players before ducking away. With this, Halo Infinite‘s open beta comes to a close, and I imagine that the next time I play Halo Infinite will be once the campaign launches.

Having now had the chance to experience Halo Infinite for myself, it is clear that my aging machine will run Halo Infinite in a passable manner, and the gameplay itself retains everything that made the original Halo games so enjoyable. As such, my final verdict on whether or not I will pick this game up is simple enough: I have seen enough to know that I will have a good time with the game once it launches in December. The multiplayer aspect to Halo Infinite is actually free-to-play, and revenue is to be generated by a seasonal battle pass: 343 Industries will have seasons, and players can purchase the passes for seasons they wish to unlock cosmetics for. Unlike other developers, who have time restrictions, Halo Infinite‘s battle pass system will be such that one could buy the first season pass a year later and still be guaranteed a fair chance at completing everything. While my main interest in Halo has always been with the campaigns, a free-to-play multiplayer gives another more opportunity to see how my desktop handles Halo Infinite before I step into the campaign should the need arise (otherwise, if the footage of gameplay looks promising, and the benchmarks look good, picking up Halo Infinite will be an easy decision). The sum of my experiences here in Halo Infinite‘s technical test have been positive. If the final product can iron out the more serious of the issues I experienced, as well as optimise the game to further improve performance, 343 Industries will have made a very compelling case for me to pick up the single player campaign at launch price. With this being said, the multiplayer alone is not something I see myself playing extensively; in this day and age, I no longer have the time to play through multiplayer games with a lengthy progression system. The appeal of having a single player campaign is precisely that I can experience something at my own pace. However, if Halo Infinite were to include the ability to play AI bots in all of the same game modes and maps that are available to in PvP modes (complete with match score and time limits), I would be ecstatic; the AI bots seen Halo Infinite are actually pretty convincing when set to the higher difficulties, and while they understandably should not contribute to one’s completion of progression items, being able to go into a private server and mess around with the AI bots would be immensely enjoyable, perfect for folks who are interested in having a more laid-back opportunity to have fun in their own manner of choosing.

Feedback and Reflections on Insider Flighting with The Master Chief Collection: Halo 3: ODST

“A university is just a group of buildings gathered around a library.” –Shelby Foote

A few weeks ago, 343 Industries conducted a flight for Halo 3: ODST, during which several campaign missions were playable, alongside the fondly-remembered Firefight mode and an updated Halo 3 multiplayer which was intended to address issues surrounding hit detection in the retail build. This marks the first time that I’d ever played Halo 3: ODST, an entry in the Halo franchise that is often forgotten amongst the giants like Halo 3 and Halo Reach. As I progressed through the campaign missions, it became clear that at least, for the campaign, Halo 3: ODST is ready to roll. Having experimented with both the Rookie’s free-roam in the deserted streets of New Mombassa and the flashback missions, I found no major issues with gameplay or performance. Events trigger appropriately at the stipulated points in the campaign, movement and shooting feels solid. The smart HUD and VISR function as expected. Although the campaign playlists meant levels were played back-to-back rather than as the campaign originally arranged them (the flashback missions should be started when the Rookie finds evidence in the streets of New Mombassa), I imagine that these are merely loading mechanisms, and the campaign should be functional when it hits the Master Chief Collection later this month. I will, of course, be reserving my impressions of Halo 3: ODST, with regard to the themes, enjoyment factor and contributions to the franchise in a dedicated post once the retail version becomes available, and in this brief reflections post, I will be showcasing my exploration of the New Mombassa streets on legendary difficulty.

The playlist for the city streets only allowed the Rookie to explore New Mombassa with Halo‘s toughest enemies, bringing back memories of the year that Halo 3: ODST came out for Xbox 360. Back in those days, I was acclimatising to life as a university student. During that first term, I found myself in an unfamiliar environment, and my classmates all had different schedules. Having made a small mistake during registrations early on, I ended up reshuffling my schedule to fit everything in, resulting in a chemistry lab that ran into the evening. On days where I had labs, I would spend my free time studying in the basement of building housing the largest lecture halls on campus. Down here, it was quiet, making for a good place to hit the books in peace. After finishing any review and assignments I had, I would head to the chemistry labs in the building over. During these study sessions, I listened to Halo 3: ODST‘s soundtrack, whose film noir elements created a compelling sense of loneliness that I would come to associate with that far-flung corner of campus. During those late nights, darkness crept back into the world as fall gave way to winter. Exploring the deserted hallways of campus had a melancholy feel to it, a melancholy that the Halo 3: ODST captures well, and at present, after spinning up Halo 3: ODST and wandering the streets of New Mombasa, memories of those days return to me as I locate a biofoam injector, bent-up sniper rifle and a helmet embedded in a screen. Provided that the retail version of Halo 3: ODST handles as smoothly as it did in the flight (there were no game-breaking bugs, crashes or performance issues that I found during the time I spent exploring), I anticipate that Halo 3: ODST will be a very smooth launch.

Screenshots and Commentary

  • Halo 3: ODST was originally released on September 22, 2009 for Xbox 360 and became a distinct entry in the Halo franchise for its focus on an Orbital Drop Shock Trooper (ODST) known as the Rookie. These special forces are known as “Helljumpers” for their mode of being deployed into a combat situation, and during the Battle of New Mombasa, a small squad is sent on a clandestine mission that goes awry.

  • The flight allowed me to check out most of Halo 3: ODST‘s campaign, but for this post, I’ll purely focus on the streets of New Mombasa after dark – there is actually quite a bit going on in the story, well beyond the Rookie investigating New Mombasa for clues on a stormy night, so I’d figure that I’d showcase some of the more interesting places around New Mombasa now and then save the campaign moments for the full post later on.

  • The biggest surprise I had going into the New Mombasa playlist during the flight was that this was locked to legendary difficulty, which created an additional element of immersion. Even simple grunts and jackals, which are trivially easy on normal, become a challenge to engage, and every individual brute is a mini-boss, capable of absorbing a magazine-and-a-half of sustained fire from the suppressed submachine gun. It therefore became a matter of picking my fights (and avoiding them) as I picked my way through the deserted city streets.

  • Compared to its standard variant, the M7S suppressed submachine gun is a little more accurate and deals less damage per shot. It also possesses a reflex sight that is linked to a smart optic, giving the M7S a bit more reliability at long range. The Rookie has the M6C/SOCOM, a semi-automatic pistol with an integral suppressor and a VnSLS/V 6E which allows for shots to be placed with accuracy out to a longer range than the M6C. Against grunts and jackals, a single well-placed headshot will deal with them swiftly, and despite being a relatively weak weapon, it is also immensely satisfying to use.

  • When Halo 3: ODST released, the university had not yet undergone construction work to modernise it, and as such, campus relied entirely on sodium-vapour lamps to illuminate pathways with an orange glow. While waiting for a ride on evenings where I had chemistry labs, I would wander around the darkened campus, which had a very similar atmosphere and aesthetic as the streets of New Mombasa.

  • In retrospect, I was never too fond of chemistry labs, since they were set in an old building that, while still satisfying safety code, had outdated equipment that could be fickle at times. I found myself wishing I was back in secondary school, which had more modern facilities and a generally more relaxed atmosphere: university chemistry labs were a ways more stressful and we were also assessed based on how successful our yields and results were. The labs themselves dealt with relatively simple, practical applications of the theory we learnt in lecture, and at least in my first year, I performed decently well in the laboratory component.

  • Even during the academic semester, campus empties out very quickly at night, with only a handful of classrooms being occupied by lectures or tutorials. My days thus fell into a familiar pattern: once a week, I would stay late on campus to do my labs, and I had a four hour break on those days, so I would study in the basement hallways of the largest lecture building on campus until it was time to start the lab. Because my linear algebra course had the lightest textbook, I would often do most of my linear algebra here while listening to Halo 3: ODST‘s soundtrack.

  • In this way, my first term would pass in the blink of an eye, and after final exams ended, I found myself with a decent performance. During the winter break, I ended up reconfiguring my schedule somewhat to reduce the amount of time spent on campus after dark, and because the Halo 3: ODST soundtrack reminded me of those lonely days spent drilling on eigenvalues and testing for invertibility by means of Gaussian Elimination, I promptly stopped listening to the Halo 3: ODST soundtrack. Halo 3: ODST similarly fell to the back of my mind as I started the new semester, which I spent studying with friends in a much more well-lit, inviting space in the student centre.

  • During the moments exploring the more remote reaches of campus in the time after a lab and before my ride arrived, I typically walked around the outside of campus to figure out the best routes between different buildings, or else went into the basement network that linked most of the science buildings together. In my first term, all of my courses were concentrated in the sciences area, so it was easy to get around, but later on, courses would be scattered in unusual areas based on classroom availability, so knowing how to get between buildings quickly was of value. However, the engineering building was intimidating to me, and I rarely went in there early on. It wasn’t until the summer I began exploring campus more fully.

  • I managed to find a shotgun during my trek through New Mombasa, which was an immensely valuable asset in that I finally had something with the stopping power to deal with brutes, even on legendary. One thing I did notice during the Halo 3: ODST flight was that I never encountered the battle rifle, which was my go-to weapon in Halo 3 for being a solid all-around weapon: Bungie deliberately cut the battle rifle from Halo 3: ODST in order to really drive home the idea that the Rookie and other ODSTs were vulnerable, lacking the overwhelming power that the Master Chief’s presence brought to each fight.

  • When I first opened up the New Mombasa streets playlist, I was quite unaware that it had been on legendary difficulty, and even after I took out my first enemy squad, the difficulty didn’t seem to be an issue, although I had felt that I used a bit more ammunition than I’d intended to. However, after reaching the first building and entering a courtyard full of grunts, what I’d thought to be an easy fight suddenly turned into a slaughter, as a few stray plasma rounds ended up wiping me out.

  • Playing on legendary is supposed to be the iconic Halo experience: enemies are incredibly tough and hit hard, and the player’s own damage and durability are reduced. On legendary, it becomes clear as to just how vulnerable the Rookie is on his own, when even a lone grunt can wipe him with a plasma pistol. In conjunction with the lack of a motion sensor integrated into the HUD, one must use the Visual Intelligence System, Reconnaissance (VISR) display to plan out their next move, knowing when to fight and when to quietly sneak by.

  • Other parts of Halo 3: ODST‘s campaign are set during brighter hours of the day, and the Rookie’s segments are extremely dark. Fortunately, the VISR also has a special low-light mode that enhances brightness somewhat, as well as highlighting enemies in red, resources in yellow and allies in green. For these screenshots here, I’ve disabled the VISR so that each scene is as they would appear, but during combat situations, I leave the VISR engaged for improved visibility. The VISR is also immensely valuable for locating evidence, emitting audible cues as one closes in on something important.

  • Because YouTube had not been quite as user-friendly during the game’s original release, Halo 3: ODST remains the Halo title I’m least familiar with, and as such, the flight actually marks the first time I’ve seen much of Halo 3: ODST – this iteration of Halo did not come with a full multiplayer component, instead, using Halo 3‘s multiplayer and consequently, I don’t think any of my friends picked up the title. We never did Firefight during LAN parties, so ODST wasn’t really a title that any of my friends had experience with.

  • Instead, Halo 3: ODST stands out to me for its music, which has a completely different feel than the epic guitar and Gregorian Chant from earlier Halo games. Instead, composers Michael Salvatori and Martin O’Donnell adopted a jazz noir sound that evokes a mysterious, contemplative feeling through the use of saxophone. However, rather than the contemplative tone that traditional jazz noir creates, Halo 3: ODST has a more melancholy sound for its nighttime segments. The combat sequences and flashbacks, on the other hand, have a more traditional, militaristic sound.

  • That Halo 3: ODST balances both out, creating the film noir atmosphere for the Rookie’s segment, and then returning to the form that Halo is known for, creates a very compelling atmosphere during different segments of the game. The film noir tone, however, calls for the orange-yellow glow of sodium vapour street lights, and some years ago, my city transitioned away from those to LED lights. The university followed suit shortly after, replacing all of the aging lamps with modern LED ones.

  • This simple change transformed the campus’ nightscape to be a shade brighter, less shadowy. In the years following, I carefully timed my labs so they did not occur during the evenings, and most of my late-night stays on campus usually resulted from taking exams. In my graduate degree, I stayed late to help with various events around campus or invigilate exams. On the occasions where it was dark by the time I left, I noticed that the brilliant white lights of the LEDs helped to create a more inviting environment.

  • While the flighting has ended, and we’re likely due to see Halo 3: ODST somewhere later this month, I note that I’ve deliberately chosen to write about the flight now because it coincides with the first day of lecture, which admittedly took some getting used to. I believe today should also be the start of a new semester, as well. As I moved through my university program, the first day of lecture became less noteworthy: by graduate school, I regarded the first day of lecture as little more than a time for when hallways became busy again.

  • For the actual Halo 3: ODST discussion, I’ll delve into more plot-related elements and gameplay mechanics. There are enough differences in Halo 3: ODST to warrant playing with a different style, but some elements remain unchanged (such as the fact that ODST can hit as hard as Master Chief can when meleeing enemies). With this being said, it’s time to wrap things up: I realise this is my third games-related post in a row, so I assure readers that my next post will return to anime.

  • Altogether, it took about two hours to hit each piece of evidence and wrap up the streets of New Mombasa in full on legendary: once I reach the building that leads into a complex housing the Superintendent’s data core, this playlist concludes. I will be returning at some point in the future to write about Halo 3: ODST proper, and having gotten this bit of reminiscence out, that leaves me free to focus entirely on Halo 3: ODST without lapsing into nostalgia about university.

Once Halo 3: ODST hits retail, all eyes will turn towards Halo 4, the first Halo title that 343 Industries developed. The previous Halo titles, Halo 3 in particular, have set the precedence for what to expect, and moving into the future, I am anticipating a very exciting launch for Halo 4, as well. It is a little surprising to see The Master Chief Collection nearing completion, around a year after Halo Reach first released to PC, and in all honesty, The Master Chief Collection coming to PC was probably the biggest event in gaming this year, outstripping even the likes of Call of Duty: Warzone for me. Admittedly, a lot of gaming these days has begun straying from the path of what makes them enjoyable: the Battle Royale genre is one I have no patience to play, either dispensing with skill (such as Fortnite, where dirty tactics like camping are accepted) or falling to its own success (Call of Duty: Warzone and its cheaters, for instance). Seeing classics make their appearance on PC has been most welcome: Halo has always been about immersing players in a different world through its campaign, and striving to improve and learn through its multiplayer. To see the Halo approach to gaming still standing strong after over a decade, against modern titles, attests to just how well-designed and innovative the series is, and the Master Chief Collection will be something that continues to give its players enjoyment long after Halo 4 releases and finishes off the collection, keeping people engaged and excited as 343 Industries works toward releasing Halo Infinite.

Feedback and Reflections on Insider Flighting with The Master Chief Collection: Halo 3

“I would prefer even to fail with honour than to win by cheating.” –Sophocles

I had previously received an invitation to test Halo: Combat Evolved earlier in February, but an account issue prevented me from logging in and participating. This time around, 343 Industries has begun testing Halo 3 ahead of its release into The Master Chief Collection, releasing just over half of the single-player campaign missions and rotating multiplayer game types during its run. I was provided with an invitation to participate in the flighting programme and hastened to experience both the single-player and multiplayer aspects of the game before the test period ended. The Halo 3 flight offered five of the nine campaign missions: out of the gates, I was impressed with the visuals and handling. I will be returning once the game is finished to deal with the story and my impressions of gameplay – this time around, I will be focused more on the technical aspects of the game as a result of the flighting. Out of the gates, there are no major performance issues that are immediately apparent: the game handles smoothly, with no frame drops or any stuttering even in busier areas. The only major issue affecting the campaign is the weapon audio: the report of a weapon is barely audible over the music and ambient sounds during a firefight. However, while Halo 3 appears ready from the campaign perspective, the multiplayer component is stymied by a major problem with the mouse sensitivity to the point of being unplayable: in close quarters engagements, I favour having higher sensitivities to ensure I can continue tracking my targets, and I typically position myself in such a way so that I can favour closer-range engagements in Halo. At present, the maximum available sensitivity in Halo 3 is far too low to be effective in the multiplayer, and this is something that needs to be improved prior to the full release of Halo 3.

The reason why the sensitivity settings are too low in Halo 3 for the gameplay is related to the presence of both mouse-and-keyboard and controller players: in The Master Chief Collection, players who use a controller are given an aim assist utility that is intended to help them keep up with mouse-and-keyboard players by automatically shifting the camera to be centred on an enemy. In practise, this has allowed players using controllers to have an immense advantage over those who use mouse-and-keyboard in close quarters scenarios: since the time-to-kill in Halo is high, being effective means consistently landing shots on an enemy. Players must track their targets and time each pull of the trigger: on a mouse-and-keyboard setup, how well players can pull this off boils down to a matter of skill, and an experienced player can be quite effective with the mouse-and-keyboard in all scenarios. However, controller players have aim assist which handles this tracking; the player only needs to pull the trigger, and aim assist ensures their shots will land. This leaves mouse-and-keyboard players at a massive disadvantage in close-quarters firefights – the inevitable result is that during the Halo 3 flighting, I’ve been unable to see any sort of success in a given multiplayer match against players using controllers. Because of low sensitivities, I’ve experienced a reduced ability in being able to reliably track targets: players move faster than I can keep my crosshairs on them, and if they have a controller, they are assured that their shots will find their mark. Beyond sensitivity issues, the other gripe I have with the flight is that dual-wielding is similarly unintuitive: whereas Halo 2 was designed so that the left mouse button would fire the left-hand weapon and the right mouse button would fire the right-hand weapon, Halo 3 has this reversed, and there is no easy way to change this. Similarly, having separate reload buttons means that it is hardly practical to dual-wield, and for most of the campaign, I simply eschewed dual-wielding in favour of running the battle rifle.

Screenshots and Commentary

  • My performance in Halo 3‘s flight was worse than what it was during the old days of LAN parties when my friends switched us over to Halo 3 from Halo 2: back in those days, I was lucky to get 5-10 kills a match, but most games during the flighting, I found myself unable to even hit five. Halo 3‘s gameplay is slower than that of Halo 2‘s, and almost all of the weapons are weaker than their predecessors. As a result, it was quite difficult to get used to the new way things handled.

  • Owing to the weaker weapons and the fact that I simply wasn’t able to aim and track as quickly as I’d like, triple kills did not happen during my time with the flight. I do, however, have a pile of double kill medals for my trouble, and admittedly, while the experience in the flight was decidedly negative, I did have a few moments here and there in the multiplayer. My friends have long felt that Halo 2 was the superior game when it comes to multiplayer, featuring superior weapon balance and mechanics that were more skilled based.

  • While the multiplayer portion of the flight was not quite as smooth as I would have liked, I had absolutely no trouble at all with the campaign: the Halo 3 flight made five of the nine campaign missions available, giving a good spread of what was available. Overall, I have no complaints about the campaign at all. I was originally considering splitting this post to cover both the campaign and multiplayer, but it’d be tricky to do that without the full story on the table. As such, I will be doing a full discussion of the campaign once Halo 3 is launched.

  • Heretic is Halo 3‘s remake of Midship, one of the best close quarters maps in the game for MLG slayer. I’m generally not fond of FFA-style games, since there’s too much opportunity to be vultured after a firefight, but the flipside is that a skillful player has more opportunity to chain impressive multi-kills together in FFA than they would in MLG Team BRs. In the days of old, I struggled to get kills with the battle rifle and instead, most of my kills came from melee or grenade sticks.

  • One aspect I did enjoy in Halo 3 was the addition of the gravity hammer: this Brute weapon is a weaker incarnation of the gravity hammer that Tataurus yields in Halo 2, and with a powerful shockwave projector, can flatten enemies or even deflect projectiles. Having confiscated a gravity hammer from another player on Guardian, I ended up going on a short killing spree with it and earned myself a double kill for my troubles. Guardian is the Halo 3 equivalent of Lockout in terms of design, but no Halo map is as enjoyable as Lockout: an update would later add Blackout, a map that has the same layout, to Halo 3.

  • The other fun aspect of Halo 3 is the inclusion of the Spartan Laser: while I’ve now fired one properly on PC in both the Halo: Reach and Halo 3 flight campaigns, the flight represents the first time I’ve been able to pick up the weapon in multiplayer and get kills with it. It is with the power weapons where players can witness the more sophisticated physics engine of Halo 3 at work. Explosions can result in unusual things materialising, lending itself to comedy in some moments, such as when one accidentally kills themselves with a traffic cone thrown by an explosion.

  • The larger maps in Halo 3, coupled with the fact that the battle rifle is no longer as effective as it was in Halo 2, means that firefights are protracted and drawn-out. At medium ranges, the battle rifle stops being effective. As it turns out, Halo has a mechanic called “bullet magnetism”, which refers to the tolerance a bullet can be from a target and still count as a hit. Halo indicates that a player’s shots will register when the reticule is red, bullet magnetism is in play, and one’s shots are guaranteed to curve towards an opponent.

  • Outpost is probably my favourite of the Halo 3 maps from an aesthetics perspective: the combination of bases on the edges of the map, open areas in the map centre, and massive radio dishes in the background, set under the light of a day coming to an end, creates a very unique and interesting atmosphere. It is on larger maps where the battle rifle feels inadequate in Halo 3, and firefights that would’ve been very manageable in Halo 2 turned into a situation where I would dump an entire magazine at a foe, only for them to kill me instantly.

  • The aim assist aspect of The Master Chief Collection is the subject of no small debate since the launch of Halo: Reach, with some players feeling that aim assist outright ruins the game for mouse-and-keyboard players, and others believing it to be a necessary part of the game for players who run with controllers. I lean more in favour of the former: in excess, aim assist takes the skill out of Halo, and a degraded experience for mouse-and-keyboard players is bad for a game that was ostensibly supposed to bring the Halo universe into the realm of mice and keyboards.

  • As it stands, I consider defenders of strong controller aim assist to be players who want to do well at all costs. Such players fear their advantage might be taken away by any changes to aim assist, and vehemently defend aim assist under the impression that a good enough player should be able to overcome them, irrespective of input scheme. Here on Last Resort, Halo 3‘s interpretation of Zanzibar, I managed to go on a short streak with the sniper rifle. Unlike the Halo 2 sniper rifle, which yields sniper medals for every successful kill, Halo 3‘s sniper rifle only awards medals on a headshot kill.

  • The sniper rifle is even more valuable in Halo 3 owing to the fact that it can reach targets that the battle rifle cannot touch: while my team focused on closing the distance to secure the flag, I hung back with the sniper rifle and picked off stragglers to stop them from firing on teammates. The sniper rifle remains fun to use, but the old firing sound is a little weaker compared to the Halo 2 Anniversary incarnations of the rifle. The UNSC sniper rifles of Halo fire 14.5 mm rounds, which are larger in bore than 50-cal rounds, but as the rifles fire APFSDS rounds, their recoil is far lighter than that of a rifle firing BMG rounds, allowing even the marines in Halo to fire the weapon from the shoulder.

  • Infection is one of the more unusual game modes, officially introduced into Halo 3 after the Halo 2 custom game mode became popular. The inclusion of these novel modes mixes things up a little, although having spent the better part of the past seven years in Battlefield, where games are objective-oriented and set on large maps, upon returning to Halo, I find myself gravitating back towards the smaller-scale eight player matches more frequently, since these represent drop-in, drop-out sessions that fits my schedule particularly well.

  • During one match, I saw for myself the impact of a controller could have on performance: one of the players on my team began racking up kills at a rate that seemed impossible: we had ended up on a larger map, and there were numerous firefights where I had landed a few rounds on an opponent before this player appeared, snapped onto them and scored the kill. Players who’ve used both mouse-and-keyboard and controller setups state the latter gives an unfair advantage: during my time in the multiplayer, I watched as players snapped onto other players and landed shots with flawless accuracy. This performance is a result of controller aim assist helping them, rather than purely through legitimate skill – keyboard and mouse players do not get aim-assist.

  • This is what lends itself to my page quote: I don’t have fun when I lose unfairly, but I have even less fun when my team wins through the action of players who play dishonourably. Whereas gaming from an older age emphasised improving by having fun (i.e. “the more fun you have, the more you are encouraged to improve, so you can have more fun”), these days, gamers seem fixated on creating meme-worthy moments even if it comes at the expense of integrity, For these people, they believe that if they can make my meme and get upvotes for it, underhanded tactics are acceptable to use.

  • In the old days of Halo 2 Vista, I remember the thrill of improving enough in multiplayer to earn multi-kills and go on kill-streaks on virtue of skill alone: using a controller to gain an advantage over mouse-and-keyboard users, however slight the edge is, is still to be playing dishonestly, and consequently, while I do have an Xbox controller floating around, I am not going to resort to using it just to have fun in a game. As it stands, the Halo 3 flight is still quite buggy, and one of the known issues in the game was poor hit detection, which could further have exacerbated the situation.

  • 343 have acknowledged that hit detection is an issue owing how game steps on PC handles differently than on the Xbox because of to frame rate differences: in conjunction with the poor sensitivity, this is likely why my experience in the Halo 3 flight was particularly poor. The hit detection is a known issue in Halo 3‘s flight, and 343 is likely going to work on getting this one ironed out. However, the mouse sensitivity doesn’t appear to be something on their radar.

  • Another issue I’ve experienced since Halo 2 was the fact my text chat no longer seems to be working. This isn’t an issue in multiplayer, but in co-op, I use it to coordinate with friends who don’t use voice chat. I’ve had several occasions where I needed to pause and step aside for something, but because text chat wasn’t working, they proceeded ahead and entered a firefight short-handed. I’m not sure if 343 will address this issue, but in the flight for Halo 3, I tested the chat out and my messages did not seem to be getting through in the multiplayer, suggesting that it may be similarly broken if I create a lobby and co-op with friends.

  • One thing that was extremely frustrating in Halo 3 was the fact that vehicular handling is worse than it was in any Halo game I played thus far: vehicles bounce and flip on the slightest provocation, and there were a handful of matches where, had I not flipped over or slowed down as a result of the game’s implementation of vehicle physics, I might have actually ended up with a triple kill or overkill.

  • My performance in the Halo 3 flight was so poor that I wondered if I had lost my touch with FPS in general, and so, a day before the flight was set to end, I returned to Battlefield V to see if my skills had been lost. In back-to-back matches of conquest, I went 21-14 and 21-13, respectively. When I spun up a match in Halo 2, I performed as I normally would. This tells me that, rather than my skills being an issue, the poor showing I had was a result of issues in the game and a lack of familiarity with the inconsistent mechanics.

  • With a rough flighting experience, I am glad that things at least ended on a decent note: I won my last match and here, scored a kill on the enemy team’s MVP, ending a spree of theirs in the process. The flight ended two days ago, and I’ve already submitted my feedback for the team’s consideration. I hope that 343 will address the issues and make Halo 3‘s entry a success: I am fully confident that the campaign will be amazing, and I may play a match or two of the multiplayer to see if it is in a state that I am able to have fun in. With this post, we now enter July, and today is Canada Day. Traditionally, it’s a day to go out into the mountains, but owing to the global health crisis, and the fact that Canada Day is in the middle of the week, I will instead spend the day relaxing in a different way, before celebrating Canada Day properly by watching a virtual fireworks presentation.

Consequently, mouse sensitivity is the most critical fix that needs to be applied to Halo 3 at present: increasing the maximum sensitivity by around 50-80 percent will ensure that mouse-and-keyboard players have a fighting chance in close-quarters battles. If a player are given the means track their opponents at least as quickly as they move, then in a firefight, the outcome becomes dependent on skill, rather than the input method. The presence of aim assist is a contentious one in the community, and I’ve felt that a simple implementation of a much higher mouse sensitivity ceiling would level things out considerably. Overall, Halo 3‘s flight shows that once a few critical fixes are made, the game is ready to roll out into the release phase, which currently is anticipated to be mid to late July. I am particularly enthusiastic to go through the campaign: the missions were built with co-op play in mind, and with no critical performance issues whatsoever, the campaign looks like it is ready to be launched, allowing me to finish the fight and wrap up the original trilogy in Halo. Similarly, the core aspects of multiplayer are working in a satisfactory manner, and I’ve not encountered any serious issues like being disconnected from a match, or clipping through geometries in the maps at all during my run of things. If the issue of sensitivity can be adequately addressed, the multiplayer could be an engaging component of Halo 3, as well: as it was during the flight, the multiplayer was unenjoyable and frustrating to play, not for any reason beyond the fact that I’m not able to track my opponents at a speed that I am comfortable with. Beyond this, the other issues I’ve found are more of a matter of acclimatisation, and even if unaltered, I could learn to adjust to the new schemes over time.