# vtkActor SetDiffuseColor bug
**URL:** https://discourse.vtk.org/t/vtkactor-setdiffusecolor-bug/8254
**Category:** Development
**Created:** [April 10, 2022, 8:34pm UTC](https://discourse.vtk.org/t/vtkactor-setdiffusecolor-bug/8254 "2022-04-10T20:34:47Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@BlueKnight7](https://discourse.vtk.org/u/BlueKnight7)
#### Post date: [April 10, 2022, 8:34pm UTC](https://discourse.vtk.org/t/vtkactor-setdiffusecolor-bug/8254/1 "2022-04-10T20:34:47Z")
I’ve taken the ImplicitBoolean example and “merged” it with the SolidClip example.
From the SolidClip example there are 2 parts to the clipping: a clip away portion and a portion that stays – using a vktClipPolyData object. From these 2, actors are created. When the color for the clippedAwayActor is set with SetDiffuseColor, the color appears as expected. When the color for the sActor (the portion that stays) is set with SetDiffuseColor, that part is set as blue when it should be hot pink. There are no error messages. This makes no sense to me. I think that I did everything correctly. Files available:
[ImplicitBooleanClip.cxx](https://discourse.vtk.org/uploads/short-url/iE6AHCxUHgbBXGs3ZgjmoidKZwA.cxx) (3.4 KB)
[CMakeLists.txt](https://discourse.vtk.org/uploads/short-url/gQlbUqSnGfk4Cw6dPPw2ACorDyD.txt) (1.2 KB)
Bug or not? Misunderstood feature?
---
### Author:  [@BlueKnight7](https://discourse.vtk.org/u/BlueKnight7)
#### Post date: [April 11, 2022, 12:19am UTC](https://discourse.vtk.org/t/vtkactor-setdiffusecolor-bug/8254/2 "2022-04-11T00:19:13Z")
My apologies. Not a bug.
Didn’t realize that I needed to execute ScalarVisibilityOff() on the mapper to override whatever data is present and taking priority.