Last week, I mentioned the Universal GameDev Challenge presented from Microsoft, Unity, Intel and Universal Studios. Like I mentioned last week, the Back to the Future intellectual property that can be used in the contest really got my attention.
It reminded me about a 3D experience I was able to have a peek into Hill Valley through a web browser. I saw it about the time that WebGL was coming out.
Well, I started digging into WebGL and WebVR a little bit and came across the demo on the Babylon.js site.
You can watch this week’s video where I show Hill Valley VR running through Edge on the Windows Mixed Reality device.
I mention it in the video, but I’ll say it here as well… The contest is for Windows 10 Universal games, not for WebVR. I just didn’t want there to be any confusion. It is the Universal GameDev challenge because it is running as a Universal Windows app and you get to utilize Universal Studio’s IP… see what they did there?
The Unity project includes spatial mapping along with a custom spatial mapping shader. It includes speech recognition and storing and retrieving world anchors. The CSharpSynth code has been adapted to work with Unity and UWP apps in particular so that MIDI files can be played. Regular audio clips are played. The Mecanim state machine was used to a great degree to animate the text and the candy boxes.
This simple game has a solid code base that should be beneficial to anyone looking to do Holographic development using Unity. In fact, it should be beneficial to anyone interested in Unity development regardless if it is mixed reality or not.
I hope you grab the code and enjoy using it. If you have questions leave me a comment and I’ll do my best to get you an answer as time allows.
In Visual Studio, which is what you would have used for a WinJS 2.0 application, you can download WinJS 4.4 from NuGet. WinJS is actually also available as a bower, grunt or npm package. As of WinJS 3.0, it went cross platform and is no longer tied to only Windows development. You can use WinJS on your websites for example.
My default page was called default.html, but the new solution created an index.html page. If you have the same scenario, open up the package.appxmanifest in Visual Studio (to get a nice GUI) or via code to edit it directly and under the general application tab you will see Start Page as index.html. Change that to default.html and delete index.html.
In your pages that reference WinJS, for example the default.html or index.html, change //Microsoft.WinJS.2.0/ to /WinJS/ . By downloading WinJS through NuGet, it put the WinJS folder in your application.
Hopefully this will get you started on your way to upgrade your Windows 8 WinJS apps to Windows 10 Universal apps.
One last thing I’ll mention is that the package manifest has changed. You can see what has changed in Microsoft’s documentation here: