Alert! If you get an error when you write this line:
playerPlane.Raycast(rayFromCameraToCursor, out float distanceFromCamera);
Write these two lines instead:
float distanceFromCamera;
playerPlane.Raycast(rayFromCameraToCursor, out distanceFromCamera);
Sorry about that, seems my Visual Studio is using a later version of the language that lets you do this on one line, when the old one couldn't.
I hit a very strange issue in this episode, but I think I understand what happened now - details below. It throws me a bit so I make some mistakes later too - if you don't already, I suggest watching ahead to when I test a thing before copying what I've written. With my last tutorial I got some feedback that people appreciated seeing the process of dealing with things like this, more than a perfect result without explanation, so I've left it in. Which suits me nicely, because if I have to do more than 1 rehearsal and/or video editing to make these, it risks becoming a chore!
Okay, so the weird issue: it happens when I accidentally type Vector.up instead of Vector3.up. Minor typo, but it turns out Vector by itself is a word that does have meaning, but in a different 'namespace' - a sort of optional extra dictionary. Visual Studio, trying to be clever, detects this and automatically adds this namespace to the file we're working on - right at the very top of the document, it's added a line saying "using System.Numerics" - that's this extra dictionary. And that dictionary has its own different definitions of things like 'Vector3' and 'Plane' so Visual Studio is suddenly unsure what we mean by those. I've never hit this before, I didn't know VS would do this by default, but if I'd known I could have just deleted the 'using' line to fix it.
Usual notes:
Start with part 1, obviously - here's the playlist: • Make A Game In Unity With No Experience
You can download the project files for each episode here: https://drive.google.com/open?id=19L7...
Please don't hesitate to tell me in the comments if anything is unclear - I can both clarify in a future ep, and adapt the pace to improve in future. If anyone's left behind there's room for improvement.
If you're not getting the same results I am, download and check my version of the project - if that doesn't work either, something's up with your install or PC. If my version works but yours doesn't, there must be a difference between them - hunt it down if you can, or just use my copy going forward.