講演詳細

Session Detail

OpenXR Update / OpenXR アップデート情報、Interaction in OpenXR / OpenXRにおけるインタラクション、Future-Proof XR / 将来を見据えたXR

講演情報

資料公開予定 公開予定
スクリーンショット撮影可否
SNS投稿可否

講演概要

このセッションは3つのパートに分かれています。

1. OpenXR Update:The first part of this session will provide an overview of the OpenXR API; its development, usages, adoption, and extensibility and why application developers and hardware makers should be moving to this new standard.

このセッションの最初の部分では、OpenXR APIの概要をご紹介します。主に、その開発自体について、用途、採用事例、拡張性などです。また、XR関連のアプリケーション開発者とハードウェアメーカーの皆様がこの規格を利用するメリットについてもご紹介します。

2. Interaction in OpenXR : An important part of the OpenXR hardware independence is how interactions are modeled and handled: as "actions" rather than hardware state. We will discuss the basic handles involved in interaction, how to model interaction using action sets, actions, and interaction profiles, and walk through the actions and suggested bindings of the hello_xr sample app.

OpenXRがハードウェアに非依存であることに関する重要な部分は、ハードウェアの状態ではなく「アクション」としてインタラクションがどのようにモデル化および処理されるか、という部分になります。このセッションではインタラクションに関連する基本的なハンドル、アクションセット、アクション、インタラクションプロファイルを使用してインタラクションをモデル化する方法について説明し、hello_xrサンプルアプリのアクションと推奨されるバインディングについて紹介します。

3. Future-Proof XR : The OpenXR API allows you to write XR apps that target many different systems, even those that do not exist yet! I order to take advantage of this capability and achieve maximum device compatibility, the API must used correctly. This talk will take you through some of those rules and identify possible pitfalls to avoid while developing using OpenXR.

OpenXR APIを使用すればさまざまなシステムを対象にしてXRアプリを作成することが可能です(まだ開発中の存在しないシステムであっても)。この機能を利用してデバイスの互換性を最大限に高めるには、APIを正しく使用しなければなりません。この講演を聞けば、これらのルールのいくつかを紹介することで、OpenXRを使用して開発する際に陥りがちな落とし穴を避けれるようになります。

講演者詳細

  • Brent E. Insko

    Brent E. Insko

    Chair of the Khronos OpenXR Working Group and lead XR architect at Intel, Khronos Group

    Brent E. Insko , Intel Corp. (Intel Corporation, www.intel.com) Homepage: https://www.linkedin.com/in/brent-insko-a553596/ Personal profile: Chair of the Khronos OpenXR Working Group and lead XR architect at Intel. He received his PhD in Virtual Reality from the University of North Carolina at Chapel Hill under Frederick P. Brooks Jr. in 2001. He has previously worked on graphics hardware for 15 years and contributed to the development of the OpenGL, OpenGL ES, and Vulkan graphics APIs. He has been refocused on AR/VR for the last 4 years. He has spoken at VRDC, GDC, and published in SIGGRAPH.

  • Ryan A. Pavlik

    Ryan A. Pavlik

    Principal Software Engineer at Collabora in the XR team, Khronos Group

    Principal Software Engineer at Collabora in the XR team, working on XR-related client projects as well as runtime research and development. He serves as the Specification Editor of the Khronos OpenXR Working Group since April of 2019, and has participated in that working group since its formation in 2017. He has previously worked on virtual reality runtimes and technology at Sensics, and on virtual reality software frameworks, virtual assembly for engineering, natural interaction techniques, and haptic force-feedback at the Virtual Reality Applications Center at Iowa State University. He earned his PhD in computer science and human-computer interaction at Iowa State University.

  • Lachlan Ford

    Lachlan Ford

    Software Engineer at Microsoft on the Mixed Reality team and contributor to multiple standardization efforts including OpenXR and WebXR, Khronos Group

    Lachlan Ford , Microsoft (Microsoft Corporation) Personal profile: Software Engineer at Microsoft on the Mixed Reality team and contributor to multiple standardization efforts including OpenXR and WebXR. He graduated from UNSW in 2015 with a bachelors of Computer Science and worked at the Bill and Melinda Gates foundation funded education technology startup SmartSparrow from 2012, and Microsoft since 2016. He is interested in exploring the limits of technology as well as leveraging standards to combinatorially expand the XR ecosystem.