Extension allows you to consult thermal trends by domain. Here's how to degrade quality without promising universal support.
Direct answer
OpenXR's XR_EXT_thermal_query extension allows you to query the state and thermal trend of device domains, helping applications react before severe performance degradation. It is not a ratified or universal extension, so the application must check for support at runtime and maintain its own telemetry and fallback. The correct use is to gradually adapt resolution, effects or load, preserving comfort and critical task.
Trend helps to act before the limit
Sustained increase can trigger gradual reduction, avoiding a sudden change after the runtime has already needed to limit the device.
Domains ask for different answers
CPU, GPU and other components can have different bottlenecks. Policy must reduce the burden it actually contributes.
Adaptive quality needs order
Define a ladder: effects, shadows, resolution, update frequency and complexity, preserving readability and security.
Optional extension requires fallback
Without support, use available engine metrics, frame timing, and conservative profiles. Don't block the experience by an auxiliary resource.
Nexus Reading
Combine thermal signal, frame time and session duration; Validate the policy in hot, cold environment and long-term use.
FAQ
Is the extension a mandatory part of OpenXR 1.1?
No. It is optional and indicated as not ratified.
Does it measure exact temperature?
The focus is on thermal status and trend per domain, not necessarily exposing degrees Celsius.
Should I reduce everything to the first alert?
No. A tested, gradual ladder preserves quality and prevents oscillation.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on October 19, 2026. The text is original and interprets practical implications for companies.
- Khronos — XR_EXT_thermal_query: state, trend, thermal domain, and unratified status.
- Khronos — OpenXR 1.1 specification: negotiation of extensions, contracts and portability.
Date reported by main source: OpenXR 1.1 specification, extension revision 2; analysis on October 19, 2026.