DOCSLIB.ORG

Openxr 1.0 Reference Guide Page 1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openxr 1.0 Reference Guide Page 1 OpenXR 1.0 Reference Guide Page 1 OpenXR™ is a cross-platform API that enables a continuum of real-and-virtual combined environments generated by computers through human-machine interaction and is inclusive of the technologies associated with virtual reality, augmented reality, and mixed reality. It is the interface between an application and an in-process or out-of-process XR runtime that may handle frame composition, peripheral management, and more. Color-coded names as follows: function names and structure names. [n.n.n] Indicates sections and text in the OpenXR 1.0 specification. Specification and additional resources at khronos.org/openxr £ Indicates content that pertains to an extension. OpenXR API Overview A high level overview of a typical OpenXR application including the order of function calls, creation of objects, session state changes, and the rendering loop. OpenXR Action System Concepts [11.1] Create action and action spaces Set up interaction profile bindings Sync and get action states xrCreateActionSet xrSetInteractionProfileSuggestedBindings xrSyncActions name = "gameplay" /interaction_profiles/oculus/touch_controller session activeActionSets = { "gameplay", ...} xrCreateAction "teleport": /user/hand/right/input/a/click actionSet="gameplay" "teleport_ray": /user/hand/right/input/aim/pose xrGetActionStateBoolean ("teleport_ray") name = “teleport” if (state.currentState) // button is pressed /interaction_profiles/htc/vive_controller type = XR_INPUT_ACTION_TYPE_BOOLEAN { actionSet="gameplay" "teleport": /user/hand/right/input/trackpad/click "teleport_ray": /user/hand/right/input/aim/pose xrLocateSpace (teleport_ray_space, name = "teleport_ray" stage_reference_space); type = XR_INPUT_ACTION_TYPE_POSE } xrCreateActionSpace xrAttachSessionActionSets action = "teleport_ray" session actionSets = { "gameplay", ... } OpenXR separates application actions such as Interaction profiles identify a collection of buttons and Syncing actions selects the active action Move, Jump, and Teleport from the input Trigger, other input sources in a physical arrangement to allow set(s) to receive input, and updates the action Thumbstick, Button, etc. Actions are grouped into applications and runtimes to coordinate action-to-input states. Most input data is accessible with application-defined action sets that correspond mapping. Runtimes bind actions to input devices based on xrGetActionState* functions. Pose actions to usage context (menu, gameplay, etc.). This application-supplied suggested bindings and other runtime- for tracked objects use "action spaces" and simplifies support for different or future input specific sources. This permits developers to customize to xrLocateSpace instead, for use like reference devices and maximizes user accessibility. hardware they have tested, while making it possible to run spaces. on other hardware as supported by runtimes. ©2019 Khronos Group - Rev. 0719 www.khronos.org/openxr OpenXR 1.0 Reference Guide Page 2 OpenXR Fundamentals Buffer size parameters [2.11] XrResult return codes [2.8] Some functions refer to input/output buffers with parameters API commands return values of type XrResult. Negative values Traversing pointer chains [2.7.7] of the following form: are error codes, while non-negative (≥0) are success codes. typedef struct XrBaseInStructure { XrResult xrFunction(uint32_t elementCapacityInput, XrStructureType type; uint32_t* elementCountOutput, float* elements); Success codes const struct XrBaseInStructure* next; XR_SUCCESS XR_TIMEOUT_EXPIRED } XrBaseInStructure; Two-call idiom for buffer size parameters XR_SESSION_LOSS_PENDING XR_EVENT_UNAVAILABLE First call xrFunction() with a valid elementCountOutput pointer typedef struct XrBaseOutStructure { XR_SESSION_NOT_FOCUSED XR_FRAME_DISCARDED XrStructureType type; (always required), elements = NULL, and elementCapacityInput struct XrBaseOutStructure* next; = 0 to get the number of elements in the buffer; allocate XR_SPACE_BOUNDS_UNAVAILABLE } XrBaseOutStructure; sufficient space, then call xrFunction() again with the allocated buffer's parameters. Error codes XR_ERROR_X where X may be: Macros for version and header control Graphics API header control [Appendix] ACTION_TYPE_MISMATCH Compile Time Symbol API ACTIONSET_NOT_ATTACHED Version numbers [2.1, Appendix] XR_USE_GRAPHICS_API_OPENGL OpenGL ACTIONSETS_ALREADY_ATTACHED typedef uint64_t XrVersion; XR_USE_GRAPHICS_API_OPENGL_ES OpenGL ES ANDROID_THREAD_SETTINGS_FAILURE_KHR Version numbers are encoded in 64 bits as follows: ANDROID_THREAD_SETTINGS_ID_INVALID_KHR XR_USE_GRAPHICS_API_VULKAN Vulkan bits 63-48: bits 47-32: bits 31-0: API_LAYER_NOT_PRESENT Major version Minor version Patch version XR_USE_GRAPHICS_API_D3D11 Direct3D 11 API_VERSION_UNSUPPORTED XR_USE_GRAPHICS_API_D3D12 Direct3D 12 Version macros CALL_ORDER_INVALID #define XR_CURRENT_API_VERSION ENVIRONMENT_BLEND_MODE_UNSUPPORTED Window system header control [Appendix] XR_MAKE_VERSION(1, 0, 0) EXTENSION_NOT_PRESENT Compile Time Symbol Window System #define XR_MAKE_VERSION(major, minor, patch) FEATURE_UNSUPPORTED ((((major) & 0xffffULL) << 48) | XR_USE_PLATFORM_WIN32 Microsoft Windows FILE_ACCESS_ERROR (((minor) & 0xffffULL) << 32) | ((patch) & 0xffffffffULL)) XR_USE_PLATFORM_XLIB X Window System Xlib FILE_CONTENTS_INVALID #define XR_VERSION_MAJOR(version) XR_USE_PLATFORM_XCB X Window System Xcb FORM_FACTOR_UNAVAILABLE (uint16_t) (((uint64_t)(version) >> 48) & 0xffffULL) XR_USE_PLATFORM_WAYLAND Wayland FORM_FACTOR_UNSUPPORTED #define XR_VERSION_MINOR(version) XR_USE_PLATFORM_ANDROID Android Native FUNCTION_UNSUPPORTED (uint16_t) (((uint64_t)(version) >> 32) & 0xffffULL) GRAPHICS_DEVICE_INVALID #define XR_VERSION_PATCH(version) HANDLE_INVALID (uint32_t) ((uint64_t)(version) & 0xffffffffULL) Data types INDEX_OUT_OF_RANGE Color [2.14] INITIALIZATION_FAILED Color components are linear (e.g., not sRGB), not alpha- INSTANCE_LOST premultiplied, in the range 0.0..1.0. LAYER_INVALID Threading behavior [2.3] typedef struct XrColor4f { OpenXR functions generally support being called from multiple float r; float g; float b; float a; LAYER_LIMIT_EXCEEDED threads with a few exceptions: } XrColor4f; LIMIT_REACHED • The handle parameter and any child handles that will LOCALIZED_NAME_DUPLICATED be destroyed by a destroy function must be externally Coordinate system [2.15] synchronized. LOCALIZED_NAME_INVALID OpenXR uses a Cartesian right- • The instance parameter and any child handles in handed coordinate system with an NAME_DUPLICATED xrDestroyInstance x, y, and z axis. NAME_INVALID • The session parameter and any child handles in xrDestroySession Points and directions can be OUT_OF_MEMORY • The space parameter and any child handles in represented using the following PATH_COUNT_EXCEEDED xrDestroySpace struct types with the following PATH_FORMAT_INVALID members: • The swapchain parameter and any child handles in PATH_INVALID xrDestroySwapchain Members x, y for distance in meters or PATH_UNSUPPORTED • The actionSet parameter and any child handles in XrVector2f 2D direction xrDestroyActionSet Members x, y, z for distance in meters, POSE_INVALID • The action parameter and any child handles in XrVector3f or velocity or angular velocity REFERENCE_SPACE_UNSUPPORTED xrDestroyAction RUNTIME_FAILURE • Calls to xrWaitFrame for a given XrSession must be XrVector4f Members x, y, z, w for a 4D vector externally synchronized. construct SESSION_LOST Members x, y, z, w representing 3D SESSION_NOT_READY XrQuaternionf orientation as a unit quaternion XR_KHR_android_thread_settings[12.3] SESSION_NOT_RUNNING Members orientation as a unit £ If enabled, this extension allows the application to specify XrPosef SESSION_NOT_STOPPING the Android thread type. quaternion and position in meters SESSION_RUNNING XrResult xrSetAndroidApplicationThreadKHR( typedef struct XrVector2f { SIZE_INSUFFICIENT XrSession session, float x; XrAndroidThreadTypeKHR threadType, float y; SWAPCHAIN_FORMAT_UNSUPPORTED uint32_t threadId); } XrVector2f; SWAPCHAIN_RECT_INVALID threadType: XR_ANDROID_THREAD_TYPE_X_KHR typedef struct XrVector3f { SYSTEM_INVALID where X may be: float x; TIME_INVALID APPLICATION_MAIN, APPLICATION_WORKER, float y; VALIDATION_FAILURE RENDERER_MAIN, RENDERER_WORKER float z; } XrVector3f; VIEW_CONFIGURATION_TYPE_UNSUPPORTED typedef struct XrVector4f { £ XR_KHR_android_thread_settings Time float x; This extension enables the following additional error codes: float y; XR_ERROR_ANDROID_THREAD_SETTINGS_ID_INVALID_KHR float z; XrTime [2.12.1] XR_ERROR_ANDROID_THREAD_SETTINGS_FAILURE_KHR A 64-bit integer representing a time relative to a runtime- float w; dependent epoch. All simultaneous applications use the same } XrVector4f; epoch. typedef struct XrPosef { Convenience macros [2.8.3] XrQuaternionf orientation;; XrDuration [2.13] XrVector3f position; #define XR_SUCCEEDED(result) ((result) >= 0) A 64-bit signed integer representing a duration; the difference } XrPosef; XR_SUCCEEDED is true for non-negative codes. between two XrTime values. typedef struct XrQuaternionf { #define XR_FAILED(result) ((result) < 0) Special values: float x; XR_FAILED is true for negative codes. #define XR_NO_DURATION 0 float y; float z; #define XR_UNQUALIFIED_SUCCESS(result) ((result) == 0) #define XR_INFINITE_DURATION 0x7fffffffffffffffLL float w; XR_UNQUALIFIED_SUCCESS is true for 0 (XR_SUCCESS) only. } XrQuaternionf; ©2019 Khronos Group - Rev. 0719 www.khronos.org/openxr OpenXR 1.0 Reference Guide Page 3 Instance lifecycle Command function pointers [3.2] £ XR_KHR_android_create_instance [12.1] XrResult
Load more

