I recorded this while I was actively learning the new Havok integration. The useful discovery was exactly the kind of thing product documentation often misses: all the configuration can look correct while one unstated runtime condition keeps the tool from working.
Why I made this
Unity's Havok integration was a preview package tied to the early DOTS and Entities workflow. Getting from installation to a useful debugger session required several components, a particular simulation setting, and a separate analysis window.
The confusing failure appeared after that setup. The visual debugger repeatedly connected and disconnected with a timeout, even though the host, port, and Havok configuration looked correct. A developer could reasonably suspect the firewall or installation when the actual problem was that nothing in the scene had started the simulation.
What I did
I begin with the exact Unity beta version, enable preview packages, install Havok Physics, and show the dependencies it brings into the project. Then I create a configuration object with the Physics Step, Convert to Entity, and Havok Physics Configuration components.
I enable the visual debugger, open it from Unity's Analysis menu, and reproduce the timeout instead of cutting around it. I check the expected settings and then add a cube with a physics body, physics shape, and entity conversion.
Once that cube begins participating in the simulation, the debugger receives the scene successfully. The demonstration closes by walking back through the setup and showing how the same stack can support larger physics experiments and mobile VR.
The comments later confirmed the value of exposing that hidden step: developers reported that the walkthrough got them running when the available documentation had not made the path clear.
Chapters
Select a chapter to jump the video directly to that part of the workflow.
A note on the archive
This video uses Unity 2019.3 beta, preview-era DOTS and Entities components, and an early Havok package. Unity's ECS APIs, package installation, debugger workflow, supported versions, and Havok licensing have changed substantially since 2019.
Use current Unity and Havok documentation before trying it now. I’m keeping the recording because it includes the misleading timeout and the missing condition that finally made the debugger connect—the part another developer was most likely to need.