Lifelike actions and reactions - adding physics to your game

Рет қаралды 9,372

6 ай бұрын

From advanced 3D open worlds to the smallest 2D title, all games need physics to give them weight. In this video, Nicolas Borromeo and Vera Mommersteeg dive into Unity’s physics solutions for common use cases as well as challenges such as ghost collisions, tunneling, and unexpected bounces. You learn more about choosing and using NVIDIA PhysX, Unity Physics, or Havok Physics for Unity - and see how creators are integrating physics in their games.
Speakers:
Nicolas Borromeo, Senior Software Development Consultant, Unity
Vera Mommersteeg, Senior Physics Developer, Unity
#unity #gamedev

Пікірлер: 18

@dreamisover9813 5 ай бұрын

It's really nice that newer unity versions have that contact event

@unlockener 6 ай бұрын

Great video 👍

@Sharpyveyron 6 ай бұрын

How do u get on unity when the comferm email continue buttons doesn't work

@SuperZymantas 6 ай бұрын

standar unity :D

@NibbleByte 6 ай бұрын

Now I know what each collision detection mode does. It's not rocket science. Only physics science. :D

@lightbug6103 6 ай бұрын

17:47 The code on the left is not a good example. That code overrides the contact normals of all valid (a.k.a hasModifiableContacts == true) pairs. I've seen examples like that all over the internet, and even in their documentation page. The correct way of dealing with contact modification stuff per object is by checking if "this" object (the one with the script) belongs to the pair or not. If so, then do whatever you want.

@tryfinally 6 ай бұрын

Subscribing to the ContactModifyEvent once and processing contacts in batch is OK and much more performant than having every object in your game subscribe separately and process the entire contact list looking for the one relevant contact.

@lightbug6103 6 ай бұрын

@@tryfinally Yes you are right, that's why i said "per object" . What i really mean is that, if you want to use it as just another OnCollisionXXX message, then you need to identify the pair beforehand, unless you want to affect external pairs for some reason. The problem with some of these examples is that people might look at this "new" event and think it is similar to OnCollisionXXX. A better option would be having a dedicated system/controller that could handle each pair, and then notify each of the bodies separately in the same way OnCollisionXXX/OnTriggerXXX does. In my case, I have a custom OnContactModify callback which gives me the "other body" id, the current physics scene, and the pair. And like you said, it is a LOT faster when you have lots of bodies.