Adding Megascans 3D objects to a scene can cause Twinmotion to freeze and Crash on macOS.

Looking at the logs when it happened, the logs are spammed with the following:

[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Unreal Zen Storage Server HTTP service at [::1]:8658 status: OK!.
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Local ZenServer status: Healthy. Skipping recovery
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Unreal Zen Storage Server HTTP service at [::1]:8658 status: OK!.
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Local ZenServer status: Healthy. Skipping recovery
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Unreal Zen Storage Server HTTP service at [::1]:8658 status: OK!.
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Local ZenServer status: Healthy. Skipping recovery
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Unreal Zen Storage Server HTTP service at [::1]:8658 status: OK!.
[2024.12.10-20.34.12:438][514]LogZenServiceInstance: Display: Local ZenServer status: Healthy. Skipping recovery

{{The message appears multiple times within a millisecond}}

The hang is totally random, but it happened to me twice yesterday. To reproduce:

1. Launch Twinmotion and open new scene
2. Sign in with your Epic account
3. In the Megascans 3d asset library, load any 3D asset
4. Add the asset to the scene == Twinmotion can hang