1
00:00:04,400 --> 00:00:05,570
‫Hello and welcome.

2
00:00:05,570 --> 00:00:11,810
‫In this lecture, we're going to be learning how we can ask good questions and help other people to

3
00:00:11,810 --> 00:00:14,780
‫answer them by providing the right sort of information.

4
00:00:14,780 --> 00:00:16,610
‫Let's dive in and see how.

5
00:00:17,000 --> 00:00:20,630
‫So we're about to dive in to doing some more complicated things.

6
00:00:20,630 --> 00:00:24,830
‫And when following along with complicated lectures, things may go wrong.

7
00:00:24,830 --> 00:00:30,680
‫So it's important that we know how to ask for help in a useful and constructive way.

8
00:00:30,770 --> 00:00:36,170
‫So one of the first principles for asking for help is paste the exact error that you're getting.

9
00:00:36,170 --> 00:00:40,910
‫If you are getting an error message from Unreal or something's not happening as you expect, try and

10
00:00:40,910 --> 00:00:45,170
‫paste that into Google first and see what the results show you.

11
00:00:45,170 --> 00:00:50,240
‫If there's something that you can fix yourself, Google's by far the quickest way rather than asking

12
00:00:50,240 --> 00:00:51,200
‫in the Q&A.

13
00:00:51,680 --> 00:00:58,910
‫Then if that doesn't succeed, do go ahead and ask in the Q&A, but be sure to include the error message

14
00:00:58,910 --> 00:01:00,590
‫and your code.

15
00:01:00,590 --> 00:01:06,170
‫Most crucially, because it might seem like you've done everything the same as us, but that's often

16
00:01:06,170 --> 00:01:11,060
‫not the case, and it's perfectly fine and normal to make slight mistakes.

17
00:01:11,510 --> 00:01:16,520
‫And when describing your problem, be as short as possible, but as long as necessary.

18
00:01:16,520 --> 00:01:21,530
‫You don't want to give too little information and for us not to be able to help them.

19
00:01:21,560 --> 00:01:25,550
‫But also, you don't want to put too much time into writing a question.

20
00:01:25,550 --> 00:01:30,110
‫You don't want to make it too hard for someone to read and get to the nub of the problem.

21
00:01:30,410 --> 00:01:35,090
‫And also, if you find that you have later on solve the problem yourself.

22
00:01:35,090 --> 00:01:40,280
‫Please, please let us know so that we know basically that you don't need our help anymore, but also

23
00:01:40,280 --> 00:01:45,170
‫share your solutions so that others can benefit from what you found out.

24
00:01:45,170 --> 00:01:46,640
‫That's always really helpful.

25
00:01:46,640 --> 00:01:51,410
‫And also while you're waiting, if you've asked a question and have kind of twiddling your thumbs and

26
00:01:51,410 --> 00:01:55,820
‫waiting for a response, then do have a look at other people's questions.

27
00:01:55,820 --> 00:02:01,250
‫It's all there for each of us to help each other, so please answer other people's questions.

28
00:02:01,250 --> 00:02:05,540
‫You often find that you learn a lot and embed a lot of knowledge this way.

29
00:02:05,540 --> 00:02:06,800
‫So what does it take to add?

30
00:02:06,890 --> 00:02:10,430
‫Ask a really good question that will get really good answers.

31
00:02:10,580 --> 00:02:14,450
‫Well, first of all, you need to answer the question, what have you tried?

32
00:02:14,450 --> 00:02:19,430
‫It might seem tempting to say, well, I've done exactly what they did in the lectures, but it's easy

33
00:02:19,430 --> 00:02:20,270
‫to miss a step.

34
00:02:20,270 --> 00:02:22,760
‫It's easy to have misheard or not heard something.

35
00:02:22,760 --> 00:02:25,520
‫So please tell us and reiterate what you've tried.

36
00:02:25,520 --> 00:02:30,410
‫It's a good way of you to revise and make sure that you have actually done everything you thought you

