I have a very large dependency tree and Unity is failing trying resolve a dependency somewhere in this huge dependency chain. I'm having to manually look through all the dependencies to work out what might be missing, which is a huge task.
Unfortunately, unity only reports the item it's trying to construct in the exception it throws and gives no info about the route it has taken to get to that point.
Does Unity put out any tracing/logging info that might help me work out exactly what dependencies I am missing?
Path tracing is a ray tracing algorithm that sends rays from the Camera and, when a ray hits a reflective or refractive surface, recurses the process until it reaches a light source.
In Unity, you can use the Sprite Renderer to render sprite-type images in either a 2D or 3D scene. This component lets you display images as Sprites for use in both 2D or 3D scenes.
If your project is 2D, you'd be better served with URP. The trade off basically is HDRP has more graphical features built-in, comes with the engine and isn't held back by weak platforms such as mobile. Performance requirements are a bit higher. Development is a lot faster compared to URP.
There is no Tracing implemented in Unity.
The ResolutionFailedException
, that is thrown by Unity when an attempt to resolve a dependency fails, contain all relevant information whether in its Title
, StackTrace
or InnerException
property.
Normally does the most InnerException
contain the root cause of the ResolutionFailedException
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With