Sites: Estimate terrain objects bounding box overlap with site for hiding rocks etc

[dijksterhuis]

TL;DR stop mortars spawned inside rocks soft locking a zone by removing ROCK/ROCKS/HIDE terrain objects with a bounding box estimation.

Estimates whether nearby terrain objects will overlap/intersect with the spawned site, then hides them. Also hides any terrain objects directly on top of those found with bounding box search, otherwise we end up with a bunch of floating bushes. Can be expanded to other kinds of terrain objects on a per site basis.

Requires more testing on my end for both functionality and performance ... so putting up as a draft PR for now.

TODO

• [ ] Use getDir on terrain objects to more accurately calculate overlap/intersections (rectangular area instead of circular?)
• [ ] Test a different clippingType argument for boundingBoxReal https://community.bistudio.com/wiki/boundingBoxReal
• [ ] Calculate site radius using the object with largest 2D distance from site centre point.

screenshots

notes about screenshots

• used different parameters to what is in this PR. _siteRadius for this example would have been 15, not 5.
• the large rock terrain object that was hidden has a large maximum dimension, which is why it is hidden even though it's quite far away from the site.
• rocks on top of other rocks can be problematic, the secondary search with nearestTerrainObjects might want yet another bounding box calculation

debug markers

terrain hiding

[dijksterhuis]

Please can someone confirm that vn_mf_sites_load is non-functional?

Did a grep for wherever the sites data is supposed to get set in the profile DB but came up with nothing.

$ find . -name "*.sqf" -exec grep -Hn 'call para_s_fnc_profile_db' {} \; | grep sites
./mission/functions/systems/sites/fn_sites_load.sqf:19:(["GET", "sites", []] call para_s_fnc_profile_db) params ["","_sitesData"];