37
00:02:30,410 --> 00:02:30,770
‫did.

38
00:02:30,770 --> 00:02:36,170
‫And also, if you've done any steps to try and understand what's going wrong, try to try and tell us

39
00:02:36,170 --> 00:02:40,910
‫what you've already tried doing so that we aren't suggesting things that you've already done.

40
00:02:41,480 --> 00:02:42,950
‫What did you expect to happen?

41
00:02:42,950 --> 00:02:48,290
‫This may seem obvious to you, but sometimes to the person answering the question, it's not obvious

42
00:02:48,290 --> 00:02:50,750
‫what you were expecting to happen in the first place.

43
00:02:50,750 --> 00:02:54,590
‫So it's not clear why it's gone wrong or if it has gone wrong at all.

44
00:02:54,590 --> 00:03:00,860
‫And then tell us actually what did happen that wasn't what you expected.

45
00:03:00,860 --> 00:03:03,080
‫And be specific with all of this.

46
00:03:03,080 --> 00:03:11,120
‫Use exact error messages, use exact wording, use screenshots if possible, and logs and messages and

47
00:03:11,120 --> 00:03:12,230
‫all these sorts of things.

48
00:03:12,230 --> 00:03:14,090
‫So what kinds of things can we include?

49
00:03:14,090 --> 00:03:18,710
‫What useful information really helps us to debug your situation?

50
00:03:18,770 --> 00:03:22,790
‫Well, like I said already, the steps you've taken is absolutely crucial.

51
00:03:22,790 --> 00:03:23,840
‫That really helps.

52
00:03:24,110 --> 00:03:27,860
‫Any screenshots you can provide a super helpful too.

53
00:03:27,890 --> 00:03:34,130
‫If it's a textual log message, then actually some text is usually easier for us to search through and

54
00:03:34,130 --> 00:03:40,580
‫deal with, and I'll share how you can share long pieces of logs without swamping your question in just

55
00:03:40,580 --> 00:03:41,330
‫a second.

56
00:03:41,450 --> 00:03:45,560
‫The editor logs, so build logs will come later on when we're dealing more with C++.

57
00:03:45,560 --> 00:03:51,770
‫But the editor logs you can provide right now and if there's you've had a bit of back and forth with

58
00:03:51,770 --> 00:03:56,510
‫someone and they're like, how do you could you send your project across and I'll have a play with it

59
00:03:56,510 --> 00:03:58,490
‫and see if I can find the issue.

60
00:03:58,790 --> 00:04:01,730
‫Then I'll show you how to do that as well in this lecture.

61
00:04:01,730 --> 00:04:03,290
‫So let's have a look at screenshots.

62
00:04:03,290 --> 00:04:05,000
‫I'm going to assume you can do that.

63
00:04:05,330 --> 00:04:12,020
‫But in terms of getting the log messages, well, there one way is you've got this log output in your

64
00:04:12,020 --> 00:04:13,100
‫edits down at the bottom.

65
00:04:13,100 --> 00:04:16,820
‫If you click on this, it kind of shows you loads and loads and reams of information.

66
00:04:16,820 --> 00:04:20,810
‫This is not always the easiest way to go and select all of this and copy it.

67
00:04:20,810 --> 00:04:29,000
‫So another way you can get to the same log is to go into your project folder, go into saved, go into

68
00:04:29,000 --> 00:04:32,990
‫logs, and then this log file contains your project log.

69
00:04:32,990 --> 00:04:36,020
‫Now on a mac, you're going to go to a slightly different place.

70
00:04:36,020 --> 00:04:38,750
‫Now, there's a couple of ways you could actually go to get the logs.

71
00:04:38,750 --> 00:04:43,520
‫You could also do it via finder in a similar way to we use Explorer on Windows, but a slightly easier

72
00:04:43,520 --> 00:04:48,590
‫way is to have a look at your console app, which looks like so.

73
00:04:48,770 --> 00:04:55,370
‫And in the console app you can see down the left hand side there are a bunch of different reports and

