Home Fries Posted May 15, 2018 Posted May 15, 2018 Yes, this is a concession to gameplay, but i would like to have airfields with navaids to be able to accomodate all navaid types. For example, Nalchik doesn't have a TACAN and Nellis doesn't have RSBN (both for obvious reasons), but allowing this concession as a per-airfield option in the ME would allow for a lot more flexibility in mission design. Coversely, airfields that don't already have any navaids don't need to get them. Similarly, allowing this to be turned off can also prevent the OPFOR from dialing in a navaid to find an enemy airbase. Enabling this option allows mission flexibility and is much easier than refitting aircraft for export use (e.g. putting a TACAN system into the MiG-21). -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Tippis Posted May 15, 2018 Posted May 15, 2018 First step: the scripting engine has facilities for making any unit a beacon of (almost) any kind. Make that facility work, and document how it works. It's a bit silly that, even though the game features na vaids that have mobility as one of their main selling features; that it has placeable units that closely mimic those nav aids; that it has scripts and commands to turn those units into those nav ains… but that none of it actually functions when combined. ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
Frederf Posted May 16, 2018 Posted May 16, 2018 TACAN and RSBN were designed in real life to be deployable within a few days so there's no reason (except the difficulty of coding) why those systems can't be editor units deployed on a per-mission basis. Hopefully they could have default "snapping" behavior to properly setup relative to a runway to avoid poor or laborsome placement. Alternatively putting all services everywhere is not positive gameplay. Gameplay comes from lacking conveniences and having challenges.
Northstar98 Posted May 16, 2018 Posted May 16, 2018 (edited) An alternative (and my preferred option) would be to have ground vehicles/static objects that can function as NAVAIDs. Allowing you to set the frequencies/channels and output power, you can then place these as you desire. IRL systems like RSBN/PRMG, TACAN and I think even the Swedish TILS system (as documented in the Viggen manual) are mobile/have mobile variants. VOR can just be a static object, same for marker beacons and NDB/ARK stations. The other thing I'd like to is disable NAVAIDs (as well as remove vehicles present at airfields as I desire, to fully get a sandbox experience). Edited May 18, 2018 by Northstar98 Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk. Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas. System: GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV. Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.
Home Fries Posted May 16, 2018 Author Posted May 16, 2018 I agree, Lunatic. That would certainly be awesome. However, I wanted to provide something with relatively easy implementation so that we could see it sooner than later. My ideal would be having checkboxes for each navaid to be enabled/disabled, or a "default" checkbox that sets it up to be real-world accurate. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Recommended Posts