Skip to main content
XR Media & 3D Scenes

Implementation Detail

In short
  • What is checked: the XR player (Presentation Engine), the Media Access Function and the reference scene files, against ISO/IEC 23090-14 (second edition) and the XR clauses of TS 26.119, TS 26.143 and TS 26.565.
  • What works: loading and playing media through circular buffers, timed accessors, video textures, part of the spatial audio, and the larger part of AR anchoring and interactivity.
  • What is partial or missing: several anchoring and interactivity behaviours differ from the specification; scene updates, mesh linking, recommended viewports, animation timing, lighting, avatars and haptics are not used by the reference scenes or are not handled by the player. Many extensions are not used by the reference scenes; those are shown as absent, which means not in the repositories, not a defect.
  • Source of this page: an audit of the main branch of the XR repositories on 2026-10-11, each case read against the code by one reader and then independently by a second, with a third reading where they disagreed; nothing was run. Cases that could not be settled by reading the code are not shown.

For what the specifications define, see the Technology page and the Standards. For how to run the tools, see the Tutorials.

Implementation status​

Open a feature, then a requirement, to see each case and why. Filter by component and profile.

  • XR Media & 3D Scenes.
  • Presentation Engine (Presentation Engine (rt-xr-unity-player with its glTFast loader)): rt-xr-unity-player, rt-xr-gITFast. Built against: ISO/IEC 23090-14 (second edition), TS 26.119 V19.1.0, TS 26.143 V19.1.0, TS 26.565 V19.0.0.
  • Media Access Function (Media Access Function (rt-xr-maf-native)): rt-xr-maf-native. Built against: ISO/IEC 23090-14 (second edition), TS 26.119 V19.1.0, TS 26.143 V19.1.0, TS 26.565 V19.0.0.
  • Scene files (Scene files and exporter (rt-xr-content, rt-xr-blender-exporter)): rt-xr-content, rt-xr-blender-exporter. Built against: ISO/IEC 23090-14 (second edition), TS 26.119 V19.1.0, TS 26.143 V19.1.0, TS 26.565 V19.0.0.
  • Source: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group, 2026-10-11.
  • Not shown: 9 further cases (it could not be settled by reading the code).
3GPP release
113 of 370 implemented · 62 differ · 195 absentcases, over 87 requirements

✓ Implemented≠ Differs from the specification– Absent? Specification inconsistent: its text and its OpenAPI or tables disagreei Noted: observed, not a verdict against a clause

MPEG_media7 of 18 implemented · 2 differ · 9 absent
MPEG_accessor_timed11 of 22 implemented · 8 differ · 3 absent
MPEG_buffer_circular5 of 7 implemented · 1 differs · 1 absent
MPEG_texture_video8 of 23 implemented · 1 differs · 14 absent
MPEG_audio_spatial7 of 21 implemented · 2 differ · 12 absent
MPEG_mesh_linking0 of 7 implemented · 7 absent
MPEG_scene_dynamic0 of 23 implemented · 23 absent
MPEG_animation_timing0 of 9 implemented · 9 absent
Augmented Reality anchor (MPEG_anchor)20 of 49 implemented · 16 differ · 13 absent
Interactivity16 of 54 implemented · 17 differ · 21 absent
Avatar0 of 3 implemented · 3 absent
Lighting1 of 13 implemented · 12 absent
Haptics0 of 1 implemented · 1 absent
The MAF API and the buffer interface19 of 41 implemented · 9 differ · 13 absent
How timed media reaches the renderer3 of 36 implemented · 1 differs · 32 absent
General16 of 31 implemented · 5 differ · 10 absent
Full audit for members

The full audit, with the code behind each verdict, is available to 5G-MAG members through Developer Tools.

Become a member · Request access