DCS: Controller

[VTJS17_Fire]

Hi,

 

with all that new modules, that are already released (Ka-50, A-10C, P-51) and announced (MiG-21, IRIS Projects, EDs first fixed wing fighter, FC3) the airspace in DCS is growing to a good and real level.

 

If it possible, to fly with 40-50 clients in the future, we need controller - like in real life - which control and lead the airspace.

 

We will need an ATC, who coordinate the airspace around the airbase, including take off, approaches and taxi/ ramp.

 

 

On the other hand, we absolutely need GCI controllers. Now, we have an AWACS and with the "new" function, to set up the pattern of the AWACS to the real one, we have good conditions that the AWACS can even work on a turn.

But the AI as GCI is not really good, not flexible and the important: in real life, the GCI give the commands to the pilots, depending on mission task or threat level.

 

 

So, we need an DCS module for controlling the airspace and missions as ATC/ GCI!

 

 

This module have to be just a desktop with radar screen and all the other tools, controllers have - like a radio and datalink.

 

With an external tool like TARS, the controller could work like in real and contact pilots on different frequencies. Without TARS, the controller have to use radio commands and use that, to give orders to pilots on different frequencies.

 

If the aircraft has a datalink which works with the ground based station (like Link16), the controller give commands via datalink to the pilot.

 

The mission builder should choose, which radars can be used. Only airbase radars (with different ranges), SAM radars (tracking radar, search radar), early warning radars, ship radars or AWACS (range and picture depending on altitude and terrain). The mission builder could mix them.

 

The controller itself, could choose between air picture for doing GCI work, a real-time-strategy view (bird's eye view) to control the airbase and its airspace (~ 10nm, scale able) and a in-game view from the towers position, to check and control approaches at the airbase.

 

The controller should set bullseye via coords, use NCTR to make an EID at longe range, measure dynamic range between two aircrafts and so on.

 

ATC Tool by Zillion (vJabog32) for FC 1.12 (without B/E function via coordinates) - our squadrons favourite tool for that work. Sadly, it isn't updated for FC2/ DCS. The other program LoATC, isn't that good, IMO.

 

 

kind regards,

Fire

[Kaiza]

In this thread Wags mentions having an "observer" command role. I would imagine (am hoping) that this would enable a slot to be used as ATC and/or GCI/AWACS.

 

http://forums.eagle.ru/showthread.php?t=89468

[Grimes]

I got all sorts of warm fuzzy memories of Lockon 1.12 when I saw that screenshot, I'd love to see it ported to DCS.

[VTJS17_Fire]

In this thread Wags mentions having an "observer" command role. I would imagine (am hoping) that this would enable a slot to be used as ATC and/or GCI/AWACS.

 

http://forums.eagle.ru/showthread.php?t=89468

 

Nope. The observer role exists already in the A-10C beta. You can only use the map view and see, what the ground forces see. And I can't imagine, that all the ATC/ GCI stuff is implemented in CA.

 

An DCS ATC/ GCI module like the Jabog ATC tool has the benefit, that the export lua has not to send data to an external tool, so we have cheat prevention, too.

 

 

kind regards,

Fire

[Kaiza]

Don't get me wrong, I am not saying this feature would mean that such a controller module is not required, just that it hopefully it will be able to be used as a rudimentary tool for that use until something better is released.

 

Totally agree, GCI module would be great.

[KosPilot]

Excellent idea :thumbup:

[VTJS17_Fire]

I think, it makes sense, to set slots for controllers, too. Like the slots in CA. So, we need no external tool for the controllers and don't need the export.lua. This is an important point in cheat prevention.

 

 

kind regards,

Fire