Buzzer1977

Thanks ! I'll give it a try.

I'm passing a path to a unit and goRoute returns true, but the group doesn't do what it's told. local ok = mist.goRoute(grpinfo["name"], path) env.info("Group: " .. mist.utils.serialize("string", grpinfo) .. " set route: " .. tostring(ok) .. " path: " .. mist.utils.serialize("string", path)) The output of the env.info is as follows, but i can't find anything wrong with it, besides it just doesn't work. The aircraft just head to the next airport to land there. set route: true path: string = { [1] = { ["alt"] = 11000, ["x"] = -184478.33407856, ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed"] = 200, ["type"] = "Turning Point", ["y"] = 356992.43725087, }, -- end of [1] [2] = { ["alt"] = 11000, ["x"] = -182069.92084432, ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed"] = 200, ["type"] = "Turning Point", ["task"] = { ["id"] = "ComboTask", ["params"] = { ["tasks"] = { [1] = { ["enabled"] = true, ["auto"] = false, ["id"] = "Orbit", ["number"] = 1, ["params"] = { ["speedEdited"] = true, ["pattern"] = "Race-Track", ["altitudeEdited"] = true, }, -- end of ["params"] }, -- end of [1] }, -- end of ["tasks"] }, -- end of ["params"] }, -- end of ["task"] ["y"] = 303282.32189971, }, -- end of [2] [3] = { ["alt"] = 6000, ["x"] = -268851.68806047, ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed"] = 150, ["type"] = "Turning Point", ["y"] = 421561.33728146, }, -- end of [3] [4] = { ["alt"] = 11000, ["x"] = 348969.94807213, ["action"] = "Turning Point", ["alt_type"] = "BARO", ["speed"] = 200, ["type"] = "Turning Point", ["y"] = 1093523.3106468, }, -- end of [4] } -- end of string

function tacanFrequency( channel, mode ) if ( mode == "Y" and channel < 64 ) then local basef = 1087000000 local offset = 1000000 * channel return basef + offset elseif( mode == "X" and channel < 64 ) then local basef = 961000000 local offset = 1000000 * channel return basef + offset elseif ( mode == "Y" and channel > 63 ) then local basef = 961000000 local offset = 1000000 * channel return basef + offset elseif( mode == "X" and channel > 63 ) then local basef = 1087000000 local offset = 1000000 * channel return basef + offset end end

The referenced table doesn't relate in any way with what DCS does. I just analyzed what the mission editor does. Above channel 63 base frequencies of X and Y are swapped. Don't know if this is intentional or a bug. ["params"] = { ["type"] = 4, ["AA"] = false, ["callsign"] = "63x", ["modeChannel"] = "X", ["channel"] = 63, ["system"] = 18, ["unitId"] = 686, ["bearing"] = true, ["frequency"] = 1024000000, }, -- end of ["params"] ["params"] = { ["type"] = 4, ["AA"] = false, ["unitId"] = 687, ["modeChannel"] = "X", ["channel"] = 64, ["system"] = 18, ["callsign"] = "64x", ["bearing"] = true, ["frequency"] = 1151000000, }, -- end of ["params"] ["params"] = { ["type"] = 4, ["AA"] = false, ["unitId"] = 688, ["modeChannel"] = "Y", ["channel"] = 63, ["system"] = 19, ["callsign"] = "63y", ["bearing"] = true, ["frequency"] = 1150000000, }, -- end of ["params"] ["params"] = { ["type"] = 4, ["AA"] = false, ["callsign"] = "64y", ["modeChannel"] = "Y", ["channel"] = 64, ["system"] = 19, ["unitId"] = 689, ["bearing"] = true, ["frequency"] = 1025000000, }, -- end of ["params"] -- 0X 961000000 -- 1X 962000000 -- 2X 963000000 -- 3X 964000000 -- 4X 965000000 -- 10x 971000000 -- 20x 981000000 -- 30x 991000000 -- 40x 1001000000 -- 50x 1011000000 -- 60x 1021000000 -- 61x 1022000000 -- 62x 1023000000 -- 63x 1024000000 --> 63/64 change base freq -- 64x 1151000000 -- 65x 1152000000 -- 66x 1153000000 -- 67x 1154000000 -- 69x 1156000000 -- 70x 1157000000 -- 73X 1160000000 -- 80x 1167000000 -- 90x 1177000000 -- 100x 1187000000 -- 110x 1197000000 -- 120x 1207000000 -- 126x 1213000000 -- 0Y 1087000000 -- 1Y 1088000000 -- 2Y 1089000000 -- 3Y 1090000000 -- 4Y 1091000000 -- 10y 1097000000 -- 20Y 1107000000 -- 30y 1117000000 -- 40Y 1127000000 -- 50y 1137000000 -- 60y 1147000000 -- 61y 1148000000 -- 62y 1149000000 -- 63y 1150000000 --> 63/64 change base freq -- 64y 1025000000 -- 65y 1026000000 -- 66y 1027000000 -- 67y 1028000000 -- 69y 1030000000 -- 70y 1031000000 -- 80y 1041000000 -- 90y 1051000000 -- 100y 1061000000 -- 110y 1071000000 -- 120y 1081000000 -- 126y 1087000000 function tacanFrequency( channel, mode ) if ( mode == "Y" and channel < 64 ) then local basef = 1087000000 local offset = 1000000 * channel return basef + offset elseif( mode == "X" and channel < 64 ) then local basef = 961000000 local offset = 1000000 * channel return basef + offset elseif ( mode == "Y" and channel > 63 ) then local basef = 961000000 local offset = 1000000 * channel return basef + offset elseif( mode == "X" and channel > 63 ) then local basef = 1087000000 local offset = 1000000 * channel return basef + offset end end

