# The Slate.ApplyDisabledEffectOnWidgets not works for RetainerBox children

**URL:** <https://forums.unrealengine.com/t/the-slate-applydisabledeffectonwidgets-not-works-for-retainerbox-children/2437491>\
**Category:** UI\
**Tags:** unreal-engine, Rendering, question\
**Created:** [April 3, 2025, 10:40am UTC](https://forums.unrealengine.com/t/the-slate-applydisabledeffectonwidgets-not-works-for-retainerbox-children/2437491 "2025-04-03T10:40:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pingleconsoledev](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/pingleconsoledev/32/1008762_2.png) [@pingleconsoledev](https://forums.unrealengine.com/u/pingleconsoledev)\
**Post date:** [April 3, 2025, 10:40am UTC](https://forums.unrealengine.com/t/the-slate-applydisabledeffectonwidgets-not-works-for-retainerbox-children/2437491/1 "2025-04-03T10:40:03Z")

</div>

Hi everyone,

We have encountered a rendering issue involving `RetainerBox`. It seems that child widgets rendered inside these containers do **not retain the `IsInGameLayer` flag** during the rendering process. As a result, even when the CVar `Slate.ApplyDisabledEffectOnWidgets` is set to `false`, **the `DisabledEffect` draw flag is still applied** , causing unwanted opacity on disabled elements.

This behavior makes it impossible to rely on `Slate.ApplyDisabledEffectOnWidgets=0` in combination with RetainerBox-based UI (for example, when using RetainerBox for effects), since disabled elements still appear semi-transparent.

Is this the intended behavior?  
Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![fpwong](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/fpwong/32/1194512_2.png) [@fpwong](https://forums.unrealengine.com/u/fpwong)\
**Post date:** [April 12, 2025, 4:01am UTC](https://forums.unrealengine.com/t/the-slate-applydisabledeffectonwidgets-not-works-for-retainerbox-children/2437491/2 "2025-04-12T04:01:25Z")

</div>

+1 for this, I have noticed this happening on UE5.4
