Flexy Blogs

Texel Density Is the Argument You Are Actually Having

Texel Density Is the Argument You Are Actually Having

When outsourced art "looks inconsistent", the cause is almost never talent. It is that nobody specified pixels per metre.

A studio brings me in because their outsourced environment art "looks inconsistent". They suspect the vendor put junior artists on it. Nine times in ten, the models are fine and the problem is texel density.

What it is, briefly

Texel density is how many texture pixels cover a given amount of world space — pixels per metre, usually. If one crate uses 512 pixels per metre and the crate next to it uses 1024, they will look like they belong to different games no matter how well each is made individually.

The eye is extremely good at spotting this and extremely bad at naming it. Which is why it surfaces as a vague complaint about quality.

Why "use 2K textures" does not fix it

Because a 2K texture on a one-metre crate and a 2K texture on a ten-metre wall are wildly different densities. Specifying resolution instead of density is the single most common mistake in outsourcing briefs, and it guarantees the inconsistency it is trying to prevent.

What to specify instead

  • A target density in px/m for each asset class — hero props, background props, architecture, terrain
  • An acceptable tolerance, because rounding to power-of-two texture sizes means exact matching is impossible
  • A reference asset supplied with the brief, already at target

That reference asset does more work than the rest of the document. Artists calibrate against an example far faster than against a number.

Checking it without trusting anyone

Most DCC packages have a checker-map workflow: apply a standard checker texture at a known size and compare square sizes across assets visually. It takes minutes and it is unambiguous. Build it into your acceptance step rather than discovering the problem at integration.

The conversation to have up front

When I have briefed partners like PolyGame Studio, the density question comes up in their first reply. That is the behaviour you want — a vendor asking about density before asking about style is a vendor who has integrated into someone else's pipeline before.

If you are getting inconsistent art back, check density before you question anyone's skill. It is usually a specification failure wearing a quality-problem costume.

Mei-Ling Chen

Technical artist
Mei-Ling builds asset pipelines for small studios. Topology budgets, LODs, bake errors at 2am — the parts of game art nobody puts in the showreel.
View all posts

0 Comments

No comments yet — be the first to share what you think.

Leave a reply

Your email address is never published.