Possible bug with TTmod_addTrigger(GeoID...
Posted: 08 Sep 2018, 05:45
I have just started using the addTrigger (thank you very much btw, very helpful), and have now run into this a few times where it doesn't seem the GeoID is properly being converted to the correct X, Y and Z coordinates, specifically the Z coordinates.
Here's an example of two attempts at adding a trigger based on a GeoID
I have had success using the actual X, Y, and Z coordinates but for this specific instance, I only have the GeoID.
The documentation states:
Here's an example of two attempts at adding a trigger based on a GeoID
Code: Select all
INFO 2018-09-08 05:43:48.015 {02} <TTmod_addTrigger> [96974] TTmod | Registered new trigger at position 1856 1196 0 with radius 12
INFO 2018-09-08 05:43:48.015 {02} <TTmod_addTrigger> [96974] TTmod | Registered new trigger at position 476 1032 0 with radius 12
The documentation states:
Thank you in advance!%position
“X Y Z” position or GeoID of the trigger center