# Haxe solution for WebXR

**URL:** <https://community.haxe.org/t/haxe-solution-for-webxr/2520>\
**Category:** Haxe\
**Created:** [June 15, 2020, 7:42pm UTC](https://community.haxe.org/t/haxe-solution-for-webxr/2520 "2020-06-15T19:42:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Confidant](https://community.haxe.org/user_avatar/community.haxe.org/confidant/32/63_2.png) [@Confidant](https://community.haxe.org/u/Confidant)\
**Post date:** [June 15, 2020, 7:42pm UTC](https://community.haxe.org/t/haxe-solution-for-webxr/2520/1 "2020-06-15T19:42:24Z")

</div>

I am doing a bit of reading about [WebXR](https://immersiveweb.dev/), the successor to WebVR, and I’m wondering what tools a Haxe developer should start with to get into it. I am aware of externs/libraries which allow Haxe to link to BabylonJS, Three.js, and Unity, which are all [recommended engines](https://immersiveweb.dev/#babylon.js) for WebXR. As a Haxe user I would want to cover as many targets as possible, so ending up on Babylon Native or Unity seem to be possible scenarios. I currently have my head in Away3D but that engine and community seems to be [stalled](https://github.com/openfl/away3d), [splintered](https://github.com/awayjs), and/or [abandoned](http://away3d.com/) depending on where you look. Are there more Haxe-based solutions which are better candidates now or in the future? Are Armory or Heaps anywhere close? Anything else brewing out there?

---

<div class="post-metadata">

**Author:** ![haxiomic](https://community.haxe.org/user_avatar/community.haxe.org/haxiomic/32/75_2.png) [@haxiomic](https://community.haxe.org/u/haxiomic)\
**Post date:** [June 15, 2020, 9:03pm UTC](https://community.haxe.org/t/haxe-solution-for-webxr/2520/2 "2020-06-15T21:03:02Z")

</div>

I’ve done web+native VR in the past (2016) by targeting three.js and using some V8 native-bindings to pass-through to OpenGL so you have a slim native app. Performance was good enough for our use case

I’d _probably_ do the same today in a pinch, although to save time today I’d just use something like chromium window for native and then switch to something slimmer if performance required it

I have a cross-platform haxe graphics engine brewing but will likely have to wait to 2021 before open sourcing it

---

<div class="post-metadata">

**Author:** ![RobDangerous](https://community.haxe.org/user_avatar/community.haxe.org/robdangerous/32/55_2.png) [@RobDangerous](https://community.haxe.org/u/RobDangerous)\
**Post date:** [June 16, 2020, 10:17am UTC](https://community.haxe.org/t/haxe-solution-for-webxr/2520/3 "2020-06-16T10:17:16Z")

</div>

Armory and Kha support WebVR but I’m not sure anyone did anything with it recently so it probably degressed a little. Updating that to WebXR shouldn’t be hard but I’m too lazy to calibrate the headset again - please send pull-requests.

---

<div class="post-metadata">

**Author:** ![Moykul](https://community.haxe.org/user_avatar/community.haxe.org/moykul/32/2212_2.png) [@Moykul](https://community.haxe.org/u/Moykul)\
**Post date:** [July 24, 2023, 6:01pm UTC](https://community.haxe.org/t/haxe-solution-for-webxr/2520/4 "2023-07-24T18:01:56Z")

</div>

… 3 years later, how hard would an update to webxr be? I will send a pull-request.
