If I place a unit on the map, and the unit happens to be placed 'on' a rock. After mission start the unit will be placed inside the rock. On the floor with the outside of the rock as walls.
Here is an example:
http://sacha.ligthert.net/screenshots/ARMA/3/feedback/arma3%202013-03-07%2001-06-52-863.png
http://sacha.ligthert.net/screenshots/ARMA/3/feedback/arma3%202013-03-07%2001-06-38-703.png
It is as if rocks aren't seen as physical objects. But this is detrimental to scripts that spawn units on the fly at random spots. If a unit ends up being trapped who knows what will happen.
This could possibly be related to the fish I've seen swimming through rocks in the diving showcase.
@Ligthert: Check whether a position returned by your randomizing script is occupied by any objects before spawning your unit. The findEmptyPosition command (http://community.bistudio.com/wiki/findEmptyPosition) might also be useful. Keep in mind, these suggestions are just a stop-gap - this is a serious bug and does need to be fixed.
nearestLocation [getPos player,"RockArea"]returns "No Location"
while "Hill" works
C:\Arma3 pbos\ui_f\a3\ui_f\config.cpp
class RockArea: Hill
{
texture = "\A3\ui_f\data\map\locationtypes\rockarea_ca.paa";
};
In the meantime I've discovered the same goes for large fuel tanks (these big verticle cylinders and) piers.