Search Issue Tracker
By Design
Votes
0
Found in
2022.3.7f1
2023.1.9f1
2023.2.0b5
2023.3.0a1
Issue ID
UUM-46927
Regression
No
Material conversion workflow is logging warning during indexation
In the URP package, the material conversion workflow used during asset indexation can log warning if some properties are not found. Problem is there can be a lot of logs that clog up and pollute the user console (and these logs are not actionable).
I suggest the logs are only printed in the log file and not sent to the console (or remove completely).
For reference this logging happens in:
public static object GetMaterialFromMethod(this MethodInfo method,
Object obj,
Func<string, string, string> generateErrorString)
{
object result = null;
try
{
result = method.Invoke(obj, null);
}
catch (Exception e)
{
// swallow the missing method exception, there's nothing we can do about it at this point
// and we've already checked for other possible null exceptions here
if ((e.InnerException is NullReferenceException))
{
Debug.LogWarning(generateErrorString(method.Name, obj.name));
}
else
{
throw e;
}
}
return result;
}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.