My Message close
GAME JOBS
Latest Blogs
spacer View All     Post     RSS spacer
 
May 22, 2013
 
Using Small Studios As Stepping Stones In Your Career [2]
 
Combat Analysis: Guacamelee
 
Kickstarter Fu
 
Why every developer should play Aliens: Colonial Marines
 
Coding "To The Metal" is a dangerous ideal. [2]
spacer
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
May 22, 2013
 
2K Games
Graphics Programmer - 2K Games
 
2K Games
Engine Programmer - 2K Games
 
2K Games
Tools Programmer - 2K Games
 
GREE International
Senior Product Manager, Growth and Revenue
 
GREE International
Business Intelligence Data Analyst
 
Synergy Blue
3D Artist / Animator
spacer
Latest Press Releases
spacer View All     RSS spacer
 
May 22, 2013
 
Stardock’s
Turn-based Fantasy
Strategy PC...
 
indiePub’s trifecta
of deals
 
Indie Narrative /
Strategy Game 7 Grand
Steps Will...
 
Undead Hunt available now
for Android
 
And now another message
from our good friend...
spacer
About
spacer Editor-In-Chief:
Kris Graft
Blog Director:
Christian Nutt
Senior Contributing Editor:
Brandon Sheffield
News Editors:
Mike Rose, Kris Ligman
Editors-At-Large:
Leigh Alexander, Chris Morris
Advertising:
Jennifer Sulik
Recruitment:
Gina Gross
Education:
Gillian Crowley
 
Contact Gamasutra
 
Report a Problem
 
Submit News
 
Comment Guidelines
Sponsor

 
Next  Mass Effect  ditches Unreal for EA's internal Frostbite engine
Next Mass Effect ditches Unreal for EA's internal Frostbite engine
 

November 12, 2012   |   By Eric Caoili

Comments 10 comments

More: Console/PC, Business/Marketing





Frostbite is fast-becoming the standard engine for most of Electronic Arts' new titles -- BioWare has chosen the engine for its next Mass Effect release, as well as a new lead developer.

Developed by EA DICE, the 2.0 version of the tool has become the engine of choice for many of EA's internal studios. EA DICE's Battlefield 3 and 4, Visceral Games' Army of Two: The Devil's Cartel, Danger Close Games' Medal of Honor: Warfighter, EA Black Box's Need for Speed: The Run, and several other games all use Frostbite 2.0.

BioWare has already been working with Frostbite 2.0, using it as a base for a new RPG engine that's powering next year's Dragon Age III: Inquisition. The next Mass Effect also uses Frostbite 2.0 as a foundation, and will use many of the systems the Dragon Age III team has built.

The previous Mass Effect releases were developed on Epic Games' Unreal Engine 3, while the Dragon Age games were created with BioWare's internal Eclipse/Lycium engine.

EA has said before that it doesn't force its studios to use internally built tech, but there are advantages those teams can benefit from when using Frostbite 2.0 over competing engines, such as their access to support and the ability to work with the Frostbite team to accomplish what they want with the tool.

"We want to transfer resources between studios, and if they have the same knowledge on the tech base, it's going to be a hell of lot easier for us to do that efficiently, and for them to get help or for them to give help," EA Games' Patrick Soderlund told Gamasutra several months ago.

BioWare has also revealed that its Montreal office will serve as the lead team on this next project instead of the Edmonton branch, which has handled the games in the past. The Montreal team has previously contributed to the series cinematics, multiplayer content, and downloadable content.

"While [the next Mass Effect] will be very respectful of the heritage built over the course of the first three games," says BioWare Montreal studio director Yanick Roy, "with the original trilogy now concluded and the switch over to a new engine, we are exploring new directions, both on the gameplay and story fronts."

Over the years, BioWare Montreal has taken on increased responsibilities for the Mass Effect franchise, and has grown its core team slowly to reflect that, bringing in many transfers from the Edmonton arm. The studio intends to now grow its staff at an accelerated pace.

Mass Effect executive producer Casey Hudson will continue his role on the series, and will have a project director working under him at Montreal. BioWare Edmonton will also help with the transition by supporting the Montreal team throughout the project's development.
 
 
Top Stories

image
Xbox One is Microsoft's biggest play for living room domination
image
Opinion: Xbox One is a desperate prayer to stop time
image
Indies on Xbone: Where's the beef?
image
'If you're backwards compatible, you're really backwards.'


   
 
Comments

WILLIAM TAYLOR
profile image
I don't know whether that's good, bad, or neutral, but it sounds like a plan.

Joe McGinn
profile image
Change game engine and move to the B team at the same time??? I suppose "plan" is one way to describe it.

Michael Rooney
profile image
I'm glad they are at least realizing their size justifies making easily reusable tech rather than most of the EA teams remaking similar systems.

I think it's a good thing even if it initially resulting in lesser results.

Ron Dippold
profile image
So, since this is EA, and they've moved a bunch of people from Edmonton to Montreal, is this prep for shuttering Bioware Edmonton? To be clear, I have not heard of such, but it's a natural question given the circumstances.

Robert Boyd
profile image
It's more likely that the reason for the change is so that Bioware Edmonton can work on a new IP.

Alan Rimkeit
profile image
Shut down Bioware Edmonton? They would have to gripped by madness. Bioware Edmonton is the heart of Bioware. Cut out the heart and they risk the death of Bioware.

I am with Robert Boyd on this. Bioware Edmonton must be working on a new IP. Let's hope so.

Kellam Templeton-Smith
profile image
Nah, more likely trying to grow another major studio, like Ubisoft Toronto.

Christoph C
profile image
I wonder if ME4 is still scheduled (probably) for last generation consoles or if it might be made for the next Xbox/PS so that the FB2 could actually live up to its potential.

With next years reveal of the new Xbox chances are at least good that it will be on that one too.

Kellam Templeton-Smith
profile image
I'm curious to see some next-gen examples of the frostbite engine.

Dragon Age III is well into development using the same engine, but this seems to be just exiting the conceptual phase-I'd love to see how the engine scales.

Zoran Cunningham
profile image
I was asking myself the very same thing. I previously thought that next-gen consoles might use Unreal 4 and Frostbite 3 going forward, so this announcement leaves many of us thirsty for even more details.

I'm also left wondering which DLC content the new team at Montreal worked on throughout the ME series. If it was amazing ME2 DLC like The Lair of the Shadow Broker and Project Overlord, then we're in for a real treat. The ME3 multiplayer is also one of the best console multiplayer experiences in its own right. Sounds like things might be in good hands.


none
 
Comment:
 




 
UBM Tech