Does anybody know how to calculate TACAN frequncies to activate the beacon from lua ? I know it depends on channel, mode, type and AA ... but i have no idea how to calculate it. { ["enabled"] = true, ["auto"] = true, ["id"] = "WrappedAction", ["number"] = 2, ["params"] = { ["action"] = { ["id"] = "ActivateBeacon", ["params"] = { ["type"] = 4, ["AA"] = false, ["unitId"] = 676, ["modeChannel"] = "Y", ["channel"] = 1, ["system"] = 5, ["callsign"] = "ta1", ["bearing"] = true, ["frequency"] = 1088000000, }, -- end of ["params"] }, -- end of ["action"] }, -- end of ["params"] }

Is there a object that stores which liveries for a aircraft and country are available ?

That's what i do at the moment, but it makes scripting missions in lua so much harder with dynamic generated aircraft.

Iran can only use KC-130 and KC-135MPRS, but Iran also operates boom equipped KC-135 to refuel their F-4 and (K)C-130 via boom.

Hmm ... i'm having a similar issue even with the standard liveries.

When playing in multiplayer on dedicated server, all MiG-21 show up with slovak livery. In singleplayer the liveries are okay. dcs.log.old I verified it with a fresh Saved Games/DCS directory. No modules, etc .... Track and mission file are added. Test-20220512-014410.trk Test.miz

Another track showing the same problem. Ship two flying directly into the ground. suicideF14-B-2.trk

I have a larger mission with a AI two ship F-14B escorting the player. Ship two seperates from lead at altitude and flies directly into the ground. Track is attached. suicideF14-B.trk

Have a look at DCS-BIOS, especially the dcs-lua submodule. That's what most people use for their pits. https://github.com/dcs-bios/dcs-bios

Just putting a bunch of aircraft on a carrier deck leads to blocking of AI aircraft and even to accidents if a AI F-14 respawns next to a F-14. Being able to assign parking slots like on a normal airfield can help to solve these problems. A lua function that returns if a aircraft fits on a parking slot would be nice too.

It would be nice to have server based liveries, so everybody playing on the server is seeing the same.

Took some time to get it in a usable sized track, but i got it. It's quite at the end. Track is ~7MB https://gediegos.de/Renderbug-20220413-231520.trk

Works also with steam if you install the server from ed in parallel. The server installer will detect your steam version and only install the necessary files to run the server in parallel.

Welcome to the club.

Nope, it won't. I have the same issue with the new cable. Same issue here with the G2. It happens sporadically but on a regular basis. I have the latest G2 firmware, latest PC BIOS to fix the USB problems with AMD chipsets, newest RTX driver and the new G2 cable model, but still have this problem.

Hmmm could be that this is "works as designed". Firing weapons is usually prohibited with the WOW (Weight-On-Wheels) sensor engaged. So maybe the faulty gear will cause the WOW sensor to be marked as fail too.

The FLIR image in the F/A-18c is sometimes partially covered by a black rectangle making it unusable from time to time as can be seen in the recording. The behavior seems quite random. Zooming in or out sometimes fixes the issue, sometimes it's stuck.

That's what i thought too, also had to pull some Gs with 4xGBU-10 before, but repair AC didn't fix it.

Don't know. I usually get shoot and die before i can make several carrier landings.

Wing folding stops to work after a few carrier landings. Request repair won't fix it. Can't attach the track file because it's 170 MB large.