de6e324bdseparate emu thread10d3daf86Roms List improvements95d202f37Let's make the rom list process on a separate thread so the emulator doesnt take ages to load.fc306967fWow the ROM Header was just completely busted. Game list view works nowbad1691eefuck this shit2b59e5f46game list in progressd26417b83remappable inputs in progressac4af8106inpute72abc240update readme430139dc9Qt6 frontend3080d4d45Fix this small bug too08cd13b85Cop0 unused functions do not actually pose a threat (as per manual). They don't do anything, so shall we.61bb4fb44make idle loop detection a little more specific with where the load goesb037de4c3SAZDFsdff12e81e73eneed to figure out why n64-systemtest loops indefinitely at some address that appears to be valid (i think it's me not invalidating the cache properly)204f0e13bidle skipping seems to work!cb8bb634asdkfjlasdf58e5c89c1Fix compilation issue on my machine (no idea)24fb2898eattempting more serious idle skipping214719577Place rsp.Step inside cached interpreter. Gains about 3 more fpsbb97dcc23mmmmm920b77d38wjkhasdfjhkasdf430ccdab4it's a start...4f42a673aCached interpreter plays Mario 64. Start looking into RSP as wellc9a030787idle skipping works!5fbda03cenew idea366637abaIdle skipping... maybe?609fa2fb0Cache instructions implemented but broken lmao. Commented out for nowe140a6d12- Stop using inheritance for CPU, instead use composition. - Introduce KAIZEN_JIT_ENABLED optional define instead of relying on __aarch64__ and the like. - More cache work68e613057prep cache impl811b4d809fix clang formatfda755f7didkd5024ebbfsmall MI refactor in preparation of (eventually) implementing the RDRAM interface properly694b45341Merge commit '206dcdedf195fb320913584180edb12c7731e396' as 'external/SDL'206dcdedfSquashed 'external/SDL/' content from commit 4d17b99d0a4d16e1cb4need to update sdl848b19920Fix compilation errordb61b5299Merge commit 'e94a94559f28e49678fbcf72199a5258137b0fe9' as 'external/imgui'e94a94559Squashed 'external/imgui/' content from commit 02e9b8cac52edb3757need to update imguic1a705e86Emulate weird JALR behaviour4b4c32f4bFix exception for "unusable COP1" in 4 instructions i missed accidentally (again)df5828142Bug putting 0s in the log everywheref8b580048Make isviewer a sink to file8241e9735Fix exception for "unusable COP1" in 4 instructions i missed accidentallyb29715f20small changesd9a620bc1make use of my new small utility library0d1aa938eAdd 'external/ircolib/' from commit 'ce3cd726c8df8388d554abf8bb55d55020eb4450'e64eb40b3Fuck git git-subtree-dir: external/ircolib git-subtree-split:de6e324bde
9.5 KiB
OpenXR / VR Development with SDL
This document covers how to build OpenXR (VR/AR) applications using SDL's GPU API with OpenXR integration.
Overview
SDL3 provides OpenXR integration through the GPU API, allowing you to render to VR/AR headsets using a unified interface across multiple graphics backends (Vulkan, D3D12, Metal).
Key features:
- Automatic OpenXR instance and session management
- Swapchain creation and image acquisition
- Support for multi-pass stereo rendering
- Works with desktop VR runtimes (SteamVR, Oculus, Windows Mixed Reality) and standalone headsets (Meta Quest, Pico)
Desktop Development
Requirements
-
OpenXR Loader (
openxr_loader.dll/libopenxr_loader.so)- On Windows: Usually installed with VR runtime software (Oculus, SteamVR)
- On Linux: Install via package manager (e.g.,
libopenxr-loader1on Ubuntu) - Can also use
SDL_HINT_OPENXR_LIBRARYto specify a custom loader path
-
OpenXR Runtime
- At least one OpenXR runtime must be installed and active
- Examples: SteamVR, Oculus Desktop, Monado (Linux)
-
VR Headset
- Connected and recognized by the runtime
Basic Usage
#include <openxr/openxr.h>
#include <SDL3/SDL.h>
#include <SDL3/SDL_openxr.h>
// These will be populated by SDL
XrInstance xr_instance = XR_NULL_HANDLE;
XrSystemId xr_system_id = 0;
// Create GPU device with XR enabled
SDL_PropertiesID props = SDL_CreateProperties();
SDL_SetBooleanProperty(props, SDL_PROP_GPU_DEVICE_CREATE_XR_ENABLE_BOOLEAN, true);
SDL_SetPointerProperty(props, SDL_PROP_GPU_DEVICE_CREATE_XR_INSTANCE_POINTER, &xr_instance);
SDL_SetPointerProperty(props, SDL_PROP_GPU_DEVICE_CREATE_XR_SYSTEM_ID_POINTER, &xr_system_id);
// Optional: Override app name/version (defaults to SDL_SetAppMetadata values if not set)
SDL_SetStringProperty(props, SDL_PROP_GPU_DEVICE_CREATE_XR_APPLICATION_NAME_STRING, "My VR App");
SDL_SetNumberProperty(props, SDL_PROP_GPU_DEVICE_CREATE_XR_APPLICATION_VERSION_NUMBER, 1);
SDL_GPUDevice *device = SDL_CreateGPUDeviceWithProperties(props);
SDL_DestroyProperties(props);
// xr_instance and xr_system_id are now populated by SDL
See test/testgpu_spinning_cube_xr.c for a complete example.
Android Development
Building OpenXR applications for Android standalone headsets (Meta Quest, Pico, etc.) requires additional manifest configuration beyond standard Android apps.
Android Manifest Requirements
The manifest requirements fall into three categories:
- OpenXR Standard (Khronos) - Required for all OpenXR apps
- Platform-Specific - Required for specific headset platforms
- Optional Features - Enable additional capabilities
OpenXR Standard Requirements (All Platforms)
These are required by the Khronos OpenXR specification for Android:
Permissions
<!-- OpenXR runtime broker communication -->
<uses-permission android:name="org.khronos.openxr.permission.OPENXR" />
<uses-permission android:name="org.khronos.openxr.permission.OPENXR_SYSTEM" />
Queries (Android 11+)
Required for the app to discover OpenXR runtimes:
<queries>
<provider android:authorities="org.khronos.openxr.runtime_broker;org.khronos.openxr.system_runtime_broker" />
<intent>
<action android:name="org.khronos.openxr.OpenXRRuntimeService" />
</intent>
<intent>
<action android:name="org.khronos.openxr.OpenXRApiLayerService" />
</intent>
</queries>
Hardware Features
<!-- VR head tracking (standard OpenXR requirement) -->
<uses-feature android:name="android.hardware.vr.headtracking"
android:required="true"
android:version="1" />
<!-- Touchscreen not required for VR -->
<uses-feature android:name="android.hardware.touchscreen"
android:required="false" />
<!-- Graphics requirements -->
<uses-feature android:glEsVersion="0x00030002" android:required="true" />
<uses-feature android:name="android.hardware.vulkan.level"
android:required="true"
android:version="1" />
<uses-feature android:name="android.hardware.vulkan.version"
android:required="true"
android:version="0x00401000" />
Intent Category
<activity ...>
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
<!-- Khronos OpenXR immersive app category -->
<category android:name="org.khronos.openxr.intent.category.IMMERSIVE_HMD" />
</intent-filter>
</activity>
Meta Quest Requirements
These are required for apps to run properly on Meta Quest devices. Without these, your app may launch in "pancake" 2D mode instead of VR.
VR Intent Category (Critical!)
<activity ...>
<intent-filter>
...
<!-- CRITICAL: Without this, app launches in 2D mode on Quest! -->
<category android:name="com.oculus.intent.category.VR" />
</intent-filter>
</activity>
Supported Devices
<application ...>
<!-- Required: Specifies which Quest devices are supported -->
<meta-data android:name="com.oculus.supportedDevices"
android:value="quest|quest2|questpro|quest3|quest3s" />
</application>
Focus Handling (Recommended)
<application ...>
<!-- Properly handles when user opens the Quest system menu -->
<meta-data android:name="com.oculus.vr.focusaware"
android:value="true" />
</application>
Hand Tracking (Optional)
<!-- Feature declaration -->
<uses-feature android:name="oculus.software.handtracking"
android:required="false" />
<application ...>
<!-- V2.0 allows app to launch without controllers -->
<meta-data android:name="com.oculus.handtracking.version"
android:value="V2.0" />
<meta-data android:name="com.oculus.handtracking.frequency"
android:value="HIGH" />
</application>
VR Splash Screen (Optional)
<application ...>
<meta-data android:name="com.oculus.ossplash"
android:value="true" />
<meta-data android:name="com.oculus.ossplash.colorspace"
android:value="QUEST_SRGB_NONGAMMA" />
<meta-data android:name="com.oculus.ossplash.background"
android:resource="@drawable/vr_splash" />
</application>
Pico Requirements
For Pico Neo, Pico 4, and other Pico headsets:
VR Intent Category
<activity ...>
<intent-filter>
...
<!-- Pico VR category -->
<category android:name="com.picovr.intent.category.VR" />
</intent-filter>
</activity>
Supported Devices (Optional)
<application ...>
<!-- Pico device support -->
<meta-data android:name="pvr.app.type"
android:value="vr" />
</application>
HTC Vive Focus / VIVE XR Elite
<activity ...>
<intent-filter>
...
<!-- HTC Vive category -->
<category android:name="com.htc.intent.category.VRAPP" />
</intent-filter>
</activity>
Quick Reference Table
| Declaration | Purpose | Scope |
|---|---|---|
org.khronos.openxr.permission.OPENXR |
Runtime communication | All OpenXR |
android.hardware.vr.headtracking |
Marks app as VR | All OpenXR |
org.khronos.openxr.intent.category.IMMERSIVE_HMD |
Khronos standard VR category | All OpenXR |
com.oculus.intent.category.VR |
Launch in VR mode | Meta Quest |
com.oculus.supportedDevices |
Device compatibility | Meta Quest |
com.oculus.vr.focusaware |
System menu handling | Meta Quest |
com.picovr.intent.category.VR |
Launch in VR mode | Pico |
com.htc.intent.category.VRAPP |
Launch in VR mode | HTC Vive |
Example Manifest
SDL provides an example XR manifest template at:
test/android/cmake/AndroidManifest.xr.xml.cmake
This template includes:
- All Khronos OpenXR requirements
- Meta Quest support (configurable via
SDL_ANDROID_XR_META_SUPPORTCMake option) - Proper intent filters for VR launching
Common Issues
App launches in 2D "pancake" mode
Cause: Missing platform-specific VR intent category.
Solution: Add the appropriate category for your target platform:
- Meta Quest:
com.oculus.intent.category.VR - Pico:
com.picovr.intent.category.VR - HTC:
com.htc.intent.category.VRAPP
"No OpenXR runtime found" error
Cause: The OpenXR loader can't find a runtime.
Solutions:
- Desktop: Ensure VR software (SteamVR, Oculus) is installed and running
- Android: Ensure your manifest has the correct
<queries>block for runtime discovery - Linux: Install
libopenxr-loader1and configure the active runtime
OpenXR loader not found
Cause: openxr_loader.dll / libopenxr_loader.so is not in the library path.
Solutions:
- Install the Khronos OpenXR SDK
- On Windows, VR runtimes typically install this, but may not add it to PATH
- Use
SDL_HINT_OPENXR_LIBRARYto specify the loader path explicitly
Vulkan validation errors on shutdown
Cause: GPU resources destroyed while still in use.
Solution: Call SDL_WaitForGPUIdle(device) before releasing any GPU resources or destroying the device.
Additional Resources
- Khronos OpenXR Specification
- Meta Quest Developer Documentation
- Pico Developer Documentation
- SDL GPU API Documentation
- Example code:
test/testgpu_spinning_cube_xr.c