Ok very interesting and helpful stuff.
The “Tick When Offscreen” did indeed work (huzzah!). That would be a fine fix as we’re using this widget in tight circumstances and are already heavily managing its enabled/disabled state.
Looking at it further however, we have indeed disabled occlusion culling (which is a bit surprising to me) and so enabling that also fixes the problem. That feels like the better fix to me but I’ll have to check in with the team in case there was some particular reason we’d turned occlusion culling off.
I think we can consider this fixed tho. Both your suggestions are viable solutions. thx! 