About Dino Sloth

Game engineering, measured carefully.

A game-engineering consultancy specialising in Unreal performance, iteration health and technical delivery diligence.

Robert Troughton, founder of Dino Sloth

Founder

Robert Troughton

Dino Sloth was founded by Robert Troughton, who began as a programmer on Destruction Derby, co-founded Pitbull Syndicate and led work on the Test Drive series. Midway acquired the studio in 2005, and he became lead optimisation programmer — console frame time, full time, for four years.

He later founded Pitbull Studio. Epic Games acquired it in 2014, and he became General Manager of Epic Games UK, leading a team contributing to Unreal Engine 4 and Fortnite.

After Epic he founded Coconut Lizard, working at engine level with studios including Rare and Funcom. Keywords Studios acquired it in 2020.

Since then the founder has kept building and profiling in Unreal on personal projects, because reading a capture is a skill you lose.

Across those businesses the founder worked with publishers, AAA development teams, acquirers and technology partners — from winning the relationships to delivering the work they were built around. That operating experience informs the work; Dino Sloth remains focused on the build, the pipeline and the technical delivery decision.

Who works on an engagement. Dino Sloth selects people appropriate to the work. Everyone who will work on an engagement is identified to the client by name and role, and covered by the same confidentiality, access and deletion terms, before access is granted.
30 years in games 3 studios founded or co-founded 3 exits

In practice

Most of this job is reading a capture carefully.

Not workshops, not frameworks, not a deck of maturity scores. A build, a devkit, a trace, and the patience to work out which of the six plausible explanations is the one the evidence actually supports.

The other half is the conversation afterwards: telling a studio head that the thing everybody has been arguing about for a month is worth 0.4 ms, and the thing nobody has mentioned is worth nine. That part needs thirty years of having been wrong often enough to know how to check.

How engagements are built

One scope. Clear accountability.

Each engagement is shaped around the decision, evidence and expertise required. Responsibilities and review boundaries are agreed before client material is shared.

01
A decision-led scope

The question, required evidence and useful outcome are defined before work begins.

02
Relevant expertise

Work stays within demonstrated experience; additional disciplines are identified rather than quietly implied.

03
Controlled access

Everyone requiring client material is identified, approved and covered by the engagement's confidentiality terms.

04
One integrated answer

Technical evidence, operating context and specialist input come together in a single accountable deliverable.

Why the mix matters

Technical depth with delivery context.

The work combines experience writing and fixing performance-critical code with a practical understanding of milestones, technical risk and what teams can reasonably deliver.

01
Engine depth

Frame-time investigation, render-thread and GPU cost, memory attribution, engine forks and upgrade pain. Unreal since UE3, and console optimisation as a full-time job before that.

02
Delivery context

Milestones, dependencies, development partners and the pressure that exposes technical assumptions.

03
Technical diligence

Can the build support the claim, and what technical risk follows the decision?

And yes — the name. Two of the slowest animals in the world, fronting a consultancy that exists to make things faster. It is deliberate. Nothing in this work is fixed by moving quickly; it is fixed by measuring carefully, and most of the expensive mistakes Dino Sloth is called in to unpick were made at speed by people who were certain. The joke is the point.

Fit

Where Dino Sloth is most useful

Bring Dino Sloth

  • Performance and engine-level problems
  • Build, cook, DDC and shader-compilation pipelines
  • Milestone plans, cert readiness and technical delivery risk
  • Technical delivery diligence
  • Third-party technology and service decisions

Requires separate specialist scope

  • Creative direction and game feel
  • Animation-system, online, audio and gameplay-system design
  • Backend security and infrastructure certification
  • Marketing and community
  • Legal or financial opinions

Next step

Need a clear technical picture?