Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

How do you start your scrolling background on keypress?

Discussion in '2D' started by Shaoby, Nov 12, 2022.

  1. Shaoby

    Shaoby

    Joined:
    Nov 10, 2022
    Posts:
    2
    hey im creating a simple 2d scrolling rocket game but when i hit play the background which are clouds are already moving is there anyway to set it as when i hit spacebar the background starts moving giving the effect the rocket is moving

    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    4.  
    5. public class BackGroundScript : MonoBehaviour
    6. {
    7.     public KeyCode start;
    8.     public float startingYpos, resetPos;
    9.     // Start is called before the first frame update
    10.     void Start()
    11.     {
    12.        
    13.     }
    14.  
    15.     public float speed;
    16.     // Update is called once per frame
    17.     void Update()
    18.     {
    19.         transform.Translate(Vector2.down * speed * Time.deltaTime);
    20.         if (transform.position.y < resetPos)
    21.         {
    22.             transform.position = new Vector2(transform.position.x,startingYpos);
    23.         }
    24.     }
     
  2. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    36,954
    Yes. Always start with tutorials for such a simple thing.

    Hint: it will be MORE than just code. Always.

    If what you have isn't working, here's how to troubleshoot it.

    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 running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: https://forum.unity.com/threads/how-to-capturing-device-logs-on-ios.529920/ or this answer for Android: https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/

    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:

    https://forum.unity.com/threads/coroutine-missing-hint-and-error.1103197/#post-7100494

    When in doubt, print it out!(tm)

    Note: the
    print()
    function is an alias for Debug.Log() provided by the MonoBehaviour class.
     
  3. Shaoby

    Shaoby

    Joined:
    Nov 10, 2022
    Posts:
    2
    Got it working thanks


    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    4.  
    5. public class BackGroundScript : MonoBehaviour
    6. {
    7.     public float startingYpos, resetPos;
    8.     // Start is called before the first frame update
    9.     void Start()
    10.     {
    11.        
    12.     }
    13.     public KeyCode SpaceBar;
    14.  
    15.     public float ScrollSpeed;
    16.     // Update is called once per frame
    17.     void Update()
    18.     {
    19.         if (Input.GetKeyDown(SpaceBar))
    20.         {
    21.             ScrollSpeed = 10f;
    22.         }
    23.  
    24.         transform.Translate(Vector2.down * ScrollSpeed * Time.deltaTime);
    25.         if (transform.position.y < resetPos)
    26.         {
    27.             transform.position = new Vector2(transform.position.x,startingYpos);
    28.         }
    29.     }
    30. }
    31.  
     
    Kurt-Dekker likes this.