OK, just finished my version. Unfortunately with my lack of persistence I ran out of narrative steam right around the second “corridor” part.
Whats more unfortunate is that whilst uploading this and trying to run it with Firefox, I kept getting a notification to install the Web player. Did so, several times, to no avail. Same notification. Slight rage.
With some investigation it turned out that apparently Mozilla has discontinued support for Unity Web player due to security reasons on the 17th of March. From what I could gather, most other browsers are going to do the same. I still got the link to work on IExplorer but thats never going to be my choice even if they continued support, so its bye bye to any Unity Web developing plans …
What I can’t grasp is why there isn’t a proper notification explaining this, instead of the rage inducing “install the web player”. Would have saved me a lot of grief and unnecessary time wasting efforts …
/approaches cautiously in case of instilling additional rage
The original Complete Unity Developer course was written using an older version of Unity which shipped with the WebPlayer - gradually more and more browsers have dropped support for the underlying technology used by it.
One of the early versions of Unity 5 shipped with the ability to make a WebGL build, a version or so later, and the WebPlayer was removed. As such, with Unity 5+ you no longer need to install any additional browser extensions, which is good.
During the course you will get to a section where you do actually upgrade to Unity 5, so you could, should you wish to, go back and upgrade your previous games for the WebGL build - the world is then good. Additionally, the team have added additional lectures/resources to each section which cover the differences between the original course game (based on the older version of Unity) and Unity 5, so, if you wanted to install Unity 5+ right now, you could, and then use these guides to help over come the minor differences that you will experience as you progress with the course.
Note that many people have already been through this process, which is great, as it means the forum is riddled with peoples questions about the differences they have run in to and how to overcome them when they’ve run into trouble.
Had I but continued with the lecture for a few more minutes instead of rushing into uploading (although as you pointed out, this became evident only in the later addition), I would have learned about WebGL myself. Good news, all is well. Wrath fading.
One other thing to consider, obviously the browser issues for the old WebPlayer means that less and less people are able to play / test your games - so if you can push WebGL builds up you are more likely to have people play them and provide feedback.
Thanks Rob,
