winlatorxr.github.io/about.html at main · WinlatorXR/winlatorxr.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head profile="http://www.w3.org/2005/10/profile">
  <link rel="icon" type="image/png" href="img/favicon.png">
  <meta http-equiv="Content-Language" content="en" />
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="author" content="WinlatorXR" />
  <meta name="description" content="WinlatorXR" />
  <meta name="robots" content="index,nofollow" />
  <meta name="copyright" content="WinlatorXR" />
  <link rel="stylesheet" href="styles.css">
  <title>WinlatorXR</title>
</head>
<body>
  <script src="scripts.js" defer></script>
  <table>
    <tr>
      <td class="col_logo">
        <img src="img/logo.png" width="100%">
      </td>
      <td class="col_text">
        <p>
          <strong>WinlatorXR</strong> is a next-generation Windows compatibility environment
          built specifically for Extended Reality (XR). It enables users to run full Windows
          applications and games inside immersive VR and AR spaces—bringing the power of
          desktop software into a spatial, interactive world.
        </p>

        <p>
          Designed for performance and flexibility, WinlatorXR bridges the gap between
          traditional Windows programs and modern XR headsets. Whether you're launching
          productivity tools, creative software, or classic PC games, WinlatorXR transforms
          them into immersive experiences optimized for virtual environments.
        </p>

        <ul>
          <li><strong>Run Windows Apps in XR</strong> – Seamlessly execute desktop software inside virtual and mixed reality spaces.</li>
          <li><strong>Optimized Performance</strong> – Engineered for smooth rendering and low latency in XR hardware environments.</li>
          <li><strong><a href="xrapi.html" target="contentFrame">Gaming in VR</a></strong> – Play compatible Windows PC titles within immersive virtual displays.</li>
          <li><strong>Developer-Friendly</strong> – Built with compatibility and extensibility in mind.</li>
        </ul>
      </td>
    </tr>
  </table>

  <h1>Supported headsets</h1>
  <p>
    Although the Quest 3 and Quest 3 S remain the most popular headsets for running WinlatorXR, our compatibility extends well beyond Meta’s ecosystem. The Pico 4 Ultra, for example, is a strong alternative. Thanks to its Turnip driver support, it can deliver slightly better performance than the Quest 3 in many scenarios. The base Pico 4 model, however, lacks a crucial Vulkan extension; as a result, it can run only DirectX 7 and DirectX 8 titles, and we currently consider it effectively unsupported. Surprisingly, the older Meta Quest 2 continues to perform admirably. With the Turnip driver enabled, it offers full compatibility and often works far better than expected for a device of its generation.
  <p/>
  <p>
    We’ve also benefited from community contributions. A developer from Play for Dream kindly added support for the Play for Dream MR headset. While this support remains in the project, we cannot guarantee long-term reliability, as we do not have access to the hardware for continuous testing.
  <p/>

  <h1>Credits</h1>
  <h2>WinlatorXR</h2>
  <ul>
    <li><strong>Luboš V.</strong> develops the XR integration for the project.</li>
    <li><strong>Bigelowed</strong> integrates WinlatorXR API into several projects.</li>
    <li><strong>GmoLargey</strong> does the testing and creates tutorials.</li>
    <li><strong>Tobbe85</strong> ported the project to Pico headsets.</li>
    <li><strong>EasonZxp</strong> ported the project to Play for Dream headsets.</li>
    <li><strong>No1</strong> takes care of SideQuest listing and updates.</li>
  </ul>
  <p>
    Special thanks to Amanda Watson for writing a tutorial on developing hybrid (2D/VR) applications. That knowledge was unavailable elsewhere, and this project would not have been possible without her contribution.
  </p>

  <h2>Winlator Cmod (which is WinlatorXR based on)</h2>
  <ul>
    <li>Winlator was created by Brunodev85 (<a href="https://github.com/brunodev85" target="_blank" rel="noopener noreferrer">GitHub</a>)</li>
    <li>Winlator Cmod by
      <a href="https://github.com/coffincolors/winlator" target="_blank" rel="noopener noreferrer">coffincolors</a>,
      <a href="https://github.com/Pipetto-crypto/winlator" target="_blank" rel="noopener noreferrer">Pipetto-crypto</a>
    </li>
    <li>Winlator Glibc by longjunyu2 (<a href="https://github.com/longjunyu2/winlator/" target="_blank" rel="noopener noreferrer">Fork</a>)</li>
    <li>Big Picture Mode Music by Fumer</li>
  </ul>

  <h2>Third-Party Applications</h2>
  <ul>
    <li>Ubuntu RootFs (<a href="https://releases.ubuntu.com/focal" target="_blank" rel="noopener noreferrer">Focal Fossa</a>)</li>
    <li>Wine (<a href="https://www.winehq.org" target="_blank" rel="noopener noreferrer">winehq.org</a>)</li>
    <li>Box86/Box64 by <a href="https://github.com/ptitSeb" target="_blank" rel="noopener noreferrer">ptitseb</a></li>
    <li>PRoot (<a href="https://proot-me.github.io" target="_blank" rel="noopener noreferrer">proot-me.github.io</a>)</li>
    <li>Mesa (Turnip/Zink/VirGL) (<a href="https://www.mesa3d.org" target="_blank" rel="noopener noreferrer">mesa3d.org</a>)</li>
    <li>DXVK (<a href="https://github.com/doitsujin/dxvk" target="_blank" rel="noopener noreferrer">github.com/doitsujin/dxvk</a>)</li>
    <li>VKD3D (<a href="https://gitlab.winehq.org/wine/vkd3d" target="_blank" rel="noopener noreferrer">gitlab.winehq.org/wine/vkd3d</a>)</li>
    <li>D8VK (<a href="https://github.com/AlpyneDreams/d8vk" target="_blank" rel="noopener noreferrer">github.com/AlpyneDreams/d8vk</a>)</li>
    <li>CNC DDraw (<a href="https://github.com/FunkyFr3sh/cnc-ddraw" target="_blank" rel="noopener noreferrer">github.com/FunkyFr3sh/cnc-ddraw</a>)</li>
    <li>Reshade (<a href="https://reshade.me/" target="_blank" rel="noopener noreferrer">reshade.me</a>)</li>
  </ul>

  <h1>History</h1>
  <h2>Project Background</h2>
  <p>
  Between <strong>2022</strong> and <strong>2024</strong>, the lead developer of WinlatorXR
  focused extensively on advancing immersive emulation for standalone VR headsets.
  In 2022, he introduced <strong>PPSSPP VR</strong>, bringing stereoscopic 3D rendering
  and head tracking to classic handheld titles. In 2023, he revived the
  <strong>VirtualGoBoy</strong> emulator, making it working on newer Android versions.
  Continuing this trajectory in 2024, he contributed to <strong>CitraVR</strong>
  by implementing an immersive mode that significantly enhanced
  Nintendo 3DS emulation within VR environments. Together, these projects
  demonstrated a consistent effort to expand VR-native emulation and improve
  spatial presence across multiple platforms.
  </p>

  <p>
  After discovering the <strong>Winlator</strong> project, the developer immediately
  recognized its potential and initiated contact to explore the integration of
  <strong>OpenXR</strong> support. The objective was to enable standardized VR runtime
  compatibility and extend immersive capabilities within the Windows container
  environment. However, the original repository proved challenging for external open-source
  collaboration. Limited flexibility for community contributions led to the
  creation of multiple independent forks and mods of the project.
  These forks focused on experimentation, feature expansion, and improved
  integration paths, ultimately contributing to the growth and diversification
  of the ecosystem surrounding the project.
  </p>

  <h2>Project Evolution</h2>
  <p>
  Initially, there was no intention to create an independent fork or modification of WinlatorXR.
  The project existed as part of the official Winlator repository, with the goal of contributing
  VR functionality directly upstream. However, frequent Quest OS updates repeatedly broke
  compatibility, and the time required to implement hotfixes proved to be too long for a
  stable and reliable development cycle. Over time, it became clear that relying solely on
  the original repository structure was not a sustainable solution.
  </p>

  <p>
  The emergence of the GLIBC fork marked a significant turning point. This fork delivered
  a substantial performance improvement, and its maintainer — a Chinese student developer —
  quickly granted administrative access to the lead developer. This collaboration proved
  to be mutually beneficial and accelerated development. Unfortunately, the original
  maintainer later disappeared from the internet, leaving the project without consistent
  upstream updates or long-term maintenance.
  Meanwhile, Tobbe85 introduced a separate fork that added support for Pico headsets.
  This broadened hardware compatibility and brought increased visibility to the project.
  Around the same time, GmoLargey became heavily involved as a primary tester of early
  WinlatorXR builds, providing valuable feedback and helping refine stability and
  performance during critical development stages.
  </p>

  <p>
  In the summer of 2025, the release of Winlator Cmod/Bionic resolved long-standing
  issues related to Meta Quest drivers and unlocked compatibility with DirectX 9
  and newer titles. This development represented a major breakthrough. The lead
  developer merged these improvements together with Tobbe85’s work, effectively
  rebooting the project and establishing a stronger, more unified foundation for
  future WinlatorXR development.
  </p>
  <center><img src="img/winlatorxr_history.jpeg"></center>
</body>
</html>