Introduction
When Chris Murphy took the stage at Unreal Fest 2024, he didn’t start with fancy technical jargon or complicated workflows. Instead, this Senior Technical Artist from Epic Games shared something more valuable – insights from his eight years of supporting and guiding development teams at Epic. His experience with engine transitions and team dynamics proved particularly relevant for studios facing similar challenges.
Murphy’s presentation wasn’t about Unity vs Unreal Engine or features comparison between engines. Instead, he focused on something far more important – the human side of engine migration. Through his work with numerous development teams, he’s discovered that the biggest challenges often aren’t technical at all. They’re about how teams adapt, learn, and work together during major changes.
What makes his approach particularly valuable is the depth of his hands-on experience supporting development teams. Having helped numerous studios through their transition periods, he’s identified common patterns that determine whether teams struggle or succeed. These patterns form a practical roadmap for teams considering the switch to Unreal Engine.
Before diving into common mistakes, if you’re still evaluating whether Unreal Engine is the right choice for your project, check out this Ultimate Game Engine Guide: Choosing the Best for Your Project
Ultimate Game Engine Guide: Choosing the Best for Your Project
Discover the best game engine for your project. Detailed comparison of major game engines, from AAA to indie development.
Mistake #1: Poor Team Communication
The first and perhaps most crucial mistake highlighted hits close to home. Teams often underestimate the importance of sharing their discoveries during the transition to Unreal Engine. Think about it – when someone on your team figures out a clever solution or discovers a helpful feature, that knowledge could save hours or even days of work for others. Yet, many teams lack a proper system for sharing technical discoveries.
I’ve seen this myself in various projects. A developer might spend hours figuring out how to implement a specific feature in Unreal, only to later discover that someone else on the team had already solved the same problem weeks ago. The speaker suggests creating dedicated communication channels for sharing these Unreal Engine learning experiences. This could be as simple as a Slack channel or regular team meetings where people can share their “aha moments.”
The real power of good communication comes from building what Chris calls a “culture of investigation” within the team. When someone discovers a useful project setting or a powerful Blueprint node, sharing that information shouldn’t be an afterthought – it should be part of the regular workflow. This approach not only speeds up the learning process but also helps build a stronger, more knowledgeable team.
Remember, the goal isn’t just to document solutions but to create an environment where team members feel comfortable asking questions and sharing their learning experiences. As the presenter pointed out, even seemingly small discoveries can have a big impact when shared with the entire team.
Mistake #2: Not Embracing Role Evolution
The second major mistake Chris discussed really struck a chord with me. Many teams try to maintain the exact same roles and workflows they had in Unity, missing out on the unique opportunities Unreal Engine offers for professional growth and skill expansion.
In Unreal Engine, traditional role boundaries often become more flexible. For example, designers who previously relied on programmers for every interaction can now create complex gameplay mechanics using Blueprint, Unreal’s visual scripting system. As the presenter explained, this isn’t about replacing programmers – it’s about enabling team members to contribute in new ways.
I’ve experienced this evolution firsthand in my career. As a Technical Artist, I’ve seen how Unreal Engine allows artists to take more control over their work. Animators can implement their own animation blending systems, environment artists can work with procedural tools, and level designers can create complex interactions without always needing programmer support. This kind of role expansion in game development leads to more efficient workflows and more empowered team members.
The evolution of roles during an engine transition mirrors the broader career adaptability needed in game development. For a deeper understanding of how different art roles interact and evolve in game studios, check out this article: Game Artist Career Paths: Your Guide to Success
Game Artist Career Paths: Your Guide to Success
Explore game artist career paths, a variety of specializations, and tips to get a job in game development.
Mistake #3: Ignoring Source Code Access
The third mistake Murphy highlighted is one that often surprises Unity teams – not taking advantage of Unreal Engine’s open source code access. Unlike Unity, Unreal gives developers complete access to the engine’s source code. However, many teams either overlook this powerful feature or feel intimidated by it.
Having access to the source code isn’t just about making engine modifications. It’s about understanding how things work under the hood. When you encounter a bug or need to understand why something behaves a certain way, being able to look at the actual engine code can be invaluable. The speaker shared how teams can use this access to fix engine-specific issues or even pull in specific bug fixes from newer engine versions without doing a full upgrade.
However, Chris also warned about the responsibility that comes with this power. Making engine modifications should be done thoughtfully and with proper version control in place. The goal isn’t to rewrite large portions of the engine but to make strategic improvements when necessary. He emphasized the importance of maintaining what he calls “sustainable engine customization” – making changes that won’t cause headaches during future engine updates.
Mistake #4: Missing Disabled Features
One of the most eye-opening parts of Murphy’s presentation was about hidden treasures in Unreal Engine. Many teams don’t realize that some of the engine’s most powerful features are turned off by default. This oversight can lead to teams spending months building systems that already exist in the engine.
A perfect example is the Gameplay Ability System (GAS). The presenter explained how this system, while disabled by default, provides a robust framework for handling character abilities, effects, and attributes. As someone who has worked on games with complex character systems, I can tell you that building something like this from scratch is a massive undertaking. Yet many teams do exactly that, unaware that Unreal already offers a battle-tested ability framework.
Other notable hidden Unreal features include the Water System for realistic water simulation, the State Tree for advanced AI behaviors, and the Procedural Content Generation system. The speaker emphasized that these aren’t just simple tools – they’re complete systems that have been used in major games like Fortnite. What’s particularly interesting is that these features often come with built-in solutions for common gaming challenges, like automatic buoyancy for objects in water.
Mistake #5: Not Rolling with Engine Changes
The fifth mistake Chris discussed touches on a common fear among development teams – dealing with engine updates. Many teams either completely avoid updates or try to update everything at once, both of which can cause problems. The key, as he explained, is to take a more strategic approach to engine version management.
What really caught my attention was his practical advice about selective feature integration. Instead of updating the entire engine, teams can often pull specific fixes or improvements from newer versions into their current build. This is particularly useful when you’re close to release and need a specific bug fix but can’t risk a full engine update.
This approach requires what he calls “smart version control” – keeping track of what changes you’ve integrated and maintaining a clear process for managing engine modifications. It’s something I’ve seen work well in practice, especially in larger projects where stability is crucial. Teams can stay current with important fixes while maintaining project stability, creating a balance between keeping up with engine improvements and maintaining a stable development environment.
Mistake #6: Misunderstanding Blueprint vs C++
One of the most heated debates I’ve seen in Unreal Engine development is about using Blueprint versus C++. The speaker addressed this head-on, pointing out that thinking of it as a choice between one or the other is already a mistake. From my experience in a AAA studio, I completely agree – it’s not about choosing sides, it’s about knowing when to use each tool.
Murphy emphasized that both Blueprint and C++ have their strengths in game development workflow. Blueprint shines in rapid prototyping, visual flow creation, and allowing non-programmers to build gameplay logic. Meanwhile, C++ offers better performance and more precise control over complex systems. The real power comes from what Murphy calls “symbiotic development” – using both tools together to create more efficient workflows.
What really resonated with me was his practical approach to this issue. Instead of treating Blueprint as “just for designers” or C++ as “just for programmers,” successful teams use them as complementary tools. For example, programmers can create robust base systems in C++ that designers can then extend through Blueprint, creating what the presenter describes as “flexible framework development” that benefits the entire team.
Mistake #7: Fighting the Framework
The seventh mistake Senior Technical Artist discussed is something I’ve witnessed many times – teams trying to force Unity’s way of doing things into Unreal Engine. This often happens when developers aren’t familiar with what Murphy calls the “Unreal gameplay framework” – the engine’s built-in systems for handling common game development needs.
For example, Unreal’s character movement system comes with a wealth of features out of the box. Yet some teams ignore this and build their own movement system from scratch, simply because that’s what they did in Unity. Murphy shared how this approach not only wastes time but also cuts teams off from future engine improvements and optimizations.
The solution isn’t just about learning new tools – it’s about understanding Unreal’s approach to game development. Murphy explained how features like the Pawn system, Player Controllers, and Game Modes work together to create a robust foundation for any game. When teams embrace these built-in Unreal systems instead of fighting against them, they often find that complex features become much easier to implement and maintain.
Mistake #8: Underutilizing Sample Projects
The speaker highlighted a resource that many teams surprisingly overlook – Unreal Engine sample projects. As someone who learned Unreal Engine through hands-on experimentation, I can’t stress enough how valuable these samples are. They’re not just basic demonstrations; they’re complete examples of professional game development practices.
What makes these samples particularly valuable is that each one serves a specific purpose. The City Sample, for example, shows how to handle large-scale environments and optimize performance. The speaker pointed out that teams can learn not just from the content itself, but from examining the project configuration files to understand how Epic achieved certain results. This kind of insight into optimization techniques is incredibly valuable, especially when dealing with challenging technical requirements.
Murphy specifically mentioned Lyra, Epic’s most advanced sample project, but with an interesting caveat. While it’s an incredible resource, he suggested that it might be too complex for teams just switching to Unreal. From my experience, I agree – it’s like trying to learn to drive by studying a Formula 1 car. Instead, he recommends starting with simpler samples like the Content Examples, which he describes as a “museum of Unreal Engine features.”
Take a look at best games made in Unreal Engine to understand how different studios implement UE features in practice. From Fortnite’s successful UE4 to UE5 transition to indie diamonds like Hellblade: Senua’s Sacrifice, see real-world examples of engine features being used effectively at different scales and budgets.
Unreal Engine Games: Best 17 UE4 and UE5 Games
Discover 17 Best Unreal Engine games that will blow you away! Explore stunning visuals and dive deeper into the future of game development.
Mistake #9: Ignoring Engine Evolution
One of the most interesting points was about keeping an eye on Fortnite’s development. This might seem strange at first – why watch a specific game when learning an engine? But as the presenter explained, Fortnite serves as a living showcase of Unreal Engine capabilities and best practices.
Epic regularly implements new Unreal Engine features in Fortnite, effectively testing them in a massive, real-world environment. He described this as “keeping Epic honest” – they’re not just creating features, they’re using them in a game played by millions. This means teams can learn from how Epic tackles common development challenges and implements new technologies.
What I found particularly valuable was the point about how Fortnite’s various game modes (Battle Royale, Creative, LEGO Fortnite) demonstrate different aspects of the engine’s capabilities. Each mode shows how Unreal Engine features can be adapted for different gameplay styles and technical requirements. By watching how Epic Games handles these implementations, teams can learn practical approaches to using new features in their own projects.
Mistake #10: Isolating from the Community
The final mistake Chris discussed really hits home for me as a developer who shares knowledge through blogging. Many teams try to handle their Unity to Unreal transition entirely on their own, missing out on what he calls the “collective wisdom of the Unreal community.”
What’s particularly interesting is how the presenter connected this to a common development pattern: teams often start prototyping in Unity with plans to switch to Unreal later. This leads to what described as a “cloak and dagger” situation where teams become secretive about their projects. As a result, they cut themselves off from valuable community support and resources that could help them overcome common challenges.
The Unreal Engine community offers multiple ways to connect and learn. From local meetups and Unreal Fest events to the Unreal Engine Developer Community, there are numerous opportunities for what the speaker calls “knowledge exchange.” These aren’t just places to ask questions – they’re venues for sharing discoveries, validating approaches, and building professional relationships that can benefit your entire team.
Conclusion
Looking back at Chris Murphy’s presentation, it’s clear that successful transition from Unity to Unreal Engine isn’t just about learning new tools – it’s about embracing a different approach to game development. As someone who works with both engines, I’ve seen how these mistakes can impact projects of all sizes.
The key takeaway isn’t that switching engines is difficult, but rather that most challenges are predictable and avoidable. Whether it’s improving team communication, embracing new roles, or taking advantage of built-in features, each of these potential pitfalls comes with clear solutions. His insights, backed by eight years of helping teams make this transition, provide a valuable roadmap for studios considering or currently making the switch.
What stands out most to me is how many of these mistakes stem from trying to force Unity workflows into Unreal Engine. Instead, success comes from being open to new approaches and willing to learn from both the engine’s capabilities and the broader development community. As he emphasized throughout the talk, the goal isn’t to recreate what you had in Unity, but to discover new and potentially better ways to achieve your development goals.
For teams considering the switch, Murphy’s advice offers a clear path forward: communicate effectively, remain curious about the engine’s capabilities, and don’t be afraid to engage with the broader Unreal community. After all, as he pointed out, about 80% of game development principles remain the same – it’s just the remaining 20% where teams need to adapt and grow.
From Unity to Unreal Engine: Frequently Asked Questions
Do I need to know C++ to switch from Unity to Unreal Engine?
No, you don’t need to start with C++. As discussed in the article, Unreal’s Blueprint visual scripting system allows developers to create complex gameplay mechanics without writing code. However, learning C++ alongside Blueprint can give you more flexibility and control over your projects.
What is the Gameplay Ability System in Unreal Engine and why is it important?
The Gameplay Ability System is a powerful framework in Unreal Engine for handling character abilities, effects, and attributes. It’s particularly useful for games with complex character interactions, power-ups, or status effects. While it’s disabled by default, it can save teams months of development time compared to building similar systems from scratch.
How can my team effectively share Unreal Engine discoveries?
Set up dedicated communication channels (like Slack or Discord) specifically for sharing engine-related findings. Encourage team members to document and share their solutions, useful settings, and Blueprint nodes they discover. Regular team meetings where members can share their “aha moments” can also be valuable.
Should we update to the latest Unreal Engine version whenever it’s available?
Not necessarily. As discussed in the article, it’s often better to be strategic about engine updates. Consider selectively implementing specific fixes or features you need rather than doing full version updates, especially when close to release. Always weigh the benefits of new features against the potential risks of updating.
What Unreal Engine sample projects should beginners start with?
I recommend starting with Unreal Engine Content Examples rather than more complex samples like Lyra. Content Examples serves as a “museum” of Unreal features and provides clear, focused demonstrations of different engine capabilities. As you become more comfortable, you can explore more complex samples.
How can different gamedev roles expand in Unreal Engine?
Various roles can take on new responsibilities: designers can work with Blueprint, animators can implement their own systems, artists can work with procedural tools, and technical artists can work across multiple systems. The key is being open to learning new tools and workflows.
What’s the best way to handle source code access in Unreal Engine?
Start by establishing clear processes and version control practices for engine modifications. Use source code access primarily for understanding systems, fixing specific bugs, or making targeted improvements. Avoid making extensive engine modifications unless absolutely necessary.
How can we maintain Unity workflows while learning Unreal Engine?
Instead of trying to recreate Unity workflows in Unreal, focus on understanding and adapting to Unreal’s built-in systems and framework. Remember that while 80% of game development principles remain the same, embracing Unreal’s approach to the remaining 20% is crucial for success.
What community resources are available for Unreal Engine learning?
The Unreal Engine community offers multiple resources including local meetups, Unreal Fest events, the Unreal Engine Developer Community, forums, and various online learning platforms. Epic Games also regularly publishes documentation and tutorials.
How can we learn from Fortnite’s development practices?
Watch how Epic implements new Unreal Engine features in Fortnite and its various game modes. Study their technical blog posts and documentation about specific implementations. This provides real-world examples of how to use engine features effectively at scale.
Share Your Experience
Have you made the switch from Unity to Unreal Engine? I’d love to hear about your experience in the comments below. What challenges did you face? Which of these mistakes resonate with your journey? Your insights could help other developers navigating this transition.
For the full presentation, you can watch Chris Murphy’s talk Top 10 Mistakes Made by Unity Teams When Switching to Unreal Engine | Unreal Fest 2024 on the Official Unreal Engine YouTube channel.
And if you’re currently making the switch to Unreal Engine and have questions, drop them in the comments. Let’s build a helpful discussion that supports our game development community!
Let’s connect on social media!
Want more insights like this? Subscribe to my newsletter for weekly updates!
