[Part 3.5] After jumping and falling, damage is not counted.

[Da]

Helpful?

Up

0

::

Hi. Faced with such a problem. Hits are registered, but not everywhere. For example, when gg falls, they don’t want to register hits. It works, but it’s weird. You have to increase the hitbox itself, but this is poorly reflected when the gg does not fall (the hitbox becomes much larger than it should be). I did everything exactly as in the video. https://www.youtube.com/watch?v=HkuihIuKAm0&list=PLgXA5L5ma2BvEqzzeLnb7Q_4z8bz_cKmO&index=9

[Ser Apustaja]

Helpful?

Up

0

::

It sounds like you’re dealing with an issue related to hit detection in a game, particularly when your game object (gg) falls. If hits are not being registered consistently, there are a few things you could check or try to improve the situation:

1. Hitbox Size and Position: Ensure that the hitbox is appropriately sized and positioned. If the hitbox is too small, it might not register hits when the object falls. However, increasing the hitbox too much can lead to unintended collisions when the object is not falling. You might consider using a dynamic hitbox that adjusts its size based on the object’s state (falling vs. not falling).

2. Collision Layer: Verify that the layers involved in collision detection are set correctly. Sometimes, objects may not register hits if they are on different collision layers or if the collision matrix does not allow for interactions between the layers.

3. Physics Update Rate: Check the physics update rate of your game. If the game’s physics are updated at a low frequency, it might lead to missed collisions. Increasing the frequency of physics updates can help improve hit detection.

4. Raycasting: Instead of relying solely on hitboxes, consider using raycasting for more precise hit detection. Raycasting can provide more accurate collision detection, especially for falling objects.

5. Debugging: Use debugging tools to visualize the hitbox and see where it is in relation to other objects. This can help you understand why hits are not being registered in certain situations.

6. Events and Triggers: Ensure that you have the correct events set up for registering hits. For example, check if you are using OnCollisionEnter, OnTriggerEnter, or similar methods correctly.

7. Game Engine Settings: Depending on the game engine you are using, there may be settings that affect how collisions are detected. Review the documentation for your specific engine to ensure everything is configured properly.

8. Check the Video Again: Since you mentioned following a video tutorial, double-check the steps in the video to ensure that you have not missed any important details or settings.

If you provide more specific details about the game engine or the code you are using, I can offer more targeted advice.

[Da]

Helpful?

Up

0

::

I use Unity. The layers are set correctly, I don’t think the problem is with them, although I’m not sure (Everything works fine on the ground and during the jump itself, but not in the fall – the function itself works, I checked with a debugger). The code for registering hits.

[Header("Attack Settings")]
[SerializeField] private float TimeBeetwenAttack;
bool attack = false;
private float TimeSinceAttack;
[SerializeField] Transform SideAttackTransform;
[SerializeField] Vector2 SideAttackArea;
[SerializeField] LayerMask attackableLayer;
[SerializeField] private float damage;

void Update() 
{
    if (isDashing)
    {
        return;
    }
    TimeSinceAttack += Time.deltaTime;
    GetInputs();
    Attack();
    Flip();
    Move();
    Jump();
    StartDash();
    anim.SetBool("NotDash", isDashing);
}

private void Attack()
{
    if (Input.GetButtonDown("Attack") && TimeSinceAttack >= TimeBeetwenAttack)
    {
        TimeSinceAttack = 0f;
        anim.SetTrigger("Attacking");
        Hit(SideAttackTransform, SideAttackArea);
    }
}

void Hit(Transform _attackTransform, Vector2 _attackArea)
{
    Collider2D[] objectsToHit = Physics2D.OverlapBoxAll(_attackTransform.position, _attackArea, 0, attackableLayer);

    if (objectsToHit.Length > 0)
    {
        Debug.Log("Hit!");
    }
    else if (objectsToHit.Length <= 0)
    {
        Debug.Log("No Hit!");
    }
}

private void OnDrawGizmos()
{
    Gizmos.color = Color.red;
    Gizmos.DrawWireCube(SideAttackTransform.position, SideAttackArea);
}

[Terence]

Helpful?

Up

0

::

@Da can you use ScreenToGif to record a clip of the issue? https://www.screentogif.com/

Let me know if you see any errors on your Console window as well.

[Ser Apustaja]

Helpful?

Up

0

::

It looks like you’re trying to handle an attack mechanism in Unity, but you’re facing issues with detecting hits while falling. Since you’ve mentioned that everything works when the character is on the ground or during a jump, this indicates that the logic for the attack itself may be functioning correctly, but there might be some issues related to the attack detection when falling.

Here are a few suggestions to help you troubleshoot and potentially resolve the issue:

1. Check the Attack Area Size:

   • Ensure that the SideAttackArea variable is set correctly in the inspector. If it’s too small or positioned incorrectly, it may not overlap with any colliders while falling.

2. Adjust the Position of the Attack Transform:

   • When you’re falling, the position of SideAttackTransform could change. Make sure that it is correctly positioned relative to your character’s collider and that it is where you expect it to be when the attack is triggered.

3. Debugging the Attack Position:

   • Add a debug log inside the Hit method to print the position of _attackTransform and the dimensions of _attackArea. This will help you visualize whether the hit detection is being executed in the correct location.

   Debug.Log($"Attack Position: {_attackTransform.position}, Area: {_attackArea}");

