Pikey

As it stands, the West facing coastline of the Caucasus is suitable for Balkans simulations, the housing and climate and geography is close enough. You can get some very similar ranges and coastlines if you can tolerate a bit of artistic liberty when looking at the shapes, most of the concerns on reality fade away once in cockpit and navigating unfamiliar terrain. The discussion on geo-politics always ends in pretty dodgy territory, so I'm avoiding that, but I don't see the fit for a Super Carrier fleet stuck in what amounts to a snowglobe, and the politics on the ground shows how the area is being regarded without such means.

Never seen any API's for score. I know each unit has it built into their lua file. Im not sure if even the score is available in the unit description of each.

Respawning them or ammo trucks. You cannot change ammo states of items in the game with scripting.

This would be one of the reasons the Marianas is free (I suspect), because the default map isn't appropriate for the large parts of DCSW focus. There's only so many PG map copies you can sell, some folks don't buy everything. The other shift is having large US overseas bases to explain the predominant US assets that are played in DCS. Plans come together slowly when you develop on a platform that is open.

Well now you dont need to use a parking spot and can have it anywhere without a plane in the way!

Sure, I think the development appears odd to us on the outside, you see the assets made then wait for another team to pickup the code. As it is, the most obvious reason this might be delayed is because unit types align to the tasks they can perform, so en masse making all units capable of tacan would be a game issue, and you can't make the tacan a plane or a ship. So it's in an odd place. I have no doubt we might wait a bit, so having the capacity of a workaround will get some life out of this.

[DEPRECATED - USE THE INBUILT BEACON ED SUPPLY - this is for history now] At the current time of writing, the Portable TACAN unit (TTS 3030) found in the Fortifications section of units in the Mission Editor does not allow the Task to enable any TACAN to be emmitted. Hence, there are some hefty workarounds to get this going and I had to scratch my head and get creative. You will also note that in the Sim you are unable to put the Tacan task onto anything but a plane or a ship. This rule applies to scripting, so anyone using MOOSE BEACON class will find they get an error: if you attempt to place a tacan object on anything but a plane or a ship. But you can place an AABeacon on a plane. How does this help? Well a bit of imagination and of course a Late Activated object can accept tasks just like a normal unit, and low and behold I got an invisible plane and an A-A beacon. All it needed was some magic replacement to put the Tacan portable model there and it was done. Of course, for those realists, it is an Air to Air tacan and you need Yankee mode and A-A set. So it's not what it should be, but it can do until ED finish the Tasks for the Tacan portable. End result is a few lines of copy paste, so it's not a hardship. The previous options involve modding the terrain beacons.lua file....not good, or creating a modded tacan of a plane and swapping models around, also not good for some sections of the community. Here's the video explanation Here's the script --Devious TACAN workaround script by Pikey 09 1500Z MAY 2020 --WHY? --The Portable TACAN model in DCS cannot have the task "Activate TACAN". There is no way to use scripting to add a Beacon because that type is not accepting the Task Activate Tacan. --Only Ships and aircraft accept a TACAN task and you can't put them where you like. You could mod, but... --For reasons of extreme workaround the TACAN is A-A mode ONLY. There is no other way, but you get your distance and bearing anyway. --HOW TO --Requires a reasonably up to date MOOSE.lua version https://github.com/FlightControl-Master/MOOSE_INCLUDE/blob/develop/Moose_Include_Static/Moose.lua --Put a Harrier where you want a TACAN, set it LATE ACTIVATED, and make it start from Ground so it is on the floor. Call it's UNIT/PILOT name a three letter code for the TACAN --Repeat for every new TACAN you want - e.g. 'PT1', 'PT2', 'PT3' etc --Fill out the table "HarrierList" below, with all these Harrier unit names, they become the TACAN MORSE NAME --Create a Portable Tacan unit model and call its UNIT 'tacanPortable', set this to "LATE ACTIVATED" --Load MOOSE.lua on mission start --Put this script in DO SCRIPT or have it as part of an existing script --Tune to your tacan, remembering A-A mode is required --MP compatible. Any issues, make sure you READ YOUR DCS.log for errors, which will most likely be a naming issue siunce Lua is case sensitive --EDITABLE local tacanStartNumber = 50 --you need to work out Tacan channel conflicts yourself, the beacons start from this number and go up local HarrierList = {'PT1', 'PT2', 'PT3' } --add the UNIT/PILOT NAME of the Harrier aircraft to this list. They will become the Tacan Morse names so keep it 3 letters local tacanPortable = UNIT:FindByName('tacanPortable') -- This is the UNIT name of your single Late Activated Tacan object. You can change this here if you really find a need to. --NOT EDITABLE for i=1,#(HarrierList) do local imposterUnit = UNIT:FindByName(HarrierList[i]) local position = imposterUnit:GetVec2() -- Gets the position of the invisible Harrier local myBeacon = imposterUnit:GetBeacon() -- Creates the beacon myBeacon:AATACAN(tacanStartNumber+i-1, imposterUnit:GetName(), true) -- Activate the beacon SPAWN:NewWithAlias(tacanPortable:GetName(), imposterUnit:GetName()):SpawnFromVec2(position) -- Places a Portable Tacan model where the invisible Harrier is end Happy pseudo waypointing in your Hueys and F-5's or adding TACAN to your Range, or replacing TACAN stations you miss, like Khasab, or whatever else you fancy. No, I do not know how to RSBN, yet. tacanTest.lua

