koobas.hobune.stream
The question is answered, right answer was accepted
How do I make an empty transform?
How would I go about making and empty "transform" and what is a "transform"? I just started using unity like yesterday so i'm a complete noob.
The Unity Script Reference is going to be your number one friend. Navigate yourself to the link below to get a full understanding from the documentation.
"Every object in a scene has a Transform. It's used to store and manipulate the position, rotation and scale of the object."
http://unity3d.com/support/documentation/ScriptReference/Transform.html
If you want to make an empty "transform," what you're really wanting to do is create an empty GameObject:
"Base class for all entities in Unity scenes."
http://unity3d.com/support/documentation/ScriptReference/GameObject.html
To create an empty GameObject ( aka GO for short ), you would:
GameObject => Create Empty
from the top menu.
As for the rest of components inside of Unity, I suggest you search for some basic tutorials in 'getting started' with the layout of Unity and how to manipulate and create objects. Basic questions like these can be simply answered if you actually just take the time and research instead of asking them.
I don't think you should imply that this person hasn't done any research, people learn in different ways. I have had things I've asked that others think should have been obvious, but I needed them explained in a different way.
The reason the Torque engine died was because it's community was constantly telling newbies things like this.
I understand what you're saying, and I tried to word it in a manner that would create the least amount of offense.
But, I also believe that I'm completely justified in doing so.
I just started using unity like yesterday so i'm a complete noob.
Not much you can research / learn in a day, especially when you're completely new to game development. Fundamentally, people generally want instant gratification. Education isn't really based on instant learning, it's based on a lot of work, research, and then you get those 'aha' moments.
I have to agree with $$anonymous$$rAdventure. In my opinion an answer should never, NEVER involve saying "Go read the docs" or "Look at some tutorials", I't just a useless thing to say. The documentation is not perfect, some parts are broken during updates. Some parts are not very clear.
