pcc 14 Posted March 23, 2017 Spoiler Error in expression <WestUnits> Error position: <WestUnits> Error Undefined variable in expression: westunits Error in expression <EastUnits> Error position: <EastUnits> Error Undefined variable in expression: eastunits Clean warfare doesn't generate the errors. But if I call it from my mission it gets errors even with unmodified file from warfare2.pbo [] Call Compile PreprocessFileLineNumbers ("Common\Config\Config_Teams.sqf"); Warfare OA Config_Teams.sqf, doesn't generate errors. Share this post Link to post Share on other sites
opusfmspol 273 Posted March 24, 2017 EastUnits, WestUnits and ResistanceUnits is an error that comes from Common_GetUnitData.sqf. It results when no structure type can be identified for a unit (i.e., what should be returned as "EastBarracksUnits" returns as "EastUnits" instead, no structure identified). It's caused by a few different factors. One is where certain units passed by the Team & Squad configs are not defined in the factory configs. The error occurs each time they try to get data on an undefined unit. Because the unit is not listed in a structure config, no structure type can be returned. Examples from non-beta Warfare: Example 1: - ZSU_CDF is not defined in the CDF heavy config. - ZSU_CDF is listed in CDF Team "MechanizedHeavyAA". - "MechanizedHeavyAA" is twice listed in CDF Squad "LargeAALightTankSquad". Result: 3 WestUnits errors Example 2: - RU_Soldier_Sniper is undefined in RU barracks config. - RU_Soldier_Sniper is twice listed in RU team "Sniper". Result: 2 EastUnits errors Example 3: - There is no such unit as "Ins_Soldier". - Ins_Soldier is listed in INS team "Sniper". Result: 1 EastUnits error Correcting the missing and misidentified units in custom configs will clear continuing errors in a mission, but the few core errors at startup will persist since core will run before custom. Another cause is that the factory config check is case sensitive. If a Unit is not listed in the Team or Squad configs with the exact same case text as in the factory config, the check fails. Those errors are cleared by correcting the case text wherever the unit is listed in the Team or Squad configs. The last cause should be non-beta only. if winged aircraft units are added to any of the Team or Squad configs, GetUnitData checked the Barracks, Light, Heavy and Aircraft factory configs, but not the Winged Aircraft (airport) config. Adding the check of "WingedAircraft" to the list cleared the error. It was fixed in beta. 1 Share this post Link to post Share on other sites