You could also just display various important quantities in UI Text elements to watch them change as you play the game. You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.
Working hookshot code#
You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc. If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances. You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this) Knowing this information will help you reason about the behavior you are seeing. are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation) what are the values of the variables involved? Are they initialized? Are the values reasonable? is this code even running? which parts are running? how often does it run? what order does it run in? To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.ĭoing this should help you answer these types of questions: you're getting an error or warning and you haven't noticed it in the console window the code is executing on another GameObject than you think it is
the code is executing far MORE OFTEN than you think the code is executing far LESS OFTEN than you think the code is executing far EARLIER or LATER than you think the code you think is executing is not actually executing at all What is often happening in these cases is one of the following: You must find a way to get the information you need in order to reason about what the problem is. If you need to debug, here's a super-easy way to start: Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.īeyond that, Step 3, 4, 5 and 6 become easy because you already understand! For some other less-well-known content creators, this is less true. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. Of course, all this presupposes no errors in the tutorial. If you want to learn, you MUST do Step 2. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. Step 2 is the part everybody seems to miss. It might take days or weeks to work through a single 5-minute tutorial. This is the part that takes a LOT of time when you are new. Go back to the tutorial and try to figure out WHY they did that. Read the documentation on the functions involved. If you are unable to explain any part of it, STOP. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. Go back and work through every part of the tutorial again, and this time explain it to your doggie. It is almost CERTAINLY your typo causing the error, so look again and fix it. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. Do NOT continue until you fix your error.
Working hookshot how to#
If you get any errors, learn how to read the error code and fix your error. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.įortunately this is the easiest part to get right: Be a robot.
Even the slightest deviation (even a single character!) generally ends in disaster. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. How to do tutorials properly, two (2) simple steps to success:
Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration: getting a grappling hook to work properlyīoth of those things are covered by tutorials, but instead of "trying many ways," you should use this simple two-step process.ĭO NOT SKIP EITHER STEP, and that applies for both items above: Click to expand.This will not be a useful approach.
0 kommentar(er)
