Issue with Physicc2D performance on 2022.1

A BoxCollider2D creates a single physics shape, a PolygonCollider2D can create lots even hundreds so it's not surprising.

I suspect you're not moving anything then because these are Static and should never be moved. If you are moving them then it's the absolute worst thing you can do. You should learn how to use the physics system correctly here which is that Rigidbody2D move, Colliders are just along for the ride. Modifying a Transform is doing 2D physics wrong and doing this cause the colliders to be recreated completely.

Are you running the physics per-frame because you state per-frame time and physics normally runs during the fixed-update. Also, stating the total time taken for the "frame" isn't useful in this context if you're making the statement that physics is causing this. What is the proof i.e. what specific part of the simulation step is taking longer? Presumably you know this because you're stating it's 2D physics that's taking the extra time. Is it finding contacts, resolving contacts, something else?

Also note, the profiler frame you show is the fixed-update running twice because Unity decided that game-time was lagging. This calls everything in fixed-update twice; scripts, animation, physics, everything so it's showing double the time.

 

You've still not stated what is taking more time, simply that you are sure it's 2D physics.

I don't have the project, you do so you have all the info. Asking me questions as if I can somehow tell you what is going wrong isn't realistic. You need to provide some information for me to comment on.

So again, what is taking more time specifically?

 

Answered separately. First, as I've said, if you're modifing a Transform then you're doing it wrong. That's what all those unnecessary SyncTransforms are. Add a Rigidbody2D and change its position/rotation. The colliders won't need to be recreate then and no sync-transforms will happen either. If you're explicitly controlling it then use a Kinematic Body-type because this is exactly what it is for. If you want contacts between Kinematic/Kinematic or Kinematic/Static calculated then use Rigidbody2D.useFullKinematicContacts and then ask for the contacts using the GetContacts call. That said, this answers your question as to how to get contacts but I have no idea what you're doing so no idea if this is appropriate. Using a Rigidbody2D if you ever intend to move is exactly what you should be doing though.

 

You're being critical of me when you're simply not following that showing me the total current time taken gives me no information whatsoever as to what part under it was taking less time before.

So in short, my answer is that I don't know how to help you unless you can tell me what part under the simulation is taking more time as I've asked above.

 

I've just seen that you've now reported my reply as being "passive aggressive"! I am trying to get you to understand that what you're providing doesn't give me any information to help you.

If you don't believe I'm trying to get more information to help you then I think it's best for me to leave this conversation here which is a shame.

 

It is now my evening, I am spending my personal time trying to help you and you are doing nothing but being critical of both myself and Unity Employees.

I do not know why you are being so aggressive. I have only asked you for more information above.

I have above when I asked what part of the physics update is taking more time than before. Each item under it is a specific part of the engine. As I've said a few times now, knowing what the total time is now and not what it was before doesn't give me any clue as to what is taking more time.