4. Layer Masks:

   • Double-check that the attackableLayer is set correctly in the inspector. Ensure that the objects you want to hit are indeed on that layer.

5. Physics Settings:

   • Sometimes, the physics settings may impact the detection. Make sure that the Rigidbody2D component on your character has the correct settings (e.g., Gravity Scale, Collision Detection).

6. Alternative Hit Detection Method:

   • If you’re still having issues, consider using Physics2D.OverlapCircle for hit detection instead of OverlapBox, especially if your attack has a more circular motion. This could give you more reliable hit detection depending on your character’s attack animation.

   Collider2D[] objectsToHit = Physics2D.OverlapCircleAll(_attackTransform.position, _attackArea.x / 2, attackableLayer);

7. Animation Events:

   • If your attack animation has a specific frame where you want the hit detection to happen, consider using animation events to call the Hit method at the right time in the animation.

8. Collision Layers:

   • Ensure that the collision layers are set up properly in the Unity Physics settings (Edit > Project Settings > Physics2D). Make sure the layers are configured to interact as you expect.

By following these suggestions, you should be able to identify the root cause of the issue and correct it. If you’re still having trouble after trying these methods, feel free to share more details about your setup or any errors you’re encountering.

[Da]

Helpful?

Up

0

::

Yes, of course. Thank you for responding so promptly) It is divided into 3 parts, since the imgur is limited to 60 seconds.

View post on imgur.com

View post on imgur.com

View post on imgur.com

The video shows that the layers are installed correctly. The hitbox area is also visible. The recording of hits in different situations is shown. The problem is that hits are recorded very strangely when the character falls (the video shows that the hitbox hits the enemy’s layer, but hits are not recorded). What’s even stranger is that registration is completely normal during the jump and movement. The whole Internet has been crawling, but it’s like I’m the only one with this problem)

[Da]

Helpful?

Up

0

::

View post on imgur.com

1 Chapter

[Ser Apustaja]

Helpful?

Up

0

::

It seems like you’re encountering an issue with hit detection in your game when your character is falling. This can be a tricky problem to troubleshoot, but here are some common areas to investigate:

1. Hitbox Configuration: Ensure that the hitbox for your character is correctly configured for the falling state. Sometimes, the hitbox might change or not be active when the character is falling.

2. Physics Settings: If you’re using a physics engine, verify that the collision settings are consistent during falling. Check if the collision layers and masks are set up correctly, and ensure that both the character and the enemy are on the correct layers to interact.

3. State Management: Look at how you’re managing different states (falling vs jumping). It’s possible that the hit detection logic is being bypassed or altered when your character is in the falling state.

4. Debugging Hit Detection: Add debug logs or visual indicators that show when a hit is detected. This can help you see if the hit detection logic is being triggered but not registering hits as expected.

5. Gravity and Movement: Consider how gravity and movement are affecting the hitbox. If the character is moving too quickly while falling, it might be passing through the enemy without registering a hit. You might need to implement a raycast or continuous collision detection for faster falling objects.

6. Layer and Collision Settings: Double-check your layer-based collision settings. Ensure that your character’s hitbox and the enemy’s hitbox are configured to collide with each other in the physics settings.

7. Frame Rate Considerations: If your game has a variable frame rate, ensure that your hit detection logic accounts for frames where the character may fall through the enemy due to rapid movement.

If you could provide more details about the game engine or framework you’re using and the code related to hit detection, I’d be happy to help you troubleshoot further!

[Lukas Kazda]

Helpful?

Up

2

::

Hi! for testing purposes i would create another one of those attackable walls but much much taller and spawn my player gameobject at a higher position, so if i start the game the player object falls down along the wall for a few seconds which would give you a time frame to attack multiple times and see if hit detection is still inconsistant. maybe lower gravity settings for longer fall time frame. It for sure does not solve the problem, but it might help isolating whats causing the inconsistancy

• Terence

and 1 other person have upvoted this post.

[Da]

Helpful?

Up

0

::

Yes, it’s as you say. I set the gravity low and made the character fall. With it, the registration of hits works perfectly. But now the next question has arisen, why is this happening and how to fix it? And why then does the hit registration work when the character jumps. These points are not entirely clear to me, I would appreciate it if you would answer them.

[Da]

Helpful?

Up

0

::

There is an assumption that the “Attack” method should be called much more often.

[Da]

Helpful?

Up

0

::

Although, this would solve the problem of failure of the method itself. But this seems to be a different kind of problem.

[Lukas Kazda]

Helpful?

Up

2

::

When i was watching your clips i could spot some frames where the Physics2D.OverlapBox was drawn outside of the attackable walls. i mean those few frames where the player object goes from jumping into falling state

View post on imgur.com

i think, since it is so difficult to time with those small walls, you sometimes attacked while the OverlapBox was not overlapping with the attackable wall, which would mean no collider to detect

• Terence

and 1 other person have upvoted this post.

[Lukas Kazda]

Helpful?

Up

1

::

i tried to upload a image but i failed, i am new to forums >.< “the small red line = overlapbox” was supposed to be the description of the image xD

1 anonymous person

has upvoted this post.

[Da]

Helpful?

Up

0

::

Me too) Do you know how to solve this problem? (I understood about the intersection of the line and the collider itself, but usually it was clear that the attack should have passed, but it did not happen). There may be some other method. Or you need to make a collider. There is an idea, you can make the method work for a few seconds, and not just at the moment of pressing the button.

[Author]

Posts