Hi 
I’m trying to follow the steps in this process but am stuck at 3.1(2) and 3.1(5)
Here’s an OBS recording of what I’m seeing
What can I do?
Generally tutorials only require two steps:
Two steps to tutorials and / or example code:
- do them perfectly, to the letter (zero typos, including punctuation and capitalization)
- stop and understand each step to understand what is going on.
If you go past anything that you don’t understand, then you’re just mimicking what you saw without actually learning, essentially wasting your own time. It’s only two steps. Don’t skip either step.
If you have a particular problem it’s always best to go back over the items relating to the part that is giving you difficulty. Alternately you could just debug what you have.
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.
Whatever you’re doing, be sure you do it one step at a time, building always upon success, like this guy:
Imphenzia: How Did I Learn To Make Games:
If you find yourself totally stuck and you’re absolutely positive you did everything correctly, posting to the maker of the tutorial is always an option. If there’s an issue, it is rare that you would be the only one having it, so always check the notes.
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?
Thanks for the reply Kurt but this is a bit much of a reply.
I thought I made enough answers to your questions at the bottom of your reply pretty clear.
Learning 2 new advanced software (Unity & FMOD) is overwhelming.
I’m a beginner here.
Are you able to solve my specific question?
I don’t think people are keen to download a video from we-transfer to see the issue you’re having. At the very least, describe it, or take appropriate screenshots and post them in the thread.
It’s worth pointing out that tutorial is looking at Unity Hub and Unity versions from 6 years ago now, and are very likely completely out of date.
1 Like
Yeah this is almost certainly why.
That’s too bad, I was looking forward to a tutorial that centers on both Unity & FMOD
Probably, if you frame it in the structure listed above.
Remember, we’re not going digging through videos trying to figure out what your question is.
It’s on YOU to communicate effectively to complete strangers.
And that’s why we have this standardized (across the world really) list:
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?