 |
If I run through a location and exit it while the ambient light is fading from one color to another, I'm left with whatever the value was when I exited the location. So it appears to just stop updating when there's no new location entity to take over the fade. There needs to be some default code that recognizes there's no location entity in the area the player is stepping into. Then the code would fade from the current ambient to ambient_world's color. |
 |
Not including an info_location entity in a location is a serious mapper error, as most settings are suddenly undefined, including the "in which location are we actually" setting. This not only happens to ambient light, but also to the ambient music. Failing gracefully would of course be an idea, but maybe it would be even better to notify the mapper somehow of the problem? The color value cannot be used from the ambient_world light (it was already changed), instead the stored default value must be used. It is doable. |
|
|
Please find attached a testmap, and a new tdm_location_settings.script, which fixes this issue. The testmap has an undefined location to the far right, if you enter it, the red ambient will fade to black, and back to red if you leave again. The console will output these events (invalid/valid zone). The attached patch and script are based on bug 03859, and they also fix 3859, plus another issue when starting in an invalid zone, or in a zone with "no_ambient_light_fade" "1". |
- Anonymous
