ZDoom

Hello GZDoom community hope everyone is good.

Quite a strange issue here, the newer GZDoom mods and TC have a startup log with 'AimingCamera 1: can't find TID 0' on the beta versions of GZDoom? Seems to still work correctly but I cant figure out how to fix this?

Anyone have any ideas on what's occurring here?

Thankyou for your time and hope to speak soon.

“The newer GZDoom mods” means nothing to us. Please name a few of them.

0 is not a valid tid, that's really all here. The mods are buggy.

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.

Disabled the warning for targets with zero TID.

Thanks for the replies much appreciated.

Sorry for asking but could the TID 0 camera log message cause any performance issues ie any micro stuttering or lag?

Thanks for explaining the issue clearly, I see that GZDoom beta is updated with this log disabled? So I guess that it doesn't actually cause any FPS issues?

Brilliant work as always! Thanks again.

ZDL_800 wrote:Sorry for asking but could the TID 0 camera log message cause any performance issues ie any micro stuttering or lag?

No, it cannot cause any performance issues.

That's great news! Thanks again, epic works!