 |
The delay is nec. to prevent artefacts. The light is not flipped off, but faded out, and during that time it still casts shadows, which get increasingly less strong until the light is really off. If the shadow is turned on in the same frame the light is extinguished, then the light will still casting a shadow from the holder for a few frames, which creates a noticable "blink" of the light holder shadow. |
|
|
Addendum: The delay between switching the light source and the shadow shouldn't be longer than it takes the light to fade, but also not shorter (or the shadow flickers briefly). For the hard shadows themselves there is not much that can be done, as shadows are binary - either on or off. If the projected shadow is a blend light, tho, then this light could be faded in/out instead of just being flipped on or off. That would hide the transition between the states. |
 |
The projected shadows should probably operate the same as the light itself. |
|
|
There are only two delays in tdm_lights.script - one for torches (500ms) and one for electric lights (50ms). If you see the issue primarily with moveable candles, maybe these just need their own delay, like 250 ms? If you play around with these constants in tdm_lights.script, it might be apparent what works better: // When a shadow is switched on/off, this delays the switch by so many ms: #define SHADOW_SWITCH_DELAY_TORCH 500 #define SHADOW_SWITCH_DELAY_ELECTRIC 50 There is also the issue that there is only one delay for turning on the light and for turning it off. It might be that one case needs a longer/shorter delay to look better. The real solution would be to figure out how long the light actually fades in/out and then to use that delay * 0.9 for the shadow transition. But this is complicated, as the light holder would need to figure this out for all attached flames/lights. |
 |
I believe this has been fixed, will check and close. |
|
|
This was fixed a long while ago. |
- Anonymous