Recommended publications
  • GLSL 4.50 Spec
    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Implementing FPGA Design with the Opencl Standard
    Implementing FPGA Design with the OpenCL Standard WP-01173-3.0 White Paper Utilizing the Khronos Group’s OpenCL™ standard on an FPGA may offer significantly higher performance and at much lower power than is available today from hardware architectures such as CPUs, graphics processing units (GPUs), and digital signal processing (DSP) units. In addition, an FPGA-based heterogeneous system (CPU + FPGA) using the OpenCL standard has a significant time-to-market advantage compared to traditional FPGA development using lower level hardware description languages (HDLs) such as Verilog or VHDL. 1 OpenCL and the OpenCL logo are trademarks of Apple Inc. used by permission by Khronos. Introduction The initial era of programmable technologies contained two different extremes of programmability. As illustrated in Figure 1, one extreme was represented by single core CPU and digital signal processing (DSP) units. These devices were programmable using software consisting of a list of instructions to be executed. These instructions were created in a manner that was conceptually sequential to the programmer, although an advanced processor could reorder instructions to extract instruction-level parallelism from these sequential programs at run time. In contrast, the other extreme of programmable technology was represented by the FPGA. These devices are programmed by creating configurable hardware circuits, which execute completely in parallel. A designer using an FPGA is essentially creating a massively- fine-grained parallel application. For many years, these extremes coexisted with each type of programmability being applied to different application domains. However, recent trends in technology scaling have favored technologies that are both programmable and parallel. Figure 1.
    [Show full text]
  • Khronos Template 2015
    Ecosystem Overview Neil Trevett | Khronos President NVIDIA Vice President Developer Ecosystem [email protected] | @neilt3d © Copyright Khronos Group 2016 - Page 1 Khronos Mission Software Silicon Khronos is an Industry Consortium of over 100 companies creating royalty-free, open standard APIs to enable software to access hardware acceleration for graphics, parallel compute and vision © Copyright Khronos Group 2016 - Page 2 http://accelerateyourworld.org/ © Copyright Khronos Group 2016 - Page 3 Vision Pipeline Challenges and Opportunities Growing Camera Diversity Diverse Vision Processors Sensor Proliferation 22 Flexible sensor and camera Use efficient acceleration to Combine vision output control to GENERATE PROCESS with other sensor data an image stream the image stream on device © Copyright Khronos Group 2016 - Page 4 OpenVX – Low Power Vision Acceleration • Higher level abstraction API - Targeted at real-time mobile and embedded platforms • Performance portability across diverse architectures - Multi-core CPUs, GPUs, DSPs and DSP arrays, ISPs, Dedicated hardware… • Extends portable vision acceleration to very low power domains - Doesn’t require high-power CPU/GPU Complex - Lower precision requirements than OpenCL - Low-power host can setup and manage frame-rate graph Vision Engine Middleware Application X100 Dedicated Vision Processing Hardware Efficiency Vision DSPs X10 GPU Compute Accelerator Multi-core Accelerator Power Efficiency Power X1 CPU Accelerator Computation Flexibility © Copyright Khronos Group 2016 - Page 5 OpenVX Graphs
    [Show full text]
  • Augmented Reality and Its Aspects: a Case Study for Heating Systems
    Augmented Reality and its aspects: a case study for heating systems. Lucas Cavalcanti Viveiros Dissertation presented to the School of Technology and Management of Bragança to obtain a Master’s Degree in Information Systems. Under the double diploma course with the Federal Technological University of Paraná Work oriented by: Prof. Paulo Jorge Teixeira Matos Prof. Jorge Aikes Junior Bragança 2018-2019 ii Augmented Reality and its aspects: a case study for heating systems. Lucas Cavalcanti Viveiros Dissertation presented to the School of Technology and Management of Bragança to obtain a Master’s Degree in Information Systems. Under the double diploma course with the Federal Technological University of Paraná Work oriented by: Prof. Paulo Jorge Teixeira Matos Prof. Jorge Aikes Junior Bragança 2018-2019 iv Dedication I dedicate this work to my friends and my family, especially to my parents Tadeu José Viveiros and Vera Neide Cavalcanti, who have always supported me to continue my stud- ies, despite the physical distance has been a demand factor from the beginning of the studies by the change of state and country. v Acknowledgment First of all, I thank God for the opportunity. All the teachers who helped me throughout my journey. Especially, the mentors Paulo Matos and Jorge Aikes Junior, who not only provided the necessary support but also the opportunity to explore a recent area that is still under development. Moreover, the professors Paulo Leitão and Leonel Deusdado from CeDRI’s laboratory for allowing me to make use of the HoloLens device from Microsoft. vi Abstract Thanks to the advances of technology in various domains, and the mixing between real and virtual worlds.
    [Show full text]
  • Khronos Native Platform Graphics Interface (EGL Version 1.4 - April 6, 2011)
    Khronos Native Platform Graphics Interface (EGL Version 1.4 - April 6, 2011) Editor: Jon Leech 2 Copyright (c) 2002-2011 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, repub- lished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re- formatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions. Khronos Group makes no, and expressly disclaims any, representations or war- ranties, express or implied, regarding this specification, including, without limita- tion, any implied warranties of merchantability or fitness for a particular purpose or non-infringement of any intellectual property.
    [Show full text]
  • The Openvx™ Specification
    The OpenVX™ Specification Version 1.0.1 Document Revision: r31169 Generated on Wed May 13 2015 08:41:43 Khronos Vision Working Group Editor: Susheel Gautam Editor: Erik Rainey Copyright ©2014 The Khronos Group Inc. i Copyright ©2014 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specifica- tion for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re-formatted AS LONG AS the contents of the specifi- cation are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions.
    [Show full text]
  • SYCL – Introduction and Hands-On
    SYCL – Introduction and Hands-on Thomas Applencourt + people on next slide - [email protected] Argonne Leadership Computing Facility Argonne National Laboratory 9700 S. Cass Ave Argonne, IL 60349 Book Keeping Get the example and the presentation: 1 git clone https://github.com/alcf-perfengr/sycltrain 2 cd sycltrain/presentation/2020_07_30_ATPESC People who are here to help: • Collen Bertoni - [email protected] • Brian Homerding - [email protected] • Nevin ”:)” Liber [email protected] • Ben Odom - [email protected] • Dan Petre - [email protected]) 1/17 Table of contents 1. Introduction 2. Theory 3. Hands-on 4. Conclusion 2/17 Introduction What programming model to use to target GPU? • OpenMP (pragma based) • Cuda (proprietary) • Hip (low level) • OpenCL (low level) • Kokkos, RAJA, OCCA (high level, abstraction layer, academic projects) 3/17 What is SYCL™?1 1. Target C++ programmers (template, lambda) 1.1 No language extension 1.2 No pragmas 1.3 No attribute 2. Borrow lot of concept from battle tested OpenCL (platform, device, work-group, range) 3. Single Source (two compilations passes) 4. High level data-transfer 5. SYCL is a Specification developed by the Khronos Group (OpenCL, SPIR, Vulkan, OpenGL) 1SYCL Doesn’t mean ”Someone You Couldn’t Love”. Sadly. 4/17 SYCL Implementations 2 2Credit: Khronos groups (https://www.khronos.org/sycl/) 5/17 Goal of this presentation 1. Give you a feel of SYCL 2. Go through code examples (and make you do some homework) 3. Teach you enough so that can search for the rest if you interested 4. Question are welcomed! 3 3Please just talk, or use slack 6/17 Theory A picture is worth a thousand words4 4and this is a UML diagram so maybe more! 7/17 Memory management: SYCL innovation 1.
    [Show full text]
  • Building the Metaverse One Open Standard at a Time
    Building the Metaverse One Open Standard at a Time Khronos APIs and 3D Asset Formats for XR Neil Trevett Khronos President NVIDIA VP Developer Ecosystems [email protected]| @neilt3d April 2020 © Khronos® Group 2020 This work is licensed under a Creative Commons Attribution 4.0 International License © The Khronos® Group Inc. 2020 - Page 1 Khronos Connects Software to Silicon Open interoperability standards to enable software to effectively harness the power of multiprocessors and accelerator silicon 3D graphics, XR, parallel programming, vision acceleration and machine learning Non-profit, member-driven standards-defining industry consortium Open to any interested company All Khronos standards are royalty-free Well-defined IP Framework protects participant’s intellectual property >150 Members ~ 40% US, 30% Europe, 30% Asia This work is licensed under a Creative Commons Attribution 4.0 International License © The Khronos® Group Inc. 2020 - Page 2 Khronos Active Initiatives 3D Graphics 3D Assets Portable XR Parallel Computation Desktop, Mobile, Web Authoring Augmented and Vision, Inferencing, Machine Embedded and Safety Critical and Delivery Virtual Reality Learning Guidelines for creating APIs to streamline system safety certification This work is licensed under a Creative Commons Attribution 4.0 International License © The Khronos® Group Inc. 2020 - Page 3 Pervasive Vulkan Desktop and Mobile GPUs http://vulkan.gpuinfo.org/ Platforms Apple Desktop Android (via porting Media Players Consoles (Android 7.0+) layers) (Vulkan 1.1 required on Android Q) Virtual Reality Cloud Services Game Streaming Embedded Engines Croteam Serious Engine Note: The version of Vulkan available will depend on platform and vendor This work is licensed under a Creative Commons Attribution 4.0 International License © The Khronos® Group Inc.
    [Show full text]
  • Opencl on The
    Introduction to OpenCL Cliff Woolley, NVIDIA Developer Technology Group Welcome to the OpenCL Tutorial! . OpenCL Platform Model . OpenCL Execution Model . Mapping the Execution Model onto the Platform Model . Introduction to OpenCL Programming . Additional Information and Resources OpenCL is a trademark of Apple, Inc. Design Goals of OpenCL . Use all computational resources in the system — CPUs, GPUs and other processors as peers . Efficient parallel programming model — Based on C99 — Data- and task- parallel computational model — Abstract the specifics of underlying hardware — Specify accuracy of floating-point computations . Desktop and Handheld Profiles © Copyright Khronos Group, 2010 OPENCL PLATFORM MODEL It’s a Heterogeneous World . A modern platform includes: – One or more CPUs CPU – One or more GPUs CPU – Optional accelerators (e.g., DSPs) GPU GMCH DRAM ICH GMCH = graphics memory control hub ICH = Input/output control hub © Copyright Khronos Group, 2010 OpenCL Platform Model Computational Resources … … … … … …… Host … Processing …… Element … … Compute Device Compute Unit OpenCL Platform Model Computational Resources … … … … … …… Host … Processing …… Element … … Compute Device Compute Unit OpenCL Platform Model on CUDA Compute Architecture … CUDA CPU … Streaming … Processor … … …… Host … Processing …… Element … … Compute Device Compute Unit CUDA CUDA-Enabled Streaming GPU Multiprocessor Anatomy of an OpenCL Application OpenCL Application Host Code Device Code • Written in C/C++ • Written in OpenCL C • Executes on the host • Executes on the device … … … … … …… Host … Compute …… Devices … … Host code sends commands to the Devices: … to transfer data between host memory and device memories … to execute device code Anatomy of an OpenCL Application . Serial code executes in a Host (CPU) thread . Parallel code executes in many Device (GPU) threads across multiple processing elements OpenCL Application Host = CPU Serial code Device = GPU Parallel code … Host = CPU Serial code Device = GPU Parallel code ..
    [Show full text]
  • Conference Booklet
    30th Oct - 1st Nov CONFERENCE BOOKLET 1 2 3 INTRO REBOOT DEVELOP RED | 2019 y Always Outnumbered, Never Outgunned Warmest welcome to first ever Reboot Develop it! And we are here to stay. Our ambition through Red conference. Welcome to breathtaking Banff the next few years is to turn Reboot Develop National Park and welcome to iconic Fairmont Red not just in one the best and biggest annual Banff Springs. It all feels a bit like history repeating games industry and game developers conferences to me. When we were starting our European older in Canada and North America, but in the world! sister, Reboot Develop Blue conference, everybody We are committed to stay at this beautiful venue was full of doubts on why somebody would ever and in this incredible nature and astonishing choose a beautiful yet a bit remote place to host surroundings for the next few forthcoming years one of the biggest worldwide gatherings of the and make it THE annual key gathering spot of the international games industry. In the end, it turned international games industry. We will need all of into one of the biggest and highest-rated games your help and support on the way! industry conferences in the world. And here we are yet again at the beginning, in one of the most Thank you from the bottom of the heart for all beautiful and serene places on Earth, at one of the the support shown so far, and even more for the most unique and luxurious venues as well, and in forthcoming one! the company of some of the greatest minds that the games industry has to offer! _Damir Durovic
    [Show full text]
  • Portable VR with Khronos Openxr
    Portable VR with Khronos OpenXR Kaye Mason, Nick Whiting, Rémi Arnaud, Brad Grantham July 2017 © Copyright Khronos Group 2016 - Page 1 Outline for the Session • Problem, Solution • Panelist Introductions • Technical Issues • Audience Questions • Lightning Round • How to Join • Party! © Copyright Khronos Group 2016 - Page 2 Problem Without a cross-platform standard, VR applications, games and engines must port to each vendors’ APIs. In turn, this means that each VR device can only run the apps that have been ported to its SDK. The result is high development costs and confused customers – limiting market growth. © Copyright Khronos Group 2016 - Page 3 Solution The cross-platform VR standard eliminates industry fragmentation by enabling applications to be written once to run on any VR system, and to access VR devices integrated into those VR systems to be used by applications. © Copyright Khronos Group 2016 - Page 4 Architecture OpenXR defines two levels of API interfaces that a VR platform’s runtime can use to access the OpenXR ecosystem. Apps and engines use standardized interfaces to interrogate and drive devices. Devices can self- integrate to a standardized driver interface. Standardized hardware/software interfaces reduce fragmentation while leaving implementation details open to encourage industry innovation. © Copyright Khronos Group 2016 - Page 5 OpenXR Participant Companies © Copyright Khronos Group 2016 - Page 6 Panelist Introduction • Kaye Mason Dr. Kaye Mason is a senior software engineer at Google and the API Lead for Google Daydream, as well as working on graphics and distortion. She is also the Specification Editor for the Khronos OpenXR standard. Kaye has a PhD in Computer Science from research focused on using AIs to do non- photorealistic rendering.
    [Show full text]
  • The Opengl ES Shading Language
    The OpenGL ES® Shading Language Language Version: 3.20 Document Revision: 12 246 JuneAugust 2015 Editor: Robert J. Simpson, Qualcomm OpenGL GLSL editor: John Kessenich, LunarG GLSL version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost 1 Copyright (c) 2013-2015 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]