JG4_Deciman Posted October 9, 2020 Posted October 9, 2020 Hi there According to whatever I've found the AType:8 should be logged whenever a mission objective was touched (completed or failed) My logs show the following line: T:23883 AType:8 OBJID:863 POS(317124.0938,26.6398,285962.5313) COAL:3 TYPE:1 RES:1 ICTYPE:0 Usually that would mean: Objective with ID 863 was triggered, and everything else is not important here Strange thing is: In the mission file (.Mission), the id 863 is used by a 'MCU_TR_Media' and that media was never triggered. And the mission itself behaves like it should... Could it be that either the dServer or the mission editor is renumbering in 2 different ways? The procedure was the same on every test (and I've made several) Opening the mission (editor) Saving with new name Closed Mission Editor (was not asked to save again) Loading the new generated .msnbin with the dServer and compared the logfile with the .Mission file by hand (text editor, not opened with mission editor again) Deci
JG4_Deciman Posted October 10, 2020 Author Posted October 10, 2020 Ok, it's getting even stranger.... Assuming the dServer is creating it's own 'id' for every unit what makes searching for any id inside the mission file useless next try was the position (x,y,z) available for the objective inside the mission file AND inside the dServer logfile. But they are also different. Not much different, but different enough to cause problems even when using math.round... Deci
coconut Posted October 10, 2020 Posted October 10, 2020 Numerical identifiers change every time a mission is loaded, making them in effect useless in the logs. for the purpose of communicating info to an external script from a mission, you can instead damage some non-neutral entity that you hide somewhere far from the action, and that has a unique name.
JG4_Deciman Posted October 11, 2020 Author Posted October 11, 2020 Thanks. Nice workaround, indeed... Deci
JG4_Deciman Posted October 13, 2020 Author Posted October 13, 2020 Ok, finetuning. Use 'unique named objects' (tested with fake-vehicles, too) Set entity AND set INVULNERABLE (lets them spawn without further damaging even inside forests or buildings) Set 'enabled' OFF Let them spawn when you need a log entry, only To generate a log entry damage them some seconds later Let them despawn afterwards. So they need no resources except the few seconds they are active and there is no need to hide them. Logfile shows entry for spawning (AType:12) with the unique name but entry will be shown only if unit was damaged or killed. Deci
1CGS -DED-Rapidus Posted October 27, 2020 1CGS Posted October 27, 2020 @JG4_Deciman, only events write to the logs: player's respawn (atype:10), game object's respawn when it is affected (atype:12) , take-off, (atype:5) and landing (atype: 6)- active events, if there is a need to pass to the logs about the triggering of some trigger in the game world, objects are used(for example, an airplane hitting the check zone). ID objects have the same numbers as block_array.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now