Change Details

There are times where one might need to detect the height above the closest "walkable" surface at a position. One such application would be to create a "landing pad" for helicopters on top of another object. Using lineIntersectsSurfaces is not an option because it doesn't support the "roadWay" lod. The only solution at the moment is to: 1. Create a test vehicle 2. Transfer the test vehicle to the desired coordinates using setPosXXX 3. Using the (getPos _vehicle select 2) command to return the height above the surface. If there was a built in command that could return the same result without any need to create a unit, it would be more convenient and hopefully faster, because getPos has a relatively high execution time (~0.01-0.02 ms) which is even worse when combined with the whole process above.

As you know, units typically stand on the roadWay LOD, and if it doesn't exist, they stand on the GEOM LOD. So a command like this: `lineIntersectsSurfaces [top, bottom, objNull, objNull, true, 1, "ROADWAY", "GEOM"] ` can give the next surface where you can stand on. It is very useful when you want to place something on top of another object.

There are times where one might need to detect the height above the closest "walkable" surface at a position.As you know, One such application would be to create a "landing pad" for helicopters on top of another object. Using lineIntersectsSurfaces is not an option because it doesn't support the "roadWay" lod. The only solution at the moment is to: 1units typically stand on the roadWay LOD, and if it doesn't exist, they stand on the GEOM LOD. Create a test vehicleSo a command like this: 2.`lineIntersectsSurfaces [top, bottom, objNull, objNull, true, 1, "ROADWAY", Transfer the test vehicle to the desired coordinates using setPosXXX"GEOM"] ` 3. Using the (getPos _vehicle select 2) command to return the height above the surface. If there was a built in command that could return the same result without any need to create a unit, it would be more convenient and hopefully faster, because getPos has a relatively high execution time (~0.01-0.02 ms) which is even worse when combined with the whole process abovecan give the next surface where you can stand on. It is very useful when you want to place something on top of another object.