Troubleshooting
Tips on how to handle common problems
On macOS, some versions of the Unity Hub don't install platform modules properly. This issue is fixed on version Unity Hub version 3.3.0. If you want to use a prior version, install one module at a time.
SDK 0.9 release removed dependency to the experimental package Platforms. As a result, your existing BuildConfiguration assets will have its defining script missing. To recreate the Simulator build configuration with the new pipeline, you can do it from the Simulators Module in coherence Hub.
- When networked Entities are added by loading a scene additively, mind that the
CoherenceMonoBridgemust be set to a singleton mode. In case of a non-singleton MonoBridge the Entity will search for a MonoBridge instance within its scene, and if none is found it will be created in that scene. This applies to bothCoherenceSyncandLiveQueryobjects. - For a complete control over
CoherenceMonoBridgeresolving you can use eitherCoherenceSync.MonoBridgeResolveinstance event orMonoBridgeStore.MonoBridgeResolveglobal event. ACoherenceMonoBridgeinstance provided by theMonoBridgeResolveevent takes precedence over the scene and singleton ones.
- Sometimes packages cache gets stalled and after updating the coherence package you might find Unity still uses the old package version. Try
Reimport allor closing the project, deleting theLibraryfolder, and reopening the project again. It will clean and update packages cache, and use the version of coherence stated inmanifest.json.
If you run into issues that are not mentioned here, take a look at our Known Issues list at the end of Release Notes.
Last modified 2mo ago