You need to make a change of trajectory

Unity Engine
,
1

Привет всем. При разработке игры возник вопрос с траекторией. То, что я уже прикрепил. Необходимо следить за тем, чтобы при выстреле траектория оставалась и когда игрок целится во второй раз, траектория первого выстрела все еще висит, после второго выстрела первая траектория меняется на вторую и так далее с остальными выстрелами.

8664303--1166835--upload_2022-12-15_15-31-42.jpg
8664303--1166835--upload_2022-12-15_15-31-42.jpg1920×1080 191 KB

На скрине видно, что траектории отображаються все. Я сделал их клонирование с помощью спавна(Instantiate(Trajectory, transform.position, transform.rotation)).

Привожу скрипт)

с использованием UnityEngine;
использование Системы;
использование System.Collections.Generic;

[RequireComponent(typeof(Rigidbody))]
[ТребоватьКомпонент(тип(Коллайдер))]

публичный класс DragAndShot : МоноПоведение
{

публичный GameObject Ball;
публичная играObject BoosterBall;
публичная играObject SpawnPos;
публичная линия GameObjectRend;

частная мышь Vector3PressDownPos;
частная мышь Vector3ReleasePos;
приватная скорость Vector3;

частное жесткое тело РБ;

общественный бустер Бустер;
публичный Спаунер Спаунер;
публичная траектория траектории;

частный bool isShoot;

частный статический int Shoots = 0;

общественное поплавковое усилиеMultiplier = 3f;

приватный пустой Start()
    {
        rb = GetComponent<Rigidbody>();
    }

частное пустое обновление()
    {
        if(Input.GetMouseButtonDown(0))
        {
            mousePressDownPos = Input.mousePosition;
        }
       
if(Вход.GetMouseButton(0))
        {
            mouseReleasePos = Input.mousePosition;

            speed = (mousePressDownPos - Input.mousePosition) * forceMultiplier;
Траектория.ShowTrajectory(Ball.transform.position, скорость);
        }

        if(Input.GetMouseButtonUp(0))
        {
            mouseReleasePos = Input.mousePosition;
            Shoot(mousePressDownPos - Input.mousePosition);
        }
    }

void Shoot (Vector2 Force)
    {
        if (isShoot)
возвращать;

рп. AddForce(новый Vector2(Force.x, Force.y) * forceMultiplier);
isShoot = истина;

        Spawner.Instance.NewSpawnRequest();

       
        if (isShoot == true)
        {
Debug.Log("+1 съемка");
Побеги += 1;

Создание экземпляра(Траектория, преобразование.положение, преобразование.вращение);
        }
       
if(Стреляет == 3)
        {
Бустер.ШоуButtons();
        }
    }
}[/код]
2

Hello, English-speaking forum here… welcome!.

I think you are trying to debug a trajectory but I am not 100% sure.

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: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

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:

When in doubt, print it out!™

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

3

Вы не уточнили проблему? Вы пытаетесь иметь вариацию для каждой траектории, чтобы траектория никогда не была одинаковой дважды?

You did not specify the problem? are you trying to have a variation for each trajectory so that the trajectory is never the same twice?