Engine icon indicating copy to clipboard operation
Engine copied to clipboard

Bug: Env_projectedtextures do a fade in on first turn on.

Open TheEnderek0 opened this issue 5 months ago • 1 comments

Describe the bug

The color transition time in pre-clustered projected textures was specified in seconds, but after the update it got re-interpreted as color transition speed, instead; making the keyvalue act as a some sort of "how fast does the color change".

It also affects the turn on and turn off inputs, which I guess is cool, but it might break backwards compat (it did for me), as previously it only affected changing the Light Color keyvalue

To Reproduce

  1. Open a map with projected texture
  2. Try to turn it off/on, messing with the color transition time keyvalue

Issue Map

Expected Behavior

Behaviour of color transition time should be changed to match from before the update. If someone wants to do fade in / fade out, they can do so by setting the Light Color kv to X X X 0, and it'll fade out (then disabling the ptex by firing TurnOff), same goes for fading in but in a reverse order.

Operating System

No response

TheEnderek0 avatar Jul 15 '25 17:07 TheEnderek0

Update: It seems that this kv is fine, but ptexes do fade in on the very first time you fire TurnOn at them (being turned off by default)

TheEnderek0 avatar Jul 15 '25 18:07 TheEnderek0