Trying my 2017.3 project in 2018.1 beta and getting terrible performance, it is all coming from FixedUpdate.PhysicsFixedUpdate
Inside Physics.Processing, various PhysX commands are causing huge ms spikes
I dont see these issues in 2017.3, still digging around to isolate what in-scene is causing it.
some culprits in deep profile, generally same as non-deep profile
PhysX.PxsContext.prepareCMDiscreteUpdateResults
PhysX.PxsDynamics.solverCreateFinalizeConstraints
PhysX.ScScene.broadPhase
PhysX.PxsSap.sapPostUpdateWork
I reported this as well. In my case it was caused by the rigidBody component. An otherwise empty scene will have the performance spikes if you drop that component in there. When I reported it back on 2018.1.0b4, I got pointed to the same issue number linked above. After a poke this morning, the QA team let me know that they’re aware it’s still present and are working on a fix.