74
00:04:55,370 --> 00:04:56,690
‫different areas that you can look for.

75
00:04:56,690 --> 00:05:01,220
‫Logs when we're looking for is the log reports and then you can scroll down through this list and you

76
00:05:01,220 --> 00:05:03,230
‫can see logs from all sorts of applications.

77
00:05:03,230 --> 00:05:03,590
‫Now you'll.

78
00:05:03,650 --> 00:05:07,370
‫Looking for the one that has the same name as your project.

79
00:05:07,370 --> 00:05:10,150
‫So in my case you can see I've got my project too.

80
00:05:10,160 --> 00:05:18,770
‫I've got the intro project pro logs, so you can go and click into that and you can see the the log

81
00:05:18,770 --> 00:05:24,020
‫is very long just like on windows and you can copy and paste from here if you hover over this.

82
00:05:24,020 --> 00:05:25,910
‫It also shows you where it is on disk.

83
00:05:25,910 --> 00:05:33,500
‫In my case, it's under my user library logs, Unreal Engine, and then the name of the particular project

84
00:05:33,500 --> 00:05:36,320
‫and then the log file within there.

85
00:05:36,710 --> 00:05:39,890
‫But because it's so long, please don't paste that into your question.

86
00:05:39,890 --> 00:05:46,970
‫It's going to make it really hard to figure out go to jist dot github dot com and what you can do is

87
00:05:46,970 --> 00:05:51,290
‫you can take the file, the project log file and you can just drag it onto this web page and you can

88
00:05:51,290 --> 00:05:54,050
‫see it just uploads the contents of that log.

89
00:05:54,050 --> 00:05:57,260
‫You can go and say, create secret gist.

90
00:05:57,530 --> 00:06:02,300
‫And then what you're going to do is you can just copy the URL from the URL bar and paste that into your

91
00:06:02,300 --> 00:06:03,980
‫question instead.

92
00:06:03,980 --> 00:06:08,150
‫And that's going to allow someone to come through, search through for the relevant bit of the log and

93
00:06:08,150 --> 00:06:13,610
‫maybe help identify what has actually gone wrong in your setup.

94
00:06:13,610 --> 00:06:15,860
‫So that's how you would share your log messages.

95
00:06:15,860 --> 00:06:22,640
‫You can do the same thing with build errors that are particularly long in C++ when we get to the C++

96
00:06:22,640 --> 00:06:23,450
‫section.

97
00:06:23,720 --> 00:06:29,300
‫But the other thing, the last resort sort of is to share your actual project.

98
00:06:29,300 --> 00:06:36,080
‫Now it might be tempting to just zip up the entire project folder, but there's a lot of stuff in here

99
00:06:36,080 --> 00:06:40,400
‫that we don't need to send a lot of build information that can just be recreated.

100
00:06:40,400 --> 00:06:49,910
‫So the best way to produce the output here is to go to your file menu, go to zip project and then select

101
00:06:49,910 --> 00:06:52,640
‫where you want this zip project to go.

102
00:06:52,640 --> 00:06:56,000
‫You might go and put this on your desktop, for example.

103
00:06:56,000 --> 00:07:00,380
‫I've already got one here, but I'm going to overwrite that and then you can go ahead and hit save and

104
00:07:00,380 --> 00:07:01,880
‫say, I want to replace it in this case.

105
00:07:02,240 --> 00:07:06,680
‫And you'll just see a little pop up saying that it's zipping up the project and when it's complete,

106
00:07:06,680 --> 00:07:11,600
‫it's complete and you can go and upload that to something like Dropbox or Google Drive and then share

107
00:07:11,600 --> 00:07:13,130
‫that in your question.

108
00:07:13,130 --> 00:07:20,240
‫So I hope you've got a better idea of how you can ask really great questions and hopefully get really

109
00:07:20,240 --> 00:07:22,130
‫great answers in return.

110
00:07:22,370 --> 00:07:23,630
‫See you in the next lecture.