WebGL Camp #3

Page 1

Reflections: WebGL Camp #3 @Google Mountain View (June 10th 2011) R. Ates Gursimsek (Roskilde University) ates@ruc.dk http://worlds.ruc.dk - Human Engines: Rachid el Guerrah, the president of the company, made a videoconference presentation, in which he introduced their 3-year old startup.‟ Human Engines‟ aims to deliver 3d content with high performance, provide hardware-centric optimizations for using content in tablets and mobile devices, and solve many performance and optimization issues. They also collaborate with Google to develop optimized WebGL demonstrations. - Tony Parisi is the co-inventor of VRML. His title was „A Brief History of 3D on the Web”, where he provided a “history lesson” which begins with the “Virtual Banana” he created with Mark Pesce in 1994. Chronologically, Parisi mentioned VRML and emergence of 3D models and hyperlinks in pages (1994); VRML97 and animation, scripting and interactivity in Netscape/IE browsers (1997); X3D, XML and skimming, programmable pipeline, multitexturing (2004), COLLADA as an exchange standard for 3D (2007); and finally, WebGL (2011). According to his “Parisiometer”, major potential threats to 3D on the Web are: immaturity & incompatibility & infighting & inaccessibility & ill timing. - Tim Johansson presented the Opera browser from Norway. Opera was released on March 2011 and the platform supports 3d through OpenGL. Currently, Opera supports only Windows, but Direct3D and Linux/Mac support is on its way. - Altered Qualia presented two inspirational projects: “three.js” and “RO.ME”. Three.js application creates procedural geometries (cube, plane etc) by using vertices (triangles and quads) and transform affordances. Lightweight 3D engine provides low quality but effective components that contain modeling, texturing, lighting/shader effects, etc. Most complex three.js project is RO.ME, which is an interactive movie built on user generated elements on social media. 3D and 2D animations & videos are used in the RO.ME project, and smaller videos with two optional resolutions and smaller refresh rates are afforded to overcome texture memory & bandwidth issues. Assets in RO.ME are mostly created by 3D Studio Maxand Maya, scene composition was made by Blender, and programming was mainly done by using Python. - Remi Arnaud (Screampoint) on REST 3D API: The major aim of REST 3D is getting data from the server onto the browser. Representational State Transfer (REST) is a system architecture, not a file standard. Most web interfaces put humans in the loop (to organize and modify the archives) and a 3D software (or a viewer) for accessing the 3D assets (i.e. Turbosquid) . The REST 3D API proposes affordances for storing, collaborative browsing and viewing of models by providing a URL link to the scene. In other words; “it‟s a WIKI for 3D”! - Vangelis Kokkevis presented the version of Google Body Browser and the funny “Google Cow” (made as an April‟s Fool trick) Kokkevis calls the body Browser as “Google Earth of human body”. It is possible to zoom in & out with varying levels of detail inside the body, select particular organs


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.
WebGL Camp #3 by Ates Gursimsek - Issuu