Briggybros

Hello, this update appears to have broken the behaviour of "inArea" and "inAreaArray" when testing against hexagonal areas. _cube = "Land_VR_Shape_01_cube_1m_F" createVehicle [0,0,0]; _inCircle = _cube inArea [ [0,0,0], 5, 5, 0, false ]; _inHex = _cube inArea [ [0,0,0], -5, -5, 0, false ]; hint format ["in circle: %1\nin hex: %2", _inCircle, _inHex]; The above will hint: on the main branch, but: on the profiling branch

Hello, new to this, but I've been attempting to create a new plane class that is a modification of an existing aircraft config - following https://community.bistudio.com/wiki/Arma_3:_Vehicle_Loadouts#vehicle_config_-_CfgVehicles and https://community.bistudio.com/wiki/Class_Inheritance#External_Base_Child_Classes The new B_A_Plane_Fighter_05_CAS_F works as I would expect, but the original B_A_Plane_Fighter_05_F spawns empty, and pylons are no longer configurable in attributes. Looking at the pylon classes in the config viewer there appears to be no difference in config when the above is included and when it isn't. Am I missing something obvious here, or do pylons just not play well with inheritance and need to be completely redeclared as in the CfgVehicles wiki page?