Good afternoon everyone, sorry you are asking this question, it is very important for me, I have already looked for a lot of videos on how to build the game, but I face a problem. I would need my build to come out like when I play it in unity, explain better why I need it. character movement that bugs when it is not already open in the root of the game so I made it all open in the root but when I press play it works normally but when I go to build the mentioned problem happens of him closing the character and opening it again there is a way to solve it this in the build already build with the character open in the root?
Would you like to build without changing anything, just build to open as in the PLAY MODE of unity?
Thank you for your attention and sorry for something personal but I really need this help so I don’t abandon my project I’m very sad in Play everything works when I went to build it loses control of the camera
I really need help, I’ve been working on my rigbody character in my netcod for months now when I thought I had fixed the build I made for testing it broke me, please I don’t want to have to give up my project uses latedupdate on unit when it reloads or doesn’t open on browser root it bug frame
If you have no idea what your program is doing, it is now time to fix that! Here’s how:
You must find a way to get the information you need in order to reason about what the problem is.
Once you understand what the problem is, you may begin to reason about a solution to the problem.
What is often happening in these cases is one of the following:
the code you think is executing is not actually executing at all
the code is executing far EARLIER or LATER than you think
the code is executing far LESS OFTEN than you think
the code is executing far MORE OFTEN than you think
the code is executing on another GameObject than you think it is
you’re getting an error or warning and you haven’t noticed it in the console window
To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.
Doing this should help you answer these types of questions:
is this code even running? which parts are running? how often does it run? what order does it run in?
what are the values of the variables involved? Are they initialized? Are the values reasonable?
are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)
Knowing this information will help you reason about the behavior you are seeing.
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);
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 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.
You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.
You could also just display various important quantities in UI Text elements to watch them change as you play the game.
If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.
Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.
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:
When in doubt, print it out!™
Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.
