Add missing display options to new map

[DanAlbert]

Only thing here that's are strong requirement for 3.0 is the display for exclusion zones. The rest are nice-to-haves and debugging tools.

• [x] Culling
• [x] Threat zones
• [x] Navmeshes
• [ ] Time of day/weather themeing
• [x] Exclusion zones
• [ ] "Actual" front line
• [x] Debug flight plan drawing

[gatorman22]

I place a high value on displaying Culling zones, especially with the latest DCS 2.7 update that adds SLAM-ER to the Hornet with ~150mi range. I enjoy running the larger scale wars and use Culling of 75 to 150mi depending on the number of active units. I might have to fly over 75mi to get within range/alt/speed, putting the target some significant distance from the nearest active position. It helps to know I'm not going to leave a mud hole where I thought a BB would be.

At the same time, I'm familiar enough with Liberation that I can work around it until it is implemented after higher priorities.

[DanAlbert]

That's not how culling works. Package targets are excluded from culling.

Regardless, that's why it's a nice to have.

[gatorman22]

I understand, but I don't do standard strike packages in that way. Used as intended, I admit it works.

What I typically do is setup a CAS/Front line flight and delete all the Waypoints - see issue #822 . Then I use Advanced: Add Waypoint to load the individual targets for loading into GPS-guided munitions as TOO targets, followed by a RTB Waypoint.

An enhancement could further extend the Culling routine by also including flight waypoints in the zones. Maybe even a toggle in settings to enable/disable the function when, for example, someone wants to create a navigation waypoint in BFE and doesn't expect to need units loaded in the vicinity.

[DanAlbert]

File an FR if you have an FR. Let's please keep this on topic. No one needs to convinced that these map modes are useful.

[DanAlbert]

The important things are done. Moving the rest to the backlog.