Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business


OverviewFelgo 3 Support (Qt 5) › Fixiture.beginContact(Fixture other, point contactNormal) Bug

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #15599

    Felgo User

    The documentation says:

    The <i>contactNormal</i> vector contains the information if the 2 objects collided on the horizontal axis (if contactNormal.x is 1 or -1) or on the vertical axis (if contactNormal.y is 1 or -1). The non-affected axis will be 0.

    but the real value is not the contactNormal, seem It’s the contactPoint


    Felgo Team

    Felgo User

    Well, the problem is that when I say


    fixture.onBeginContact: {



    The log prits something like QPointF(-25.3125, 0)

    The x value moves from -25.3125 to 25.3125 depending on the position of the objects and de direction of the collision.

    the y value is always 0.

    any idea of what I’m doing worng?


    Thank you


    Felgo Team


    As the value for the contact normal directly comes from Box2D it could be possible that the values you receive are just how Box2D works in your specific use-case. For example, the y-value is 0 if your object e.g. collides with a vertical wall.

    If this is not the case in your game it is hard to tell what is going wrong. You can prepare a small code-example for us in that case so we can do some more testing to see if we can identify the problem.


Viewing 4 posts - 1 through 4 (of 4 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded