Recommended Posts

520155273.png

Developers: 343 Industries
Publisher: Microsoft Studios
Platform: Xbox 360
Release Date: November 6, 2012

Description:

Halo 4 is an upcoming video game and the eighth installment in the Halo franchise being developed for the Xbox 360. Halo 4 is intended to be the first of a new trilogy of Halo series games, named the "Reclaimer Trilogy". Whereas the previous Halo games were developed by Bungie, Halo 4 will be developed by 343 Industries. The game continues some time after the ending of Halo 3, and marks the return of the Master Chief as the main protagonist. Cortana will also appear in the game. The game is set for release in Holiday 2012.


Plot:


Halo 4 marks the return of John-117 - the "Master Chief" - as a playable protagonist for the first time since 2007's Halo 3, as 2009's Halo 3: ODST and 2010's Halo: Reach focused on new characters and playing styles. Having been lost in space in the finale of Halo 3, John-117 and Cortana, adrift aboard the wreckage of the UNSC frigate Forward Unto Dawn, find themselves near a mysterious Forerunner planet, which was first seen at the end of Halo 3 once players beat the game on the highest difficulty setting. A key plot point will involve changes to Cortana and how her exposure to Halo and her operation beyond her natural lifespan may have contribute to her becoming "rampant." Developers revealed in fall 2011 that the game will involve a "shield world," a hollow artificial Dyson sphere type megastructure, possibly being set inside it.

The story of Halo 4 will be focused less on the Halo series' traditional straightforward first person shooter genre, instead relying more on mystery, exploration and discovery. Developers described the game as being grand in scope and scale. Forerunner elements will be featured extensively in the game's environment. Developers also suggested that the game will reveal how humanity and the UNSC have adapted to the galaxy after the end of their war with the Covenant, particularly how they have co-opted Forerunner technology.

Unlike the original trilogy, the story has been designed to be part of a three-game arc from the beginning. In addition, developer 343 Industries is aiming for a more complete connectivity between all of their future media than before, and the Forerunner Saga novel Halo: Primordium, the post-war novel Halo: Glasslands, and the terminals in Halo: Combat Evolved Anniversary, will "definitely" have "resonant connections" to Halo 4's story. Little information has been released regarding the storyline trilogy, but developers have intended that Halo 5 will be a much darker title before the conflict is resolved in Halo 6. [Source]


Links:



Screenshots:


644932257.jpg

471511216.jpg


Videos:


 

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/
Share on other sites

What ever your favourite game is.... :sleep:

We can all make trolling posts.

Except they're right. Halo has always been a :sleep: ever since it first came out(and started ruining shooters) 10 years ago. It only became popular due to the (extreme) ease of play.

As for these pics. It doesn't look like there's really any reason for these to have a whole new thread. As those models look exactly the same as they always have. And chances are any maps will look exactly the same as always when shots of those come out too.

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594704852
Share on other sites

If that really is in-game engine material, that looks pretty awesome for what is a 7 year old console!

Always loved the halo series - so can't wait for this to come out.

ANY console of the current gen can do images that detailed if it's just a single character on screen ;) I'd also like to point out that these aren't Xbox shots at all. They're 1600x900 renders. Regardless of the source, this will never be displayed on the Xbox. The Xbox version will run at a MAX of 720 pixels tall. In fact, my bets are that it will run at less, and be upscaled by the machine.

Plus ... I dunno, these images are just really really boring.

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594704886
Share on other sites

yeah...I don't believe those are in-game

They could be in-game....before it's scaled down for consoles that is.

That's absolutely true. 90% of game graphics are drawn at a very high resolution, before being scaled down (some more, some less than others) for consoles. These super high res textures never get seen by the public, as even the 'high' res textures in console games are actually pretty low res.

Then there's as I pointed out, and no one else has discussed, the sheer resolution of those images. 1600,900. NO console game runs that res. Well, maybe silly little puzzle games. No FPS with any kind of detail does. Most games are rendered by the console out to TV at 720p or less. Either way, they're never putting Halo on the Xbox 360 at 1600 pixels .... I'd bet body parts on that :)

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594704898
Share on other sites

They could well be "in game" look at the detail using the Uncharted 3 engine when being used for "in game" cut-scenes. It's possible that this is what they are from. They don't look so mindblowingly awesome that it seems impossible.

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594704908
Share on other sites

There's a reason it looks much better than what you'd normally see on consoles. And it's a practice that developers have employed since the dawn of games with 3D graphics. They do it because it makes the game look better. Obviously, it won't look that good when you play it on the Xbox 360. If you look at the screenshots of just about any 3D game out there, you'll rarely fine official screenshots that have aliasing. As for the resolution, it was likely scaled down from 1920x1080 and chances are the game will be scaled down even further to make it playable. My guess is 1152x640 (Halo 3/ODST) or 1152x720 (Halo: Reach).

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594705106
Share on other sites

Thats what everyone said about the in game halo 3 screenshots and videos before release as well...

Dude, Halo 3 had some pretty bad bullshots, especially when the real running resolution was found out.

http://www.planetxbo...aign_Screenshot

halo-3-master-chief-shoots-screenshot-big.jpg

chief-campaign.jpg

None of this is anything new, wait for gameplay videos.

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594705118
Share on other sites

I really enjoy the armor redesigns but what I don't understand are why bring the Battle Rifle back and what's up with the mech?

I'm glad 343 is taking the initiative with this game, but I fear they may go too far away from what makes Halo... Halo. This isn't enough gameplay to really say anything about how it plays, but I can say the music isn't what I'd expect from a Halo game.

Link to comment
https://www.neowin.net/forum/topic/1062170-halo-4/#findComment-594705520
Share on other sites

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      592
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!