Here's an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:įirst, please stop necro-posting to old threads. This can simplify and isolate compounding effects of other items in your scene or prefab. Google for how on your particular mobile target, such as this answer or iOS: or this answer for Android: Īnother useful approach is to temporarily strip out everything besides what is necessary to prove your issue. If you are running a mobile device you can also view the console output. 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. 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 have no idea what's happening, FIX THAT FIRST. links to documentation you used to cross-check your work (CRITICAL!!!) what actually happened, especially any errors you see This is the bare minimum of information to report: How to report your problem productively in the Unit圓D forums:
Click to expand.First, please stop necro-posting to old threads.
0 kommentar(er)
