IEEE VR-SEARIS 2014 Keynote - MiddleVR - Philosophy and architecture
•Descargar como PPT, PDF•
1 recomendación•2,060 vistas
MiddleVR is a generic VR plugin. SEARIS is the "Software engineering and architecture for realtime interactive systems" workshop for IEEEVR.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a IEEE VR-SEARIS 2014 Keynote - MiddleVR - Philosophy and architecture
Similar a IEEE VR-SEARIS 2014 Keynote - MiddleVR - Philosophy and architecture (20)
Último
Último (20)
IEEE VR-SEARIS 2014 Keynote - MiddleVR - Philosophy and architecture
- 1. Sébastien „Cb‟ Kuntz @Cb_VRGeek Philosophy and architecture SEARIS 2014
- 3. Plan • Introduction • Origin of MiddleVR • Goals • Demo • Philosophy & Architecture • Conclusion
- 4. (French railways) “Creating Virtual Reality Games: The Fundamentals” Founder & President Sébastien „Cb‟ Kuntz
- 7. FRENCH RAILWAYS - SNCF • Polhemus magnetic tracker, treadmill, 5DT Glove • C++ / OpenSceneGraph / VRPN / OpenAL
- 8. FRENCH RAILWAYS - SNCF
- 9. VIRTOOLS
- 10. VIRTOOLS VR PACK
- 12. • VR tools to simplify VR
- 13. Virtual reality Presence in a virtual world
- 14. Ridiculous If it‟s real VR, you probably look ridiculous !
- 15. • Build hardware To create and maintain presence, you need to ... • Build software • Build user experience
- 16. The challenges of creating a VR software
- 17. “VR is mainly a software problem” Jaron Lanier
- 18. Device management Physical device Driver Application
- 19. Device management Tracker 1 Driver Tracker 1 Application Tracker 2 Driver Tracker 2
- 23. Correct perspective (c) Johnny Lee
- 25. Stereoscopy
- 28. Graphics cards limitations • Number of outputs • Processing power
- 29. multiple graphics cards • Pro • More outputs • More processing power • Con • 3D engines are not optimized for multi-pipe
- 30. Cluster • Pro • More outputs • More processing power • Con • 3D engines don‟t support clustering
- 31. • No seams across displays require 3 layers of sync • 3D objects synchro (Scenelock) • New images display (Swaplock) • Left/Right eyes (Genlock) Cluster
- 32. Interactions • Many different 3D user interactions • Navigation • Selection • Manipulation • Draw • System control • etc.
- 33. Interactions are dependent on hardware
- 34. Menus
- 36. Deployment • Modify application to • Change drivers • Change displays • Change interactions
- 38. • Platform for creating interactive 3d applications • Widely used • 2.5 million registered developers
- 39. • High-quality rendering • Deferred renderer • Occlusion culling • Realtime shadows • Ambient occlusion • Light mapping
- 41. Unity 3D Features • Programming • C#, Javascript • Profiler • Physics • NVidia PhysX • Cloth • Soft/rigid bodies • Ragdolls • Cars 3D formats FBX, Collada, 3DS, OBJ… Audio engine Networking Terrain
- 42. Editor • Simple to use • Create your own tools inside Unity
- 43. Asset store • Buy / sell assets • 3D models • Textures • Shaders • Scripts • Editor plugins
- 44. Desktop
- 45. • Build hardware To create and maintain presence, you, the author, need to ... • Build software • Build user experience
- 48. Existing VR software • VRPN • OpenTracker • VRJuggler • Virtools • Worldviz • …
- 49. VRPN
- 50. VR Juggler
- 51. VIRTOOLS VR PACK
- 52. Worldviz Vizard • Based on OpenSceneGraph • Python
- 53. Worldviz Vizard
- 54. The need for better VR software tools • Hardware getting cheaper • But engineers are not getting cheaper • Need to be more efficient and spend less time creating apps • Democratization • VR developers are not all engineers anymore
- 55. Goals • Simplify VR • Simplify creation of VR applications • Simplify deployment of VR applications • Create new VR tools • Adapting existing 3D applications
- 56. What is ? • Generic VR plugin (C++ SDK) • Functionalities ○Manage input devices •3D trackers, keyboard, mouse, joystick ○Manage display •Viewports, cameras, stereoscopy, cluster ○High-level building-blocks ○Interactions ○Menu
- 57. Architecture MiddleVR (C++) Drivers OpenGL DirectX Network C# Wrapper GUI Unity Lua Wrapper Python Wrapper
- 63. Supported Devices • Via VRPN : • A.R.T • Vicon • Optitrack • Wiimote • Polhemus Fastrak Tracker, 3Space Tracker, Patriot Trackers, • Ascension Flock of Bird • Intersense IS600, IS900 • 3dTech HiBall-3000 Wide Area Tracker, • Advanced Realtime Tracking Gmbh DTrack Client, • World Viz Precision Position Tracker PPT 1.2, • Natural Point Optitrack Rigid Body Toolkit, • Phasespace optical tracking OWL, • ... • Native drivers • Oculus Rift • Leap Motion • Kinect (Microsoft SDK) • PNI SpacePoint Fusion • GameTrak • Razer Hydra • SpaceMouse • Motion Analysis (beta)
- 65. VR Camera • MiddleVR computes all the cameras‟ parameters automatically • Correct perspective • Scale 1
- 66. Stereoscopy • Active stereoscopy (OpenGL Quad-Buffer) • Which Unity can‟t natively handle • Passive stereoscopy
- 68. Simply configure your system
- 69. Navigations
- 70. Homography
- 71. Cluster & Multi-pipe • Scenelock • Swaplock • Genlock • Multi-pipe (soon)
- 72. Supported displays • Virtually any HMD • VR-Wall, Powerwall • Workbench, Holobench • HoloStage • CAVEs • 3D TVs • zSpace • Igloo Vision • …
- 73. Goals • Simplify creation of VR applications • Simplicity of adding VR into application • Simplicity of API • High-level tools • Interactions: Selection, manipulation, navigation, menus, GUIs
- 75. Driver 1
- 76. Driver 2
- 79. MiddleVR
- 80. Class reference
- 81. The value of Simplicity
- 82. The value of simplicity “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away” Antoine de St Exupery
- 83. The value of simplicity • For each feature you add • Test • Document • Support / maintain • Each feature costs !!
- 84. The value of simplicity • Huge value in simplicity ! • User side • Faster to learn, less to remember • Developer side • Faster to code • Easier maintain • Less bugs • Business side • Need less coders • More interesting features • Easy download / setup > Quickly validate on user‟s hardware ! • Easier support
- 85. API in simple english • Long discussions for naming of functions, classes, variables • Consistent api • SetNumButtons, SetButtonsNum, SetNbButtons > SetButtonsNb • French not good at english • Analog ? Digital ? Proxy ? • Use natural terms depending on device • Joystick->GetAxisValue() • Joystick->IsButtonPressed() • Keyboard->IsKeyPressed() • Why “Register” ? Why not “Add” ? • Why so complex, want to sound very clever ? • AddDevice, AddCamera, … • API in degrees, because more intuitive / simple to work with
- 86. Simplified API • Simple but complete API • Like legos • Rotate • Node3D->Rotate( Quat ) • Node3D->Rotate( Euler ) • Node3D->Rotate( Axis, Angle) • Quat( quat ), Quat( Euler ), Quat( Axis, Angle)
- 87. The value of simplicity “Simplicity is the ultimate sophistication” DaVinci
- 88. The value of simplicity • Design user interface for the 80% • Don‟t ruin the experience for the 20% • Simple things should be simple • Complex things can be complex • Put in an “advanced menu” • Don‟t let beauty of design ruin user experience • Like real life architects who want their design to be beautiful but totally unusable on a day to day • Example of Lego • Simple but complete
- 89. Optimizations • Engineers have a strong tendency to over-optimise • Complexifies code • Code must be above all readable • To avoid bugs • To maintain maintenability • If you want to optimise • First profile your code • Optimize what is *really* taking time • not what you *think* takes time
- 90. Empathy “The ability to understand and share the feelings of another.” Test with users
- 91. Hardware SDK are mostly too complicated
- 92. Drivers • Why not just a few simple functions with sensible defaults ? • Init() • Update() • GetValue() • Destroy() • And add more functions for more advanced
- 93. Documentation • User Guide • Class references
- 94. Goals • Simplify deployment of VR applications • GUI to configure VR systems • Dynamic reconfiguration of application • Ship with standard configurations • Abstractions
- 95. Deployment • Abstractions • Devices • 3D Nodes (User) • Interactions (soon)
- 96. Device management Driver Tracker 1 Application Driver Tracker 2
- 97. Device abstraction Virtual Device Application Driver Tracker 1 Driver Tracker 2
- 99. Display • Cameras & viewport created dynamically
- 100. User • Human-centric rather than techno-centric
- 101. Virtual Device 1 Hand (3D Node) Application Virtual Device 2 Inverse Kinematics User abstraction
- 102. Interactions • MiddleVR includes high-level interactions • Navigation • Selection • Manipulation • … More to come • Future: Interactions abstractions • Dynamically change interactions based on hardware
- 104. • How to create portable interactions ? • Navigations can be portable • Except collisions • Generalise what is generalisable • + Custom part for engine dependent • Collisions • Highlights • Gizmos Interactions
- 105. Menus • Ability to create menus and GUIs in HTML5 (soon)
- 107. Create immersive HTML5 GUI
- 108. C++ Reflexion • Also for configuration file • Cluster synchronisation • Accessing drivers specific information
- 109. Working with multiple 3D engines • Different coordinate systems • vrCoordinateSystem( Front, Up, Right ) • +/- X,Y,Z • OpenGL: • Front= -Z • Up = +Y • Right = +X • DirectX: • Front=+Z • Up=+Y • Right=+X
- 110. Working with multiple 3D engines • C++ • Compiling • STL, Boost • Strings (Wide strings) • Link issues • Different compilers (VC2005/2008/2010/2012) • Different languages • C wrapper • Lua wrapper
- 111. • Simplicity • Creation • Deployment • Adaptability • Hardware • Software
- 112. Our future • Games/apps development:
- 113. Conclusion
- 114. http://www.imin-vr.com/download Thank you ! Questions ? Sebastien.Kuntz@imin-vr.com @Cb_VRGeek @imin_vr