ViewportPointToRay way to ignore collision on player object?

[snake5510]

Hello, I am making simple 3rd person shooter I came across issue where camera is looking from bottom upward.

 if (Time.time >= timeToFire + 1 / weapon.fireRate)
        {
            timeToFire = Time.time + 1 / weapon.fireRate;
            Vector3 destination;
            Ray ray = PlayerCamera.cameraObject.ViewportPointToRay(new Vector3(0.5f, 0.5f, 0));
            RaycastHit hit;
            if (Physics.Raycast(ray, out hit, layerMask))
            {
                print(hit.collider.gameObject.name);
                destination = hit.point;
            }
            else
            {
                print("gotten dest");
                destination = ray.GetPoint(1000);
            }
            var go = Instantiate(bullet);
            go.GetComponent<Rigidbody>().velocity = (destination - weaponMuzzle.position).normalized * 35;
            go.transform.position = weaponMuzzle.transform.position;
            go.transform.rotation = weaponMuzzle.transform.rotation;
            go.GetComponent<Bullet>().SetUpBullet(view, weapon.damage, Parent);
            //Hit Scan
            go.transform.position = weaponMuzzle.transform.position;
            var effect = Instantiate(funFlash, weaponMuzzle.transform.position, Quaternion.identity);
            effect.transform.parent = weaponMuzzle.transform;
            Destroy(go, 1);
        }

Here is the code I use,

This is what triggers the issue when camera is positioned downwards like so, how can I make the ray just ignore the player entirely? This is a multiplayer project so I dont essentially want to ignore the raycast on another player but it should always go forward.

[Kurt-Dekker]

You can ignore layers in a raycast by supplying a layerMask.

Be sure you understand the fundamentals of layers versus layer masks:

Raycast "layermask" parameter

The layer is a number from 0 to 31. It corresponds to each of those named layers. A layer MASK is a 32-bit bitfield that says which of these you want to ignore. This enables you to ignore (mask) multiple layers, each one represented by a single bit in the 32-bit integer. In your code above, 9 (Collision) is a layer, NOT a mask. Raycast takes a layermask. If you want to turn a layer name into a LayerMask, here’s the utility you want: You can also go cheap and cheerful and rotate the bits yo…

Always use named arguments with Physics.Raycast() because it contains many poorly-designed overloads:

LayerMask + RayCast does not work like described in the docs

Physics.Raycast() is a HORRIBLY overloaded function. I recommend ALWAYS specifying the named arguments rather than hoping you got them in the correct order. This is because layerMask (an int) and maxDistance (a float) can be easily mistaken at the call site if you are passing an integer value for maxDistance. In this case, no error will be returned, and it will just fail mysteriously. The time you save by typing out named arguments will be your own. Instead of this: Physics.Raycast(origi…

The following approach will also help you reason about what is actually happening.

You must find a way to get the information you need in order to reason about what the problem is.

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

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:

Coroutine missing hint and error

This is so unnecessary. Use the beauty and power of instantly and immediately putting a Debug.Log() statement into the very start of the coroutine, right at the top. Do this always at the very first sign of trouble or question in your mind. The instant you did this you would see “Oh man, this code is simply not getting run!” And you could LASER-FOCUS 100% your efforts on studying what you expect to run it, eg., the call location, and isolate why it is not running. You would look at literall…