Why does the "Set Brightness" node not function properly?

Since all the lights had Brightness renamed to “Intensity” (no idea why), the blueprint node “Set Brightness” no longer has any effect, and there is no “Set Intensity” node either.

Can this be fixed?

If this doesn’t work, make sure your light is set to either stationary or movable - static lights can’t have their values changed during gameplay, as I’m sure you know.

Hi James,

I’ve just tested this with the following setup and everything is functioning as it should.

I’ve set two brightness levels through variables that are plugged into my Set Brightness node through a delay. After starting in PIE it will wait five seconds, turn the light brightness down to 0 then wait five seconds and turn the brightness up to 10000.

I hope this helps!

Tim

For some reason it doesn’t work in the construction script, but it does seem to work in the event graphs.

Hi James,

What version of the engine are you using. I’ve just setup this in the construction script and am not seeing an issue. I’ve set a variable that I can adjust in my details panel and it’s changed every time.

Here is my setup:

Let me know and I can look into this further.

Thank you!

Tim

Strange… I’ll post an image when I get back to the office on Tuesday!

Hey James,

I know you’re still looking at this, but for tracking purposes I’m going to mark this resolved. Once you test it and if you are still having the issue feel free to post.

Thanks!

Tim

Hi Tim,

When you use this in the construction script, does it change the default value in the components view? In mine it doesn’t, my Intensity in the Components view is still set to 5,000, even though I made the construction script change it.

Previously, it would change to match the new setting.

Thanks

I’ve not been able to get this to reproduce. I’ve only tested with the current 4.4.1 and 4.3.1 though. The components view are meant to be defaults that you can set though. If you’re changing the value via the set brightness whether using a variable or not this should not directly affect the components tab.

Maybe I’m misinterpreting what you’re talking about but I’m not sure. Is there a reason that this needs to change the components value as well when it’s never used if you’re setting the brightness via the construction script or the variable that’s plugged into the set brightness node?

It doesn’t have to really, it’s just that some properties that I drive through the construction script seem to progate over to the Components view, but others do not.

Even though I can change the values in the components view still, after the construction script runs they seem to change back. Things like Camera Spring-Arm lengths are a good example.