Recommended System Requirements:

Operating System: Windows Vista (SP2), Windows 7.
Processor: QuadCore 2.0Ghz.
Memory: 2GB RAM+.
Video Card: A video card with 512MB of VRAM and one of the following chipsets: NVIDIA GeForce GTX260; ATI Raedeon 4870.
HDD Space: 2GB.
Soundcard: Soundcard with DirectX 10 compatibility.
DirectX: DirectX 10.
Disc Drive: 16X CD/DVD Drive.

Objective Raid

Zh1nt0 and you folks have asked about it, so here's a piece on the modtools situation for BC2 PC.

Frostbite 1.5 consists of these components:

• The game runtime
• The editor runtime
• The content processing runtime (aka "the pipeline")
• and some plugins for Maya

The game runtime is distributed outside of EA, but the editor + pipeline + Maya plugins are not.

So let's take a look at some things that would need to be solved before we'd be ready to distribute the editor + pipeline.

Pipeline operation

Let's say that you tell the pipeline to build level MP_003.

MP_003 is represented by an XML file, which references a bunch of other files. These in turn reference other files. If you follow this graph of references,
you will find the level layout, heightmap, characters, weapons, vehicles, and all the content that you can see in-game.
(The in-game HUD and related stuff might also be in the graph.)

When the pipeline is about to build MP_003, it will first perform a consistency check on all content, and yell if any file that is referenced by any other is not present.

If all files are present, the pipeline will attempt to convert all files referenced by MP_003. It uses the file system journal to determine which files have changed on-disk.
Also, and any files that have already been converted have info on which files depend on it (so it has info like: "if file X changes, then files Y,Z,W will also need to be rebuilt").

Building all content for BC2 from scratch takes something like 48-72 hours on a normal workstation.
Half that time is spent building common content (such as character animations), half builds level-specific content.

In addition, there's a caching mechanism: if the pipeline wants to build a specific bit of content,
it will first check if the pre-built content is already available on a cache server and take the result directly from the cache server instead.
The pipeline can also populate the cache if it builds something new.


Pipeline issues

So how does this work in practice? It's not ideal, but it's good enough for us to ship games on it.

The pipeline is a bit overzealous with regards to rebuilding assets - sometimes it rebuilds stuff that it shouldn't need to.

The pipeline will normally crash about 2-3 times during a full rebuild.

You need to have Maya 8.5 (32-bit version) installed in order to convert any meshes.

Any content in the cache expires after 3 weeks. After 3 weeks have passed, that content will need to be rebuilt and re-uploaded by a machine running the pipeline.
The effect that this has on day-to-day development is minimized by having one or two machines dedicated to running the pipeline every time any content change is done.
By running the pipeline, those machines will populate the cache, thereby speeding up the build process for everyone else. (The output form those content build steps is discarded.)

In short: the pipeline + cache setup works better the more people are using it simultaneously.

If there are content errors, you need to know a lot about the internals of the game engine to figure out what's wrong.

Finally, in its current form, the pipeline + editor expects some specific IT infrastructure in place (most notably the cache server and a Perforce server).
If it's not there then the pipeline + editor will behave strangely.
The first time I tried, it took me about one week to get the full editor + pipeline setup to work properly outside of the DICE office.
And that was when I had the option to call any of the other developers to ask for help.

... does this sound bad to you?

Truth be told, this is approximately where the industry average is at for game studios' internal game engines.
One of FB 1.5's weaknesses is specifically that its content processing is flaky, and the flakiness gets more problematic as the amount of content goes up.
FB 2.0 is much improved in this regard, but FB 1.5 is what we're using for BC2 and that's what relevant in the current discussion (or monologue if you prefer).

Content

Both the pipeline and the editor takes in all content in its raw, original form. Anyone who is to build any content needs the full 80GB of raw data on their machine.
We are not comfortable giving out all our animations, meshes etc in raw form.

We are comfortable giving out the processed data - after all, that's what on the game disc - but that data does not plug into the editor/pipeline at all.

Licenses

The game, editor and pipeline all use commercial middleware. It is developed by Havok and several other companies.

The licensing agreement for the middleware allows us to use that code in specific products, on specific platforms.
If we want to release editor + pipeline, we need to license the middleware specifically for this. How much would that be? Perhaps $1M-$3M. I'm guessing wildly here.

Stripping out that middleware would seriously hamper the functionality especially of the pipeline. We use Havok Physics, for instance.
Without Havok Physics, the pipeline wouldn't be able to convert any of the physics meshes. We also use Granny.
Without Granny, the pipeline will not be able to convert any of the character animations. Etc.

Re-implementing the necessary functionality of the middleware ourselves ("let's make our own physics engine / let's plug in an open-source physics engine")
would take literally man-years. Licensing is cheaper in pure $ cost and faster (it works now instead of by 2012).

The pipeline also uses some code that is under GPL. Given that we do not want to release the full source code for the editor + pipeline,
we would need to replace the GPLed code with other implementations.

The GPLed code is less of a problem than the proprietary middleware.

Editor

