Search Unity

Inside Look: Best Practices for Moving from Internal Game Engine Technology

, 7月 31, 2015

Game developer studios of all sizes are making the move from using or supplementing in-house technology to adopting an external engine like Unity. Unity’s newest whitepaper, “A Guide to Moving From Internal Game Engine Technology,” takes an in-depth look into this growing trend, and shares real-world perspectives from some of the most successful game developers on why they switched to Unity, and how studios can do it right.

You can access the full report HERE, but below is a quick snapshot of what the whitepaper is all about:

Inside this report

In this new whitepaper, we’ll consider why many studios are finding success in moving from custom technology to an external engine.

Unity invited developers from some of the world’s most respected and experienced studios to share their insights on what motivated their teams to look beyond established in-house tech, how they best adopted a new engine, and what the advantages and challenges have been.

While using Unity to develop some of the most successful and exciting games on the market, such as Assassin’s Creed Identity, The Bridge, Grow Home, Plague Inc., Hitman GO and Total War Battles: SHOGUN, some of these studios have turned their backs on custom tech completely, while others are using an external engine on select projects. What unites each, though, is the success they’ve met in embracing an external engine – specifically Unity.

Grow Home_Unity Whitepaper_Blog_Body Image

What you should get from this report

By the end of the report, you should have an informed understanding of whether it is the right time to move away from your custom technology and embrace an external engine to use alone – or to use alongside your existing solutions. In short, this whitepaper will:

  • Explore the reality of potential improvements to efficiency, return on investment, and creativity.
  • Look at the impact moving beyond custom can have on your existing team, and how it can help bring in the best talent from a broader pool of skilled developers.
  • Share the experience of how the process worked for studios looking to extend and support console and PC IP, or prototype new ideas so as to expand their remit and relevance to stay at the industry’s cutting edge.
  • Provide an overview of the process of integrating a new engine into a studio pipeline and workflow, and gain an understanding of the relative ease of the porting and adoption process.

If you’re curious as to whether or not your custom technology is enough on its own, then this report is for you. We present a potential new route for your team, your technology, your games and your business. Moving beyond custom may help you enjoy the success of the various contributors, who between them have created truly distinct and brilliant titles – all of which were made with Unity by a studio previously committed at various levels to its custom technology.

The Bridge_Unity Whitepaper_Blog_Body Image

30 replies on “Inside Look: Best Practices for Moving from Internal Game Engine Technology”

Well done boys. A simple PDF download doesn’t work. Corrupted, can’t open, even outside the browser.

Thanks for helping each other find workarounds. The Unity community is truly the crème de la crème! We are still working on the solution — anyone in North America can think of falling asleep tonight as like time travel to this being resolved :)

Well, that’s weird.

It won’t open on Chrome, nor Adobe Reader, nor IE, but it opens inside Mozilla Firefox… Maybe I should go back to the foxy, haha. Anyway. It’s a workaround for those who wants to read it so badly (as I am).

Hope it get fixed. (:

It Didn’t work for me on chrome or Firefox both the latest version and adobe have been updated also.

I’ve downloaded the PDF, but it doesn’t open. Adobe Reader says file is not supported or damaged…

Hi everyone,

For some it’s working and for some it’s not. For those of you having trouble can you let us know what browser you’re using, what tool you’re using to try to automatically open it and/or any error message? It seems to be working for those who’ve updated to the latest version of Adobe Reader and it also works to open in Mac’s Preview. Thanks for the feedback.

@Hadrien, don’t go! Give us a chance to make it right! :)

Corrupted / won’t load for me also:
Chrome 44.0.2403.125,
Won’t load in Chrome, Foxit or Adobe

Saved file opens in Firefox 39.0 with warning ‘This PDF document might not be displayed correctly’ but does not open in Adobe Reader 11.0.12 ‘File has been damaged’. As the document was created on a Macintosh suggest you check that it opens in Windows too.

It only opens in Firefox here. Chrome and the last version of Adobe Reader won’t open it. IE says “file does not begin with ‘%PDF”, and Edge haven’t yet heard of the PDF format apparently.

Anyway, Firefox does the trick so it’s not corrupted after all, just a little bit tricky to open :)

Same here… I’m moving to Unreal!
No, just kidding. ^^ Hope it gets fixed soon,

I thought it’s corrupt too, but it’s not. Try to open this with Mozilla Firefox, for instance.

Hi! already downloaded three times, looks corrupt the paper, just me or someone else? Greetings!

Comments are closed.