by AFADoomer » Wed Aug 26, 2020 5:59 pm
This error shows up since
this commit back in May.
Up until that time, the warning had been commented out for about 10 years (since
SVN r2973), and was carried over into ZScript still commented out.
Based on the SVN commit, I think the intent of having it commented out was so that there would be no error message if the aiming point was established after the camera was spawned (the commit note says so that it can target players, who can't spawn with a TID).
The warning is correct, but at least a few mods (Blade of Agony was one) used AimingCamera where they should have used SecurityCamera, since AimingCamera previously worked without visible problems or error messages. I can imagine that someone also used it once upon a time for the case described in the SVN commit, where it aimed to follow a player whose TID was set after spawn via ACS.
This error shows up since [url=https://github.com/coelckers/gzdoom/commit/0631670a66800c7af47ac06e434b363c101620c6]this commit[/url] back in May.
Up until that time, the warning had been commented out for about 10 years (since [url=https://github.com/coelckers/gzdoom/commit/18205c82a605f987e9cb90bcb939c1ff7e6ba8e5]SVN r2973[/url]), and was carried over into ZScript still commented out.
Based on the SVN commit, I think the intent of having it commented out was so that there would be no error message if the aiming point was established after the camera was spawned (the commit note says so that it can target players, who can't spawn with a TID).
The warning is correct, but at least a few mods (Blade of Agony was one) used AimingCamera where they should have used SecurityCamera, since AimingCamera previously worked without visible problems or error messages. I can imagine that someone also used it once upon a time for the case described in the SVN commit, where it aimed to follow a player whose TID was set after spawn via ACS.