What is Measured PBR?

Why is PBR important?

PBR stands for physically based rendering, and it has changed 3D. It gave artists, engineers, and studios a shared framework for describing how materials look and behave, how rough an object actually is or how light scatters off a surface. Drop a PBR asset into Unreal or Unity and the engine knows what to do with it. The interoperability is the point.

But there's a problem baked into that promise that the industry rarely confronts directly.

Nobody actually agrees on what PBR is.

The approximation problem - M-XR’s thoughts

PBR is not physics. It's a mathematical approximation of physics, a set of equations designed to be intuitive enough for artists to use as a creative tool, not rigorous enough to satisfy a material scientist.

The consequence of that design is significant: because PBR is an approximation, there are no universal ground truth values for what the "correct" PBR material properties are for any given real-world material.

What does “correct” actually look like?

For a single artist working on a single project, this doesn't create a problem. You adjust roughness until the leather looks right. You tweak the specular until the chrome feels real. Whatever combination of values produces the best looking result is, in that context, correct. The end result is the measure of success.

Different artists will arrive at different values for the same material. Different render engines have their own variants of PBR with their own properties. Different capture workflows make different assumptions. And because there's no agreed definition of "measured" in measured PBR, the term can mean almost anything.

For a single artist, this is fine. For an industry trying to build consistent, scalable, AI-ready pipelines, it isn't.

Studios are building training datasets. They're deploying real-time pipelines. They're creating material libraries that need to be portable, reusable, and reliable across engines, projects, and teams. At that scale, the ambiguity in how "correct" is interpreted turns into a real problem.

The industry has been papering over it for years. M-XR is addressing it directly.

What measured PBR actually means?

The word "measured" is doing a lot of work and it means exactly what it says.

Instead of approximating PBR values through intuition, inversion, or artist judgment, measured PBR captures them directly from the physical material itself.

When light hits a real surface, it scatters in a pattern that is unique to that material. The mathematical description of that scattering, its intensity relative to the surface, its distribution across angles - is called a BRDF. That lobe of light carries the information that defines how a material truly behaves.

M-XR's Marso Measure captures that information. Using a camera, a flash, and a standard photogrammetry workflow, no custom hardware, no lab environment. It maps the measured light behaviour of a real surface directly onto a PBR shader. The result isn't an interpretation of what the material should look like. It's what the material actually is.

When that asset loads into an engine, the shader isn't making assumptions. It's rendering from data.

Why consistency changes everything?

This is where the M-XR approach has implications beyond individual asset quality.

Because measured PBR removes the subjectivity from material capture, every asset produced through Marso Measure follows the same underlying standard, regardless of who captured it, when, or on what hardware. That consistency makes assets more portable and it makes them more useful as training data.

For studios investing in AI workflows, real-time pipelines, or high-fidelity content at volume, that consistency isn't a feature. It's the foundation.

For 3D artists, it means something more immediate: you stop second-guessing your roughness values and start capturing. The output equals measured, consistent, physically grounded PBR maps that drop into your engine without cleanup. The material looks right because Marso Measure is right.

Building towards a standard

The broader challenge is that the industry still doesn't have a universally agreed definition of what measured PBR is. Different systems make different assumptions. Different workflows produce different values. "PBR-ready" can mean almost anything.

Measured PBR is what you get when you stop approximating and start measuring. That's what we do at M-XR.

Want to try Marso Measure out and understand further what measured PBR looks like? You can by creating your M-XR account and getting started.