Render device unavailability
Generated from engine/render/device_unavailable.h at aceb130. The text under each declaration is the header's own comment, word for word. About the reference says how these pages are made.
Audience: game code.
#include "engine/render/device_unavailable.h" · namespace labrador
class RenderDeviceUnavailable
Section titled “class RenderDeviceUnavailable”The selected renderer cannot meet its device or context requirements at startup. This does not establish that the machine physically lacks a GPU. The message retains the backend's reason and any native error details.
Catch this category to choose a startup refusal message or an optional graphics policy. It remains a std::runtime_error for existing handlers. Content, shaders, invalid arguments/state, unrelated API failures, audio and runtime device-loss recovery are outside this category. No fallback backend is selected by throwing or catching it. Ambiguous browser context refusals can also be caller-owned canvas state and remain ordinary runtime errors; this category is not exhaustive.
RenderDeviceUnavailable
Section titled “RenderDeviceUnavailable”Stores reason in the runtime_error base; what() preserves its text.
In the samples and tests
Section titled “In the samples and tests”The files that include this header directly. A file can also reach it through another header.
tests/render/d3d11/startup_tests.cpptests/render/d3d12/instrumented_device_resources.cpp,startup_tests.cpptests/render/dds_file_tests.cpp,device_unavailable_tests.cpptests/render/gl/context_unavailable_tests.cpp,material_tests.cpp,texture_tests.cpp,web_context_unavailable_tests.cpptests/render/vulkan/initialization_tests.cpp,shader_failure_tests.cpp
Explained in
Section titled “Explained in”Development documentation (unreleased). Built from Labrador aceb130 of 2026-11-20.