Not Personal jammers in the last 60 years :) There are some fantastic Vietnam era videos on jamming, how it works and what it looks like on the recieving end, Unfortunately ECM and ECCM is about the most closely guarded of all the secrets you can get (of course) Jamming is also done a lot "off board" by dedicated planes or other agencies, as you can note by the dedicated airframes that perform these functions, so we can deduce even less about SPJ's usefulness, I'd go as far to say, I don't rate them in the modern world. Home on Jam is the thorn in understanding personal jammers, you need to know the weapons that might come at you, hence this is why the offboard jamming is probably more of a thing. It's neglected in DCS because it would have to be so artificially provided that it could only relate to player versus player activities in a balanced setting else the game would be a miserable experience. No one liked jamming in FC3 when it was still a thing.

i think it was already mentioned about Manston shouldnt be paved, they are aiming for an earlier date.

"God grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference." Reinhold Niebuhr

Well yeah, exactly, if one is running a script where RAT is using things you dont want it to, then, 'untell' to use those in the same way as you told it to, but in reverse...

What version are you running? as far as I remember this came with 2.5.6. It's been raised before so that's the best you can hope for - that it's acknowledged. There's no notifications for things that will happen in terms of bug fixes, never has been, so it's easier on your mind to just go with the flow and take the waves.

Helles Belle: NP - Frank did th ehard work for this, i'm just keeping him scripting Babok: Not sure I understand, if you mean you dont want RAT using farps and Oil platforms, then you need to tell the script.

Hey man, if DCS crashes, it's a straight up defect and to report it, head to the DCS World bugs section, do your best with saying what steps you need to perform to reproduce it, supply the logs and the pack that DCS produces during a crash, and the track file if it made one and the mission which you can all attach to the thread. These types of crash are fairly significant, you might notrecevie feedback, but you will be doing your part to help :)

it doesnt - you mean the fluffy ones, right? It changes the solid cloud layer at 9 and 10 tenths Sorry, another one we've been begging for. Also Dynamic weather ends up pretty weird on different parts of the map, you can get a whole load of fluffy clouds, then it just stops suddenly. Personally, I wouldnt, after experience :)

Not how I think you are thinking. You can't search by name, nope. You can only search an area and have it return a bunch of names, from which you could work on and filter, but its all ugly and not designed for this. And without scripting you are up s&&t creek without a paddle for this.

This is pretty hot

They stop a few hundred metres away and always have. One day they will have to solve that for LST's and similar. Until then, you are seeing what happens.

This is your answer. 4000 views, i did it in 2017.

Use MOOSE's FOX missile trainer, it's exactly for that. I'm sure clients cannot be made invincible, but players can. https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Functional.FOX.html takes about 3 lines to write and the examples are at the link.

You could produce a list of scenery objects with scripting by model name. The problem is, you wont know what the model name actually is, it will only be interesting if its uncommon. Some are obvious. Like "HANGAR_A". Or similar. The other, bigger problem is it does tax DCS as there are millions, especially on NTTR and PG where you get objects as small and insignificant as sections of fencing and fire extinguishers, bins and cars. if you want to do specific areas, and i can only work out circles because i'm a bit of an idiot at scripting. I think one of my signatures has some scripting related code, but its not exactly what you want and to produce something that scans an entire country efficiently isnt something im invested enough to do for anyone. Try first usign my scenery tools and the map in satellite mode to mark things that look like they might be interesting, then get to know the model names. If you find example sof each of the interesting things, like Roki tunnel entrances and unique objects, you can start to use an area search and output to file and look at the models. You can work backwards from there to scane for specific models. Sorry I can't help more but that's how I woudl do it.

Indeed. You need to go to the objects properties and press HIDDEN. unfortunately this disables access via a GameMaster slot and is not practical for some servers, but should be fine for you.

@teqqra On the tanker...You so nearly did it yourself great :) You have the solution but put the spawn object instead of what the argument needs, which is a string with the group name. You have TANKERRU, which you defined as the object that holds the SPAWN data, what you wanted was the SPAWNs returned GROUP.name: :OnSpawnGroup(function(grp) A2A_Dispatcherred:SetDefaultTanker(grp:GetName()) end)

Good find. I've known quite a few folks getting issues with long and deep nested menus and we also had a lot of people say they had issues with long and complex menus but we never saw any direct error that stood out at the time. I can say that the symptoms have existed for a long time and 132nd was prone to getting menus begin to corrupt for over two years afaik. But nothing that related it to a dcs error message. We just trimmed them until it worked. It was also a bit erratic when it could happen, so we coudl never reliably reproduce. FIrst time I heard there actually WAS a limit, so thanks for posting.

This is copied from Discord stickies, Frank already made a master list for CAM. -- Liveries CAM v0.80 B727skins={"AEROFLOT", "Air France", "Alaska", "Alitalia", "American Airlines", "Clean", "Delta Airlines", "Delta Airlines OLD", "Hapag Lloyd", "Lufthansa", "Lufthansa Oberhausen Old", "Northwest", "Pan Am", "Singapore Airlines", "Southwest", "UNITED", "UNITED Old", "ZERO G"} B737skins={"Air Algerie", "Air Berlin", "Air France", "airBaltic", "Airzena", "AM", "American_Airlines", "British Airways", "C40s", "Clean", "Disney", "EA", "easyjet", "FINNAIR", "HARIBO", "JA", "Jet2", "kulula", "LH", "Lufthansa BA", "Lufthansa KR", "OLD_BA", "OMAN AIR", "PAN AM", "Polskie Linie Lotnicze LOT", "QANTAS", "RYANAIR", "SouthWest Lone Star", "ThomsonFly", "TNT", "Ukraine Airlines", "UPS"} B747skins={"AF", "AF-One", "AI", "CP", "IM", "KLM", "LH", "NW", "PA", "QA", "TA"} B757skins={"AA", "BA", "C-32", "Delta", "DHL", "easyJet", "Swiss", "Thomson"} A320skins={"Aeroflot", "Aeroflot 1", "Air Asia", "Air Berlin", "Air Berlin FFO", "Air Berin OLT", "Air France", "Air Moldova", "Airbug Neo", "Al Maha", "Alitalia", "American Airlines", "British Airlines", "Cebu Pacific", "Clean", "Condor", "Delta Airlines", "Easy Jet", "Easy Jet Berlin", "Easy Jet w", "Edelweiss", "Emirates", "Etihad", "Eurowings", "Eurowings BVB09", "Eurowings Europa Park", "Fly Georgia", "Fly Niki", "Frontier", "German Wings", "Gulf Air", "Iberia", "Iran Air", "Jet Blue NY", "JetBlue", "jetBlue FDNY", "Kish Air", "Kuweit Airways", "Lufthansa", "Lufthansa New", "MEA", "Qatar", "S7", "SAS", "Saudi Gulf", "Saudia", "Small Planet", "Star Alliance", "SWISS", "Thomas Cook", "Tunis Air", "Turkish Airlines", "United", "Ural Airlines", "US Airways", "Vietnam Airlines", "Virgin", "WiZZ", "WiZZ Budapest", "WOW"} A380skins={"Air France", "BA", "China Southern", "Clean", "Emirates", "KA", "LH", "LHF", "Qantas Airways", "QTR", "SA", "TA"} Cessnaskins={"Blank", "D-EKVW", "HellenicAF", "Muster", "N9672H", "SEagle_blue", "SEagle_red", "USAF-Academy", "V5-BUG", "VH-JGA"} Although if you want regional only or variation you still need to set Livery per spawn using the line in your RAT object like this, to limit, the script will not and should not randomly pick liveries without being told to otherwise you would lose control and people would get mad: a380s:Livery({"Emirates", "China Southern", "BA", "KA"})