Even though I mentioned that the Unity version of A5 would be much harder (I didn't intentionally make assignments harder in Unity, they just are as part of the nature of the engine), the point of this class is NOT to discourage people from using Unity or try to punish those people who are using it (believe it or not). So I wrote a Unity version of the class example that does the same thing as the UE4 examples, navmesh, all grab methods, and everything. By my estimate in my experience porting this code, it would have taken the Unity people at least 4x longer to do the assignment than the UE4, which is definitely not fair to them. To help the Unity people follow the lecture code, I have also created utility attachment functions like UE4's inside NickVRPawn so that you can easily look at the lectures and see what's happening (e.g. attach, detach, Snap, Keep World, etc.). This also means that you no longer need to write the Unity parenting code I mentioned!

I made sure to use prefabs and prefab variants to essentially try to make the project object-oriented like UE4's version (as close as Unity can get), so this might help to some extent with the Unity version of A4 (e.g. PickupCubes are "subclasses" aka prefab variants of a Collectible). Because of Unity's janky physics engine, some more work needs to be done to preserve momentum, however.

I'm also posting the entire projects on Github for people to borrow code from. If you borrow code from my project, as usual, make sure to write a comment in your code saying where you got it from.

Unity version: https://github.com/nrewkowski/COMP590ClassExampleUnity

UE4 version: https://github.com/nrewkowski/COMP590ClassExampleUE4

For both engine users, I strongly recommend looking at my comments in the Unity version of the code explaining some differences in implementation so you can better understand how the engines differ. If you continue in this field, it would benefit you to understand both (UE4 users, the C++ version would look kind of similar to the C# except I wouldn't need to write Attachment functions myself, so it's still worth understanding it). Hope it helps a bit for those of you struggling with the noodle code.