The editor itself is reasonably stable and well-behaving.
It is far from obvious how to set up the game logic for a level,
but that is easily covered by releasing some example levels which contain the logic setup for the common gamemodes.

Test-running levels

First the level needs to be successfully processed by the pipeline. Then you'd want to be able to test it locally.
That involves having a listen server around. We don't have a listen server neatly packaged. There's probably a piracy angle here too but I'm not going to discuss that.

Distribution of levels

Getting levels onto the RSPs server machines would likely not be any problem.
However there's need for checksumming levels, so that game clients can know whether or not they have the correct version of level X on their machines.
There's a whole bunch of other things (mainly UI-related) which will need cleaning up as well. Not difficult to do, just takes time and I'm listing it for the sake of completeness.

Also, there are some complications wrt when we release patches that affect the base game's content.
Whenever we release a patch, all existing levels will need to be rebuilt with a new set of original data.
This is because some level-common data is stored inside of the level archives.
I'm not sure at the time of writing,
but that probably means that the only manageable way for us would be to invalidate any user-made levels when we release a patch of that form.
Then creators of any user-generated levels would be required to run their levels again through the pipeline with the new base content supplied.


So how about just a map editor?

If it doesn't plug into the ecosystem above, then getting it to work involves some serious wrangling.
Either it is a light-weight replacement for our existing editor - in which case all the challenges with the pipeline still remain - or it is a separate mode (think Forge for Halo). Developing an extra mod-layer that is sandwiched into the game would easily take 6-12 months.

Synergy effects between FB 1.5 and FB 2.0

So let's say that we would go through the procedure of making mod tools for FB 1.5. How much of that work would be reusable for FB 2.0?
I don't have any firm figures, but the differences between FB 1.5 and FB 2.0 are pretty large by now.
Given this and the fact that a fair bit of the FB 1.5-specific problems (where the devil often is in the details) don't apply to FB 2.0,
I'd guess that less than half of the work would port over to FB 2.0.

Conclusion

In conclusion, my recommendation to the rest of DICE is not to develop mod tools for BC2 PC. There are too many hurdles to overcome.
That energy is better spent elsewhere, be that on BC2 or other titles.

- Kalms

• 24 players max.
• Trusted GSPs, at least more then one, maybe same list as BC2.
• Admin controls, server and client will be available to some devs.

Medal of Honor is quickly approaching it's release on October 12th and it's time to talk about multiplayer PC servers!
Medal of Honor will operate on dedicated servers, and while the executable will not be released publically,
servers will be available for rent through the following selected game server providers:

- 4NetPlayers
- Art of War Central
- BrainStorm Network
- Branzone Inc.
- Clan-Server.at
- Computer Games Online
- Diabolic Servers
- Dovermed
- Eliott Ness
- Fragnetics
- ForTeam.ru
- GameHosting.co.uk
- Gameservers.com
- Hosters.at
- Hypegamez
- Hypernia
- i3D
- iGame
- InnovaSoft
- KillerCreation
- LeetServers
- Low Ping Game Servers
- Mammoth
- MecaHost
- Multigamer.no
- Multiplay
- MyInternetServices
- Newlight Systems
- Nuclearfallout
- On3 Network
- Primary Target
- Rackage
- SAIX Games Service
- SwissQuake.ch
- Web Africa
- XFactorServers

Anyone who rents a server will be able to control it through the game server provider's admin panel along with the game server's remote administration interface.
The remote administration interface is a very simple command console, which will be included with the server's documentation.
However, with that being said, it would be much easier to use one of the graphical clients that are developed by various independent tool developers.

We have offered the following developers pre-release access to the game client and server, in hope that their tools will be ready in time for the game's launch:

- MOHCC (by the creators of BC2CC)
- ProCon
- Big Brother Bot (B3)
- Other tool developers are welcome to join in as soon as the game has launched.

Now on to ranked and unranked modes. When the server runs in ranked mode, any score and awards that a player collects is reported to the master servers.
The server administrator is required to abide by the "Rules of Engagement," so you and everyone else can enjoy an entertaining online experience.
In unranked mode, no player progression is reported to the master servers. However, the server administrator has more control and can apply arbitrary game rules.
All game modes support a maximum of 24 players.

Medal of Honor also supports PunkBuster. It is up to each server administrator to enable this option on his or her server.
However, if the server is ranked, then PunkBuster is mandatory.
We have sent out pre-release game builds to the following organizations to ensure compatibility with streaming services before launch:

- PBBans
- GGC-Stream
- PunksBusted

There is also an option to to reserve dedicated server slots on the game server. Each reserve slot will replace a normal spectate slot.
Spectators will be allowed to free-flight around the map, however there is no 1st/3rd person spectate option as well as no demo recording feature.

"Here at EA, we want to make sure our fans know that we're listening.
That's why we we've created The MOH Experience, a series of uncut, unedited single player and multiplayer videos we've put together
to show our audience what they can expect when Medal of Honor launches on October 12th."

Here at EA, we want to make sure our fans know that we’re listening. That’s why we we’ve created The MOH Experience, a series of uncut, unedited single player and multiplayer videos we’ve put together to show our audience what they can expect when Medal of Honor launches on October 12.

