WinlatorXR is a port of Winlator for Meta Quest and Pico headsets. It uses 2D/VR hybrid app flow documented by amwatson.

History of the project

• Winlator is originally developed by brunodev85 but as he does not opensource the latest versions then I am forced to use a custom fork for this project.
• In 2024 WinlatorXR was based on Glibc fork by longjunyu2 but as he stopped communicating, the project was inactive for a long time and later it stopped working.
• In 2025 Pipetto-crypto ported Winlator to Bionic/Proton which is a massive boost for Meta Quest integration.
• His integration was enhanced by coffincolors in Winlator CMOD fork which is now base for WinlatorXR.
• Pico support and XR enhancement were brought by Tobbe85.
• Play for Dream support was brought by EasonZxp.
• Content is maintained by StevenMXZ who maintains it for Winlator-Bionic.

How to compile

1.Clone repository with all submodules git clone --recursive git@github.com:Team-Beef-Studios/WinlatorXR.git

2.Donwload the latest APK from releases

3.Unzip the APK and copy the content of assets into app/src/main/assets/ (except dexopt folder)

4.Open the project in Android Studio and have fun :)

WinlatorXR API

Our XrAPI provides developers with a way to replace OpenVR or OpenXR in their applications, enabling PCVR content to run natively within WinlatorXR on standalone VR headsets. The XrAPI is still very experimental and may change over time.

Required changes for the Windows app

1. WinlatorXR checks for Z:\tmp\xr\version file and read the API version which should be used
2. The data are sent using UDP protocol on localhost:7872 as AsCII string in order which can be found below.
3. It is important to keep the Windows app as much in sync as possible, ideally holding renderer until HMD_SYNC changes.
4. Windows app have to render value of HMD_SYNC as shade of red (in sRGB colorspace) into top-left corner.
5. Information about used headset is written into Z:\tmp\xr\system (manufacturer, product, Android version, security patch version).

XrAPI 0.3 specification

The Windows app/game has to sent data on localhost:7278 as string of float numbers separated by space:

L_HAPTICS, R_HAPTICS, MODE_VR, MODE_3D, HMD_FOVX, HMD_FOVY

• The haptic values indicates length in frames how long should controller vibrate (the first value is for left controller and the second for the right one).
• The VR mode is 1 to enable, 0 to disable. To receive HMD and controllers data, the VR mode has to be enabled.
• The 3D mode is 2 for alternate-eye-rendering, 1 for side-by-side, 0 for flat screen, -1 to give user the control.
• If FOV values are higher than 1 then it forces a custom Field-of-View values in degrees. This is need by apps and games where the variable FOV isn't supported.

3D modes:

• alternate-eye-rendering - set blue framesync pixel to 0 when rendering left eye, 255 when rendering right eye, quickly swapping left and right eye brings 3D effect
• side-by-side - the left half of the container is drawn to left eye and right half to right eye

The data transfered over UDP starts with an array of float numbers separated by space, the values are:

L_QX, L_QY, L_QZ, L_QW, L_THUMBSTICK_X, L_THUMBSTICK_Y, L_X, L_Y, L_Z, 
R_QX, R_QY, R_QZ, R_QW, R_THUMBSTICK_X, R_THUMBSTICK_Y, R_X, R_Y, R_Z, 
HMD_QX, HMD_QY, HMD_QZ, HMD_QW, HMD_X, HMD_Y, HMD_Z, HMD_IPD, HMD_FOVX, HMD_FOVY, HMD_SYNC

next is a string containing characters T (for TRUE) and F (for FALSE). This string represents the controller buttons in order:

L_GRIP, L_MENU, L_THUMBSTICK_PRESS, L_THUMBSTICK_LEFT, L_THUMBSTICK_RIGHT, L_THUMBSTICK_UP, L_THUMBSTICK_DOWN, L_TRIGGER, L_X, L_Y,
R_A, R_B, R_GRIP, R_THUMBSTICK_PRESS, R_THUMBSTICK_LEFT, R_THUMBSTICK_RIGHT, R_THUMBSTICK_UP, R_THUMBSTICK_DOWN, R_TRIGGER

next is a string containing characters T (for TRUE) and F (for FALSE). This string represents the XR flags in order:

Immersive, SBS

Code examples

• SixDOFinator_MinimalProject - Unity sample implementation (minimal project)
• SixDOFinator_SampleProject - Unity sample implementation (full project)

---

Original README:

Winlator

Winlator is an Android application that lets you to run Windows (x86_64) applications with Wine and Box86/Box64.

Installation

1. Download and install the APK (Winlator_7.1.apk) from GitHub Releases
2. Launch the app and wait for the installation process to finish

---

---

Useful Tips

• If you are experiencing performance issues, try changing the Box86/Box64 preset in Container Settings -> Advanced Tab.
• For applications that use .NET Framework, try installing Wine Mono found in Start Menu -> System Tools.
• If some older games don't open, try adding the environment variable MESA_EXTENSION_MAX_YEAR=2003 in Container Settings -> Environment Variables.
• Try running the games using the shortcut on the Winlator home screen, there you can define individual settings for each game.
• To speed up the installers, try changing the Box86/Box64 preset to Intermediate in Container Settings -> Advanced Tab.

Credits and Third-party apps

• Ubuntu RootFs (Focal Fossa)
• Wine (winehq.org)
• Box86/Box64 by ptitseb
• PRoot (proot-me.github.io)
• Mesa (Turnip/Zink/VirGL) (mesa3d.org)
• DXVK (github.com/doitsujin/dxvk)
• VKD3D (gitlab.winehq.org/wine/vkd3d)
• D8VK (github.com/AlpyneDreams/d8vk)
• CNC DDraw (github.com/FunkyFr3sh/cnc-ddraw)

Many thanks to ptitSeb (Box86/Box64), Danylo (Turnip), alexvorxx (Mods/Tips) and others.

Thank you to all the people who believe in this project.