Search Unity

Question Newbie at Unity; Need help with scripting please :)

Discussion in 'Editor & General Support' started by hsadiyaa, Mar 28, 2023.

  1. hsadiyaa

    hsadiyaa

    Joined:
    Nov 15, 2022
    Posts:
    3
    :rolleyes:Hello, World! (Pun not intentionally intended)

    After countless YouTube videos, forums, manual, and blog readings, I was wondering if I may receive some help with coding for movement cause I cannot figure it out completely (just able to collect some idea on how-to along the way). I have have two objects that I would like to have slide away from each other x amount of distance and then begin to rotate up to ~135• (ex. to help visualize: double doors that are closed and then start to slide/move away from each other and then begin to rotate outwards pivoting on their outer edge say once they are like 10units from each other, then they stop translating at 90• and 15units apart, but continue to rotate outwards while stationary until they reach 135• and then stop; at this point the doors should now be wide open, each outwards at 135• and 15 units apart. Also movement is relative to their outer edge, so 15 units apart from the outer edge when closed but after rotating the outer edge is now the inner/closer edge to each other). Hopefully that made sense

    I want to be able to change the units of translation and the angle in the inspector so I know I’ll need to have public floats for each (I presume). So far I have:

    .
    .
    .
    public Transform objectLocation;
    public float rotationAngle;
    public float rotationSpeed;
    public GameObject pivotObject;
    .
    .
    .
    transform.Translate(new Vector3(1,0,0), objectLocation);
    .
    .
    .
    private Vector3 Vector3(float v1, int v2, int v3)
    .
    throw new NotImplementedException() <—this was inserted as a suggestion by visual studio but idk what it really does except something to do with true/false I think
    .
    .
    .
    transform.Rotate(new Vector3(0,0,-1), rotationSpeed * Time.smoothDeltaTime);
    .
    .


    I won’t lie some of the script ‘I think’ I made-up just based on what I’ve come across (I’m just trial and error at this point but I guess that’s the best teacher)

    I know I’ll need a start/stop and a true/false codon somewhere or somehow but I haven’t figured that part out yet.

    Also would like to be able to have them do the reverse; so rotate inwards and slide back closed.

    Any guidance or help or explanation or script;) would immensely help as I’ve been trying to figure it out for two days now and time is moving but progress is slow.
    Thank you in advance !
     
  2. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,745
    That won't be a useful approach until you reach an actual level of understanding of what you are doing. It doesn't sound like you've reached that point.

    It actually sounds like perhaps you're not doing the tutorials properly??

    Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

    How to do tutorials properly, two (2) simple steps to success:

    Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

    Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
    BE PERFECT IN EVERYTHING YOU DO HERE!!


    If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

    Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

    Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

    Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

    Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

    Finally, when you have errors, don't post here... just go fix your errors! Here's how:

    Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

    The complete error message contains everything you need to know to fix the error yourself.

    The important parts of the error message are:

    - the description of the error itself (google this; you are NEVER the first one!)
    - the file it occurred in (critical!)
    - the line number and character position (the two numbers in parentheses)
    - also possibly useful is the stack trace (all the lines of text in the lower console window)

    Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

    Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

    All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.

    Imphenzia: How Did I Learn To Make Games:

     
    hsadiyaa likes this.