In our first installment dubbed “Fallen Angel,” you can see what’s in store for the multiplayer mode of Medal of Honor. The beta we hosted a few weeks back was in fact a beta, a work in progress, and your feedback is helping us make the best game possible. Need proof? Check out The MOH Experience Part 1: Fallen Angel below.

While this is good news for MoH...how about a bit o'bad? Looks like U.S. government PX's will not be allowed to sell MoH:Tier 1.
Chalk this ban up to to the fact that there's just too many damned Taliban in the game.
Apparently it's too soon to shoot e-Taliban, especially since the real thing are still putting up a fight. Read more here.

• 42 gametypes
• A "war server".
• A "Help Mode", which is in essence a realism version of the famous Freeze-Tag mode.
• Hardcore gameplay with realistic damage, blood, gore, some physics and of course war effects that will make you feel really inside a real war.
• It comes with "Intelligent Server" which admins the server for you 24/7 without the need of human interaction.
• HER (Hajas Enhanced Realism) with realistic Blood, Gore, Pain, Damage & Physics effects
• Over 2400 Weapons Modes with 16 pre-defined modes
• Airborne support in many gametypes let you be a paratrooper falling from the sky
• 4 Different Support Strikes (Tactical Airstrike/Heavy Bombing Strike/Artillery Strike/Mortar Strike)
• Intelligent Anti-Camping System coded to each gametype
• Frontlines Weapons, brand new balance and behavior!
• Medic System with a Medic Perk to let you save your wounded teamates
• Full Rank System with Custom Classes + Create-A-Class INGAME
• Frontlines Duel, where the remaining two people in a round will duke it out with knives.

Medal of Honor™ MP Beta requires at least the following minimum configuration:

• Operating System: Windows XP (SP3), Windows Vista (SP2), Windows 7
• Processor: Intel Core 2 DUO @ 1.4 GHz/AMD Athlon64 X2 @ 1.8 GHz
• Memory: 1 GB
• Video Memory: Video card must be 256MB or more and contain these chipsets or better: NVIDIA GeForce 7800 GT ; ATI X1900. Laptop versions of these chipsets may work but are not supported. Updates to your video and sound card drivers may be required.
• HDD Space: 3GB
• Sound Card: Soundcard with DirectX 9.0c compatibility
• DirectX: DirectX 9.0c

The making of our “Leave A Message” trailer started with a simple concept and a very straightforward execution.

Everyone involved in creating the trailer was in complete agreement from the very beginning. We had three simple goals. We wanted to be authentic, we wanted to be respectful, and most of all, we wanted to give a special nod to Steven Spielberg, who created the Medal of Honor franchise over a decade ago.

The best way we knew how to do this, was to recreate the Omaha Beach landing with Jimmy Patterson. Except now, instead of arriving on the shores of occupied France in the hull of a Higgins boat, our Ranger would arrive in the Shahi-Kot Valley, in Afghanistan’s Paktia province, in the modern day equivalent, the CH-47 Chinook helicopter. Basically, Normandy in the desert.

Since the entire piece is taken directly from the opening of the first Ranger mission in our game, creating the first pass of our trailer was quick and easy. We simply slowed the animation down and removed a few scenes that didn’t fit within the message. The entire untouched scene at regular speed remains in the final product.

There is a wonderful gag in the middle of the scene where one of the Rangers actually begins to realize that things seem very familiar to him. When it finally dawns on him that he is basically reliving the D-Day landing from “Saving Private Ryan” he quickly notices that he is sitting closest to the loading ramp at the rear of the fuselage. He then taps one of his teammates on the shoulder and says, “Hey, I’ve seen this movie, you sit here!” and then trades places with the young Ranger.

The actual phone message Jim leaves for his family back home changed after we showed it to one of our military consultants. When he first heard the message, he offered up a dose of reality. He explained to us that when you are deployed and in harm’s way, you tell your loved ones whatever they need to hear to keep them from worrying. Even when you are moments away from stepping outside the wire to conduct a raid or begin a major offensive, you never disclose anything. You assure them that you are fine and that you will be fine, knowing it will help them sleep at night. We let this information settle in for a few hours and then we rewrote the dialog to what you hear now.

After the trailer was completed we showed it to a select group of individuals to get their reaction. We showed it to the wife of a Marine who had recently returned home. We showed it to our significant others and our families. We then showed it to senior officials within the U.S. Army. It was late one afternoon and our liaison, Lieutenant Colonel Greg Bishop, had brought a colleague of his from the U.S Army Public Affairs Office to meet with us, see our game and get a tour of our facility. We stopped by the theater and I surprised them with a private viewing of the trailer. At the end of the piece, the room was silent. He then stood, pointed at the screen and said very matter-of-factly, “That right there gentleman is the reason we are working with this team, and why the U.S. Army will continue to support Medal of Honor.”

Needless to say, it was a very rewarding day.

"After almost 6 years at Infinity Ward, I resigned today. I'm incredibly proud of everything we accomplished and I'm going to miss everyone."

IWSlothy Twitter