[SOLVED] OnBecameVisible & OnBecameInvisible require Renderer component?

Question
Do the OnBecameVisible & OnBecameInvisible GO events require the GO to have some kind of Renderer component? The documentation gave me the impression that it is required, but I wanted to be sure.

 

From:
http://docs.unity3d.com/ScriptReference/MonoBehaviour.OnBecameVisible.html

Yes, it needs a renderer attached.

Honestly, how would an object become visible/invisible if it didn't have a renderer? It's the renderer that renders it, giving it something that could be considered 'visible'.

 

@lordofduct
I wasn't sure because my area of expertise has always been shaders, and I haven't done much with the scripting side of things. Unity does have more than a few odd behaviors, so I thought it better to check.

 

Understandable.

The unity API can be a bit wonky at times.

I tend to always keep a generic 'test' project around that I can go in and just slap together basic code to test things if I don't know, or the wording is a little confusing. Heck often when answering questions on here for other people, that's really what I'll do first to confirm my answer is correct before posting it.

 

The UI components are rendered/visible but its renderer does not inherit from Renderer. So they don't fire the OnBecameVisible/Invisible events.

 

Any similar function for UI?

 

+1 Would be nice to have a callback function if a UI element is visible or not (especially for those UI element outside a scroll View Mask)

 

A callback for UI visibility and invisibility would be extremely helpful as @eltrexx has mentioned. Any ideas as to how to handle checking for if a UI element is hidden behind a mask?