Hi, hello.
I am making a Gorilla Tag fangame, but there is a problem, my hands are not following my controllers, i tried a lot, but nothing works.
Can you help me solve this problem?
Time to try debugging!
By debugging you can find out exactly what your program is doing so you can fix it.
Use the above techniques to get the information you need in order to reason about what the problem is.
You can also use Debug.Log(...); statements to find out if any of your code is even running. Don’t assume it is.
Once you understand what the problem is, you may begin to reason about a solution to the problem.
Remember with Unity the code is only a tiny fraction of the problem space. Everything asset- and scene- wise must also be set up correctly to match the associated code and its assumptions.
Shouldn’t you tag this thread VR and not android? That way other actual VR devs are more likely to see this thread.
Still, you need to describe more about what you tried and what hasn’t been working.
Note: I’m not a VR dev, just trying to help your thread get seen.
Side note: There seems to be a million people making Gorilla Tag fan games.
1 Like
Please don’t necro-post. If you have a new question, make a new post. It’s FREE!!
Posting a photo does not constitute a useful technical request for assistance. Nobody here wants to play guessing games. Instead, try this bog-standard problem reporting template:
How to report your problem productively in the Unity3D forums:
This is the bare minimum of information to report:
- what you want
- what you tried
- what you expected to happen
- what actually happened, log output, variable values, and especially any errors you see
- links to actual Unity3D documentation you used to cross-check your work (CRITICAL!!!)
The purpose of YOU providing links is to make our job easier, while simultaneously showing us that you actually put effort into the process. If you haven’t put effort into finding the documentation, why should we bother putting effort into replying?
If you post code, only post the relevant code and always use the format button above. Do not post photographs of code.
If you lack ANY of the above, that just means you haven’t done your homework yet to debug what is happening. By debugging you can find out exactly what your program is doing so you can fix it or ask meaningfully for help.
Use the above techniques to get the information you need in order to reason about what the problem is.
You can also use Debug.Log(...); statements to find out if any of your code is even running. Don’t assume it is.
Once you understand what the problem is, you may begin to reason about a solution to the problem.
Remember with Unity the code is only a tiny fraction of the problem space. Everything asset- and scene- wise must also be set up correctly to match the associated code and its assumptions.