Jump to content

Oculus Connect 1: Difference between revisions

No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Event Infobox
{{Event Infobox
|image= [[File:oculus connect 1 logo1.jpg|400px]]
|image= [[File:oculus connect 1 logo1.jpg|350px]]
|Type= Developer Conference
|Type= Developer Conference
|Format= In-person (Keynotes, Sessions, Demos)
|Format= In-person (Keynotes, Sessions, Demos)
Line 13: Line 13:
|Winner= N/A
|Winner= N/A
|Location= Loews Hollywood Hotel, Los Angeles, California, United States
|Location= Loews Hollywood Hotel, Los Angeles, California, United States
|Dates= September 19–20, 2014 <ref name="oc1-dates-location">{{cite web |url=https://techcrunch.com/2014/07/10/oculus-vr-announces-oculus-connect-developer-conference-in-los-angeles-sept-19-20/ |title=Oculus VR Announces ‘Oculus Connect’ Developer Conference In Los Angeles Sept. 19-20 |author=Darrell Etherington |date=2014-07-10 |website=TechCrunch |access-date=2023-10-27}}</ref>
|Dates= September 19–20, 2014 <ref name="oc1-dates-location">{{cite web |url=https://www.theverge.com/tech/2014/7/7/5878449/oculus-connect-developer-conference |title=The Oculus Rift is getting its own developer conference |author=Colin Lecher |date=July 7, 2014 |website=The Verge |access-date=2025‑05‑03}}</ref>
|Attendants= Approximately 1,000 <ref name="oc1-attendance">{{cite web |url=https://www.roadtovr.com/oculus-connect-2014-keynote-live-blog-1030am-pst-friday-19th-september/ |title=Oculus Connect 2014 Keynote Live Blog – 10:30AM PST Friday 19th September |author=Ben Lang |date=2014-09-19 |website=Road to VR |access-date=2023-10-27}}</ref>
|Attendants= Approximately 1,000 <ref name="oc1-attendance">{{cite web |url=https://www.meta.com/blog/oculus-connect-2014/ |title=Oculus Connect 2014 |website=Meta Quest Blog |date=September 20, 2014 |access-date=2025‑05‑03}}</ref>
|Previous= None (Inaugural event)
|Previous= None (Inaugural event)
|Next= [[Oculus Connect 2]]
|Next= [[Oculus Connect 2]]
Line 31: Line 31:
Arguably the most significant reveal was the Crescent Bay [[headset]] prototype. Positioned as a major step beyond the DK2 and much closer to a potential consumer product, Crescent Bay featured several key improvements:
Arguably the most significant reveal was the Crescent Bay [[headset]] prototype. Positioned as a major step beyond the DK2 and much closer to a potential consumer product, Crescent Bay featured several key improvements:


Integrated Audio: High-quality, detachable headphones providing [[spatial audio]] ([[3D audio]]) were built directly into the headset, emphasizing the importance of sound for [[presence]]. <ref name="crescent-bay-audio">{{cite web |url=https://www.engadget.com/2014-09-19-oculus-rift-crescent-bay.html |title=Oculus Rift's new prototype has integrated audio and 360-degree head tracking |author=Joseph Volpe |date=2014-09-19 |website=Engadget |access-date=2023-10-27}}</ref>
Integrated Audio: High-quality, detachable headphones providing [[spatial audio]] ([[3D audio]]) were built directly into the headset, emphasizing the importance of sound for [[presence]]. <ref name="crescent-bay-audio">{{cite web |url=https://www.theverge.com/2014/9/20/6660901/oculus-announces-new-vr-headset-prototype-crescent-bay |title=Oculus announces new VR headset prototype: Crescent Bay |author=Adi Robertson |date=September 20, 2014 |website=The Verge |access-date=2025‑05‑03}}</ref>


360-Degree Positional Tracking: Expanded tracking volume compared to the DK2's front-facing system, enabled by [[LED]] markers on the back of the headset strap, allowing users to turn completely around while maintaining tracking. <ref name="crescent-bay-audio"/>
360-Degree Positional Tracking: Expanded tracking volume compared to the DK2's front-facing system, enabled by [[LED]] markers on the back of the headset strap, allowing users to turn completely around while maintaining tracking. <ref name="crescent-bay-audio"/>


Improved Optics and Display: Higher resolution (though specifics weren't officially disclosed, estimated near 1440p split between eyes) and higher [[refresh rate]] (90Hz) [[OLED]] panels compared to DK2, reducing motion blur and [[screen-door effect]]. <ref name="crescent-bay-display-refresh">{{cite web |url=https://arstechnica.com/gaming/2014/09/oculus-unveils-crescent-bay-prototype-with-90hz-refresh-higher-res/ |title=Oculus unveils Crescent Bay prototype with 90Hz refresh, higher res |author=Kyle Orland |date=2014-09-19 |website=Ars Technica |access-date=2023-10-27}}</ref>
Improved Optics and Display: Higher resolution (though specifics weren't officially disclosed, estimated near 1440p split between eyes) and higher [[refresh rate]] (90Hz) [[OLED]] panels compared to DK2, reducing motion blur and [[screen-door effect]]. <ref name="crescent-bay-display-refresh">{{cite web |url=https://www.wired.com/2014/09/oculus-crescent-bay-prototype/ |title=Oculus’ Mind‑Blowing New Prototype Is a Huge Step Toward Consumer VR |author=Tim Moynihan |date=September 20, 2014 |website=Wired |access-date=2025‑05‑03}}</ref>


Lighter and More Ergonomic Design: Significant reduction in weight and improved ergonomics for better comfort during use. <ref name="crescent-bay-audio"/>
Lighter and More Ergonomic Design: Significant reduction in weight and improved ergonomics for better comfort during use. <ref name="crescent-bay-audio"/>
Line 50: Line 50:
Oculus Mobile SDK: Announced alongside Gear VR, providing tools for developers to build mobile VR applications.
Oculus Mobile SDK: Announced alongside Gear VR, providing tools for developers to build mobile VR applications.


Low Persistence: [[John Carmack]] detailed the significant software optimizations required to achieve low-persistence display on mobile, crucial for reducing motion blur and nausea. <ref name="carmack-gearvr-optimizations">{{cite web |url=https://www.anandtech.com/show/8548/oculus-connect-developer-conference-live-blog |title=Oculus Connect Developer Conference Live Blog |author=Joshua Ho |date=2014-09-20 |website=AnandTech |access-date=2023-10-27}}</ref>
Low Persistence: [[John Carmack]] detailed the significant software optimizations required to achieve low-persistence display on mobile, crucial for reducing motion blur and nausea. <ref name="carmack-gearvr-optimizations">{{cite web |url=https://www.vox.com/2014/9/20/11631116/oculus-cto-john-carmack-samsung-let-us-bypass-android-development-hell |title=Oculus CTO John Carmack: Samsung Let Us Bypass Android “Development Hell” |author=Eric Johnson |date=September 20, 2014 |website=Vox |access-date=2025‑05‑03}}</ref>


=== Oculus Platform ===
=== Oculus Platform ===
Line 59: Line 59:
Oculus PC SDK 0.4: An updated [[SDK (Software Development Kit)]] for Rift developers, incorporating improvements and support for new features.
Oculus PC SDK 0.4: An updated [[SDK (Software Development Kit)]] for Rift developers, incorporating improvements and support for new features.


Developer Support: Emphasis on providing resources, documentation, and forums to aid developers. <ref name="oc1-platform">{{cite web |url=https://uploadvr.com/oculus-connect-1-retrospective/ |title=Oculus Connect 1 Retrospective: The Dawn of Modern VR Development |author=Jamie Feltham |date=2015-09-22 |website=UploadVR |access-date=2023-10-27}}</ref> (Note: Retrospective article referencing the event's focus)
Developer Support: Emphasis on providing resources, documentation, and forums to aid developers. <ref name="oc1-platform">{{cite web |url=https://techcrunch.com/2014/09/20/oculus-platform/ |title=The “Oculus Platform” Marketplace for Virtual Reality Apps Launches This Fall |author=Josh Constine |date=September 20, 2014 |website=TechCrunch |access-date=2025‑05‑03}}</ref>
(Note: Retrospective article referencing the event's focus)


=== Oculus Audio SDK ===
=== Oculus Audio SDK ===
Recognizing the critical role of audio in creating immersive VR, Oculus announced the Oculus Audio SDK. This specialized SDK was designed to help developers implement realistic spatial audio in their VR experiences, working closely with the integrated audio hardware demonstrated on the Crescent Bay prototype. <ref name="oc1-audio-sdk">{{cite web |url=https://developer.oculus.com/blog/introducing-the-oculus-audio-sdk/ |title=Introducing the Oculus Audio SDK |author=Brian Hook |date=2014-09-19 |website=Oculus Developer Blog |access-date=2023-10-27}}</ref>
Recognizing the critical role of audio in creating immersive VR, Oculus announced the Oculus Audio SDK. This specialized SDK was designed to help developers implement realistic spatial audio in their VR experiences, working closely with the integrated audio hardware demonstrated on the Crescent Bay prototype. <ref name="oc1-audio-sdk">{{cite web |url=https://theaudiospotlight.com/oculus-connect-introduction-audio-vr/ |title=Oculus Connect: Introduction to Audio in VR |website=The Audio Spotlight |date=September 2014 |access-date=2025‑05‑03}}</ref>


=== Partnerships ===
=== Partnerships ===
Line 69: Line 70:
[[Unity Technologies|Unity]]: Integration of Oculus SDK features directly into the Unity engine, simplifying development for a large portion of the VR developer community.
[[Unity Technologies|Unity]]: Integration of Oculus SDK features directly into the Unity engine, simplifying development for a large portion of the VR developer community.


[[Epic Games]]: Similar integration efforts with the [[Unreal Engine]], showcased powerfully through Epic's "Showdown" demo running on Crescent Bay. <ref name="unreal-showdown">{{cite web |url=https://www.unrealengine.com/en-US/blog/epic-games-unveils-showdown-cinematic-vr-demo |title=Epic Games Unveils ‘Showdown’ Cinematic VR Demo |author=Dana Cowley |date=2014-09-19 |website=Unreal Engine Blog |access-date=2023-10-27}}</ref>
[[Epic Games]]: Similar integration efforts with the [[Unreal Engine]], showcased powerfully through Epic's "Showdown" demo running on Crescent Bay. <ref name="unreal-showdown">{{cite web |url=https://www.unrealengine.com/marketplace/en-US/product/showdown-demo |title=Showdown VR Demo |website=Unreal Engine Marketplace |publisher=Epic Games |date=September 2014 |access-date=2025‑05‑03}}</ref>


== Keynotes and Sessions ==
== Keynotes and Sessions ==