Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"

PGF2FSOReviewClip1

0 (0 Likes / 0 Dislikes)
Hello, welcome to Programming Foundations 2. This is Chris Maxwell speaking, and I will be your primary instructor throughout this month. Other instructors may pop on and off throughout the month, so don't be surprised if you see a familiar face from the past or potentially a future instructor. So, that being said, what are we going to be doing this month? Well, obviously the title of the class is Programming Foundations, so were very much going to be programming. What are we going got programming? Well, we're going to be programming in the C# language. Why the C# language? Well, that's now the primary language of the Unity 3D editor and game conglomerate tool. You saw this is level design a month or so ago, so hopefully this is not completely a brand new experience for you, but if it is then you should learn a lot of good details and if it is, well hopefully, a good refresher. Alright, so as I mentioned we're going to be working Unity and C#. Over the course of the month we're going to be building a little arcade style space shooter where you can start exercising in safe environment some of your programming talents that you'll learn. So, let's look at the end product of what one of the other students from a couple of months ago created. As you can see simple, standard menu. One thing that might be a little bit lacking, not to critique the assignment too much, is maybe an animated background. Because right now it looks like it's could be frozen or on pause but clearly when I hover the mouse over the buttons you can see how they interact. And they give you some great controls there at the bottom, so you know what you're doing. So go ahead and play a little bit. And as you can see there are some particles there, there's some projectiles, there's some enemies, there's lights, let's see if I can turn on multi-shot, you have multi-shots here. You have different styles of bad guys. And let me see if I can shoot a missile there. But you kind of get the sense of it, theres storing. There's even a pause menu. So that's just a very, very quick intro into what you'll be doing this month. Alright, let's run back to FSO here and go over the activities page. There's always some common questions that I like to address. As you can see there's the course policies, obviously you're going to have some tests. Those tests basically say "Hey, did you actually read these policies?". Yes or no. If you did then you then you should be able to answer the test questions very, very quickly and without much trouble. Then you have the course help page or activities and I'll get back to these in just a second. And then you start falling into this weekly routine of working on your notes and your lab, your notes and your lab, your notes and your lab. Well, the fourth week is special and I know without a doubt there's going to be at least one person who forgets to look at the due dates, so pay attention to the fourth week and the due dates. It's an early due date, unlike the weekly assignments, the labs being the body of the work, as you can see by the percentage of the weight of the grade. They're all due Sunday night, 11:59 PM. Pretty standard. But the fourth week, because I have to get my grading done, by Friday at noon, the test are actually going to be due Thursday night. Again, the due date is not when you do the work, rather that's your last chance to do the work. Please don't wait until the last day of the fourth week to realize that oh, you missed the test. Now I always send out a reminder Saturday, the week before hand. A little reminder saying "Hey, early due dates. Don't forget about this stuff". So, I really, really, really want to stress that because it's very heart breaking to see somebody who has a great lab project has done well in the class and then they make that simple mistake of assuming that the last's weeks activities will be due on Sunday. So, that's not the case. Please, please, please write down this week four due date. And then the fourth week lab is optional just because of the time crunch and just because you're coming off week 3, which probably is the most difficult lab, or most challenging. There wasn't really much time or a fair way of giving you this work to do and expecting you to get it done in three days after. So the fourth week is very much just menus and polish and it implements it using game objects, rather than the new UI system, so it's a little bit of a deprecated experience. Still, lots of good stuff, lots of screens fades in there that you can implement into your own project. And then finally, we have the course exit. Now, sometimes this is confusing because you see a survey and the evaluation. The evaluation is what you see in every course, the survey is something that's very targeted to my class, or the PGF2 course. The evaluation is just the generic thumbs up, thumbs down type survey. While the regular, or I should say the student course survey, is geared towards the lab the assets, questions, how long have you been debugging, this and that, so if you have time please take the survey because that helps me target specific activities and improve them. So, course policies. Let's look over what course policies are all about. Again, I'm not going to read these to you because you're more than capable of reading them on your own. But I just want to run through them really quickly. The academic honesty policy has changed since last month, so if you thought you've read it before, please take time to read it again because it has changed. Contact policy again just has my information, the different ways you can reach me, my hours, sometimes I'll have something listed next to them like the Unity Open Lab, so I'll be available in the evening hours from 7 pm - 10pm, but to reach me you'll have to go through the Unity Open Lab, or like tonight, I'm in the Go To Training. So just pay attention to some of those marks and you'll be able to contact me easy enough. Again, there's lots of requirements about contacting me, what you need to send me. And it may seem overly harsh, but these are really here for you. For instance, never email attachments. Now how could that help you? Well, if you send me an email attachment there's a 99% chance that our quarantine system will lock it away for 24 - 48 hours, then I won't see it until the next day. Well, if that happens then you're not going to get a reply from me. in a timely fashion and that's obviously not what either one of us wants. So, if you follow these guides it will save me asking you questions that you could already answer. And it would help get communication to me quicker. And then we have the late submission policy. Basically if you don't have documentation of the emergency, and you're not requesting it before the due date, it's a denial. So if you ask the next day "Hey, can I re-submit it because I didn't submit the right files Or I wasn't paying attention, or whatever the case may be, it's going to be an automatic no. And then we have the Submission Guideline policy. This is reiterated at the bottom of each of the lab documents and I'll walk you through this process. It may seem very wordy, but it should be a simple five minute process or less than five minutes. And then backing up your work. I don't think anyone really needs to be told why backing up your work is important. Every month there's unfortunately a student who forgets to backup their work they've worked all week long and I get an email Sunday night at 10pm, They're panicked because they accidentally deleted their work, the work became corrupt, who knows what the issue was. And they don't have any backups. So just make regular back ups throughout your work week. And put them somewhere safe. Put them in DropBox, somewhere else that's not on your hard drive just incase your hard drive does crash. I've had that same situation. Student says "I have 50 back ups" "Five back ups a day and my hard drive crashed. All my backups were on my hard drive". "Now all my back ups are lost as well". Writing Technical Questions. This comes back to the contact policy. Although the contact policy is much more about times and how to reach me, while this is much more of a way to be a professional in your communication. So, just read through it and learn the information that you can from it. And then take the test on it and you will do fine. Now moving on to the course help. So, we have this discussion Google group. What is this all about? Well, a lot of times you'll see discussion groups where you have forced replies saying you have to reply to this three times, you have to post this, and I find that personally busy work. Unless you have something of value to say, then just saying something for the sake of saying it is just spam. And that's not to discourage you from posting I definitely want to encourage you to post, but the point being I don't want your time taken away from programming to do busy work. You should only do the "busy work" when it's beneficial to you. In that case it is not busy work. So, what does this Google group do for us? If you've accepted the invite or if you've joined, then you should be able to see that this is a persistent discussion. This has started I believe about a year ago or longer. Students from the previous courses or previous months have posted in here questions and tips and things like that. So if you have a question potentially about some lab feature, then look on here and see if it has already been answered. If it hasn't then post on here and ask the question. Either I'll reply or a fellow student will reply or a different instructor will reply. Or maybe a lab technician will reply and they will try to address your question as best as possible. Now does that mean that you can just post all your code up there, all the code from your project? "Hey, can you finish my assignment for me", "Hey, tell me what I did wrong"? No. Obviously you have to perform you due diligence and actually put forth some reasonable effort before you can seek a reply. That being said, maybe you have a tutorial that you came across that you thought was really, really helpful or you found a way to change the theme in your code editor, then post that on here. Just perform some due diligence, make sure you're not just posting something that has already been posted. Otherwise it will just get deleted. So yes, this discussion group is for you, it's not busy work. Post if you have something legitimate to post, be it a question or a helpful tip. Alright, the other activity in the course help which is the course resources and materials. Well, I'm a big fan of having a centralized location of all the course materials. If you go through the labs and the note templates and everything else, you can download them in the downloads section. In this activity you can se how they're a bunch of documents in this download section. One of the key ones is the PGF2 Assets. Which you'll need for your labs, so if you're missing it make sure that you take the time to download it. Now that being said, this link here jumps over to a google drive. This google drive contains all the course resources. You can download it as one big zip file if you want or you can pick it part and get the individual files. Again, that PGF2 Asset package, make sure you download it. I've heard some people say how, well we don't want to open it. Well, when we do you'll see something like this. Potentially on a Mac side, depending on your file association. And I say the Mac side. I should mention that currently I'm on the PC side. I do all my work on the PC side. I very rarely use the Mac side. So if you're having some weird, bizarre technical issue, the first thing I'm gonna say is try it out on the PC side. If it works, then continue on. If it does't work, then I can probably help trouble shoot it a bit more on the Windows side or the PC side. Again, you have all the loose documents in the top folder, or the root folder. And these documents here just span the course the entire month. While these weekly folder are basically just the drops of each weeks lab assignment. I'll go through this here in just a second in a bit more detail I want to go over some of these loose documents first.

Video Details

Duration: 13 minutes and 19 seconds
Country:
Language: English
License: Dotsub - Standard License
Genre: None
Views: 10
Posted by: gaiarose on Oct 27, 2015

PGF2FSOReviewClip1

Caption and Translate

    Sign In/Register for Dotsub to translate this video.