Unity Bug

Invalid effector for CustomOverlay attribute

Daniel 1 month ago updated 1 month ago 2


I had a similar issue with Bolt that does not appear anymore but now its seems to be related to PEEK and you can see the thread on Bolt here:


This the new error that is very similar to the one I saw in the past that was related to Bolt( before I upgraded Bolt + Peek to the latest version)

Invalid effector for CustomOverlay attribute.
System.Attribute:GetCustomAttributes(MemberInfo, Boolean)
Ludiq.PeekCore.AttributeCache:.ctor(MemberInfo) (at Assets/Ludiq/Ludiq.PeekCore/Runtime/Reflection/AttributeUtility.cs:90)
Ludiq.PeekCore.AttributeUtility:GetAttributeCache(MemberInfo) (at Assets/Ludiq/Ludiq.PeekCore/Runtime/Reflection/AttributeUtility.cs:361)
Ludiq.PeekCore.AttributeUtility:HasAttribute(MemberInfo, Boolean) (at Assets/Ludiq/Ludiq.PeekCore/Runtime/Reflection/AttributeUtility.cs:450)
Ludiq.PeekCore.<>c:b__0_0(Type) (at Assets/Ludiq/Ludiq.PeekCore/Editor/Interface/Annotations/AnnotationDisabler.cs:13)
Ludiq.PeekCore.AnnotationDisabler:DisableGizmos() (at Assets/Ludiq/Ludiq.PeekCore/Editor/Interface/Annotations/AnnotationDisabler.cs:13)
Ludiq.PeekCore.UpdateWizard:Initialize(IEnumerable`1, Product) (at Assets/Ludiq/Ludiq.PeekCore/Editor/Windows/UpdateWizard/UpdateWizard.cs:41)
Ludiq.PeekCore.UpdateWizard:Show(IEnumerable`1, Product) (at Assets/Ludiq/Ludiq.PeekCore/Editor/Windows/UpdateWizard/UpdateWizard.cs:24)
Ludiq.PeekCore.UpdateWizard:Show() (at Assets/Ludiq/Ludiq.PeekCore/Editor/Windows/UpdateWizard/UpdateWizard.cs:18)
Ludiq.Peek.PeekProduct:HookUpdateWizard() (at Assets/Ludiq/Ludiq.Peek/Editor/Plugin/PeekProduct.cs:64)

Unity Version:
Peek Version:
Unity Bug

Hi Daniel,

Sorry for the delay and thank you for the bug report.

I've investigated and I was able to reproduce this.

It seems like a Unity Bug. Their [CustomOverlay] attribute in the Animation Rigging package logs an error when its parameter type is invalid. I was not able to infer why that happens though, as it only seems to be in use once in their source, and on a valid type.

Regardless, I've submitted a minimal bug report to Unity so they can have a look:


In the mean time, rest assured that this should have no impact whatsoever on Peek (or Bolt's) functionality. It's not even an exception (just an error that gets displayed), so nothing gets interrupted by this bug.

Hey Lazlo,

Thank you for investigating! 

Yeah, it hasn't been directly impacting my work but definitely annoying to always have an error popping up like that. I try to keep my projects free of errors or warnings!

Hopefully, Unity will be able to tackle that problem soon!

I didn't know Unity have a fogbugz account. Is that the way we are supposed to report Bolt bugs from now on?

Thanks for the help!