Profile mechanism

At DCS startup, the %userprofile%/Saved Games/DCS/mods/services/lotatc/profiles/ directory is listed by LotAtc server and will be displayed in the DCS > Options > Special > LotAtc 4 DCS options page

Default profiles are provided with LotAtc server but you can add your own profiles to customize LotAtc as you want. It could be usefull for a specific campaign or mission for example.

Create my profile

Go into the %userprofile%/Saved Games/DCS/mods/services/lotatc/profiles/ directory. Just copy custom.lua to a new file for example my_profile.lua.

You can edit any profile with no restriction but files will be overwritten on next LotAtc server update, so copy them is a best choice.

Open the new profile with Notepad++ or any other text editor.

Do not use Notepad, it generally break the lua files, prefer Notepad++

Here is the default settings with explanation, adapt as you want:

    return  {
    -- Name displayed in DCS
    profile_name = 'Custom',

    -- You can insert any values available in config.lua, it will be OVERRIDE by this file
    -- Ex: blue_password = "mynewbluepassword"

    -- Show eni datas (type, name...)
    show_datas = true,

    -- Show all sams
    show_sams = true,

    -- Filter low speed aircrafts/helicopters
    speed_filter = true,

    -- Radar mode
    --  0 = See all, no radaar
    --  1 = Cylinder model, no altitude management 
    --  2 = Sphere model, radar are full sphere
    --  3 = Conic model, radar are sphere but have some blind cone (cone are defined in DCS)
    radar = 1,
    -- Use RCS management on radar side
    -- ONLY USED WITH radar=3, ignored otherwise
    use_rcs = true,

    -- Use relief computation
    relief_filter = true,

    -- Automatically set type of contacts
    --  0 = for all contacts
    --  1 = only for friends
    --  2 = only for friends Awacs
    --  3 = disable
    automatic_type = 0,

    -- Allows approach on airports
    --  0 = No approach
    --  1 = Only coalition airport can have approach
    --  2 = All airports can have approach
    approach_all_airports = 1,

    -- Define how airport radar will be modelized with LotAtc
    -- Only airport allowed could act as radar, it is depending of approach_all_airports value above
    -- 0 = Airport will not act as radar
    -- 1 = Airport radar see all units ( flying and ground units)
    -- 2 = Airport radar see only aircraft (planes, helicopters) in flight or on ground
    -- 3 = Airport radar see only FLYING aircrafts or active transponders units (for both AI and human)
    airport_radar_mode= 2,

    -- Force the use of the player name
    force_player_name = false,

    -- Use neutral coalition for all unknown contact
    neutral_coalition_by_default = true,

    -- Use callsign instead of group name
    --  0 = Do not use callsign on group name (activate callsign specific display on clients)
    --  1 = Use callsign for all units except humans (disable callsign specific display on clients)
    --  2 = Always use callsign for all units including humans (disable callsign specific display on clients)
    use_callsign = 0,

    -- Indicate radar coverage simulation to be used
    -- "global"    = use all radars available to make a global coverage (as with LotAtc 1.x)
    -- "monoradar" = controller will have to choose which radar to control on connection (WIP) 
    modelisation = "global",

    -- Tracking delay, time for the simulation to be able to make a track on a spot radar
    -- Put 0 to disabled the feature and make track instant (as with LotAtc 1.x)
    -- Delay is in seconds
    tracking_delay = 0,

    -- If yes, when severals units are near each other, we will only have one track, due to resolution radar
    -- Use false to see everybody in a patrol
    use_range_resolution = true,

Once done, start DCS, select your profile in the DCS > Options > Special > LotAtc 4 DCS options page

Advanced configuration

You can also add config values from %userprofile%/Saved Games/DCS/mods/services/lotatc/config.lua in the profile.lua files, it allows to add specific password for example.

red_password        = "mymissionredpass" ,
blue_password        = "mymissionbluepass",

virtual_awacs_name 	= "myvirtualawacs_",
use_chat = false,

See all available values on the advanced configuration page.

You can create specific profile for a custom event/mission.