Jump to content

Forums

  1. Welcome

    1. Announcements / News

      The latest. What is happening with 0 A.D. Stay tuned...

      5,4k
      posts
    2. Introductions & Off-Topic Discussion

      Want to discuss something that isn't related to 0 A.D. or Wildfire Games? This is the place. Come on in and introduce yourself. Get to know others who are using 0 A.D.

      38,6k
      posts
    3. Help & Feedback

      Here is where you can get help with your questions. Also be sure to tell us how we are doing. What can we improve? What do you wish we could do better? Your opinion matters to us!

      16,9k
      posts
  2. 0 A.D.

    1. General Discussion

      This is the place to post general stuff concerning the game. Want to express your love for hoplites or find people to play the game with? Want to share your stories about matches you have played or discuss historical connections to the game? These and any other topics which are related to the game, but don't have their own forums belong in this forum.

      51,1k
      posts
    2. Gameplay Discussion

      Discuss the game play of 0 A.D. Want to know why the game plays the way it does or offer suggestions for how to improve the game play experience? Then this is the forum.

      28,1k
      posts
    3. Game Development & Technical Discussion

      A forum for technical discussion about the development of 0 A.D. Feel free to ask questions of the developers and among yourselves.

      48,3k
      posts
    4. Art Development

      Open development for the game's art. Submissions, comments, and suggestions now open.

      30,3k
      posts
    5. Game Modification

      Do you have any questions about modifying the game? What will you need to do what you want to? What are the best techniques? Discuss Modifications, Map Making, AI scripting and Random Map Scripting here.

      45,7k
      posts
    6. Project Governance

      Forums for decision-making on issues where a consensus can't be reached or isn't sufficient. The committees are chosen from among the official team members, but to ensure an open and transparent decision process it's publically viewable.

      148
      posts
    7. 597
      posts
  • Topics

  • Posts

    • We don't decompose the collision vector. We calculate the resulting impulse from the contact normal, and the spin actually comes from calculating the torque given the impact position to the center. Since the shape is (almost) a rectangle, then it's just about calculating the lever effect on a axis - the contact point projected on it.  Velocities are also calculated based on this closest point. I think to apply your idea it would be to add a scaling to the lever effect? But I'm not sure it's always desirable, for example on the choke point wouldn't that create more units facing the wrong direction of movement?
    • @Atrik maybe you consider something already, I haven't delved deep enough into the code. In collisions, you would have radial and perpendicular components, the last one making the body rotate. Is that last one also scaled by relative velocity? I thought only the first one. But even if both are, their scaling could be treated differently, and what I'm saying is that if the perpendicular component were to depend even more strongly on relative velocity, it would rotate static objects blocking the way more easily, while (hopefully) not affecting those marching shoulder to shoulder, which are the problems mentioned. I'm not sure how it would behave if objects collided head on (high relative velocity), but the dependency could be defined in a way that the resulting behaviour is also what is wanted.
    • Wait, but I told you it does for collision, just not for the 'soft' push who are mostly meant to keep units apart more then simulating a collision. So for 'soft' pushs you don't really want to scale it down with velocity. It's not so much about complexity you even tried yourself it's just less then 10 lines of codes, less if we refactor with the one for collision. But why would it help rotation here?
    • I see, it was even more constrained than the case of me pushing that elephant in the open. It all comes down to their resistance to rotate, and how messing with that messes with other things. Seems the only solution is "taking into account the relative velocity" between them, but I guess you didn't want to complicate the code with that.    
×
×
  • Create New...