# Bug when assign new image processing to material

**URL:** <https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524>\
**Category:** Bugs\
**Created:** [May 19, 2025, 10:41am UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524 "2025-05-19T10:41:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nwBen](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/nwben/32/46113_2.png) [@nwBen](https://forum.babylonjs.com/u/nwBen)\
**Post date:** [May 19, 2025, 10:41am UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524/1 "2025-05-19T10:41:54Z")

</div>

When a new image processing is assigned to a material, it is not applied unless the isEnabled variable is forced to change.

repro:

> **[Babylon.js Playground](https://playground.babylonjs.com/#2FDQT5%232953)**
>
> Babylon.js playground is a live editor for Babylon.js WebGL and WebGPU 3D scenes

Comment out lines 26 and 27 to see how the image processing does not change without the workaround.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [May 19, 2025, 3:09pm UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524/2 "2025-05-19T15:09:13Z")

</div>

cc @Evgeni_Popov

---

<div class="post-metadata">

**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\
**Post date:** [May 19, 2025, 4:09pm UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524/3 "2025-05-19T16:09:13Z")

</div>

Assigned @Evgeni\_Popov on May 19, 2025, 4:09pm UTC



---

<div class="post-metadata">

**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\
**Post date:** [May 19, 2025, 4:32pm UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524/4 "2025-05-19T16:32:30Z")

</div>

Thanks for reporting, this PR will fix the problem:

> <https://github.com/BabylonJS/Babylon.js/pull/16633>
>
> See https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-materi…al/58524

---

<div class="post-metadata">

**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\
**Post date:** [May 19, 2025, 4:32pm UTC](https://forum.babylonjs.com/t/bug-when-assign-new-image-processing-to-material/58524/5 "2025-05-19T16:32:33Z")

</div>

Unassigned @Evgeni\_Popov on May 19, 2025, 4:32pm UTC