Chump

The laser is quite picky. ONLY use it for any necessary spot ranging and during missile launch. Here are the rules: Laser rangefinder operation mode for one flight, series: 5 Each serie consists of 16 cycles of 10 seconds with 5 sec interval between the cycles. Interval between the series, min: 30 Page 13-4 from DCS: Blackshark 3 Pilot's Manual Every time that you land, repair your bird. This will reset the laser.

@buur I fixed the code above. I wrote it from memory without testing it late at night. </excuses> It can be executed in a mission now.

@winghunter I'm not sure what direction would do for TACAN/VOR/VORTAC. The parameter passed into the Beacon constructor is as follows: /MissionEditor/modules/Mission/BeaconData.lua: -- NOTE: non-pertinent lines omitted for clarity local function createBeaconVorFromAirdrome(airdrome) local angle = 0 local beacon = Beacon.new(x, y, angle, frequency) end local function createBeaconTacanFromAirdrome(airdrome) local angle = 0 local beaconTacan = Beacon.new(x, y, angle, frequency) end /MissionEditor/modules/Mission/MapView.lua: -- NOTE: non-pertinent lines omitted for clarity local function addBeaconVORTAC(beaconVORTAC) --- BEACON_TYPE_VORTAC = 5 local angle = 0 local icon = createIcon('beaconVORTAC', x, y, angle) end The angle is hard-coded to zero when creating some beacons. The defined angle in the Beacons.lua file is never actually used.

@buur Yes, you will need to comment out the following line in /scripts/MissionScripting.lua in order to use require: _G['require'] = nil

@Mav87th Have you tried something like: -- includes local magvar = require("magvar") local terrain = require("terrain") -- taken from /Scripts/utils_common.lua local function toDegrees(radians) return radians * 180 / math.pi end -- get unit position local unit = Unit.getByName("MyUnit") local p = unit:getPosition().p -- convert x,y to lat,lon local lat, lon = terrain.convertMetersToLatLon(p.x, p.z) -- set month/year from mission magvar.init(env.mission.date.Month, env.mission.date.Year) -- get magvar local mv = toDegrees(magvar.get_mag_decl(lat, lon)) -- pretty print local txt = string.format("%+0.1f°", mv) trigger.action.outText(txt, 10)

@BIGNEWY This is still happening in both SP and MP.

@paco2002 It seems that the event.initiator is no longer present in the Event message (for SP or MP) when creating/changing/removing a mark. Without a Unit, it is impossible to get the Controller to set the Task. Bug Report:

@-Solly- Are the pilots not being killed (ie. ejecting)? I'm playing Devil's advocate here, but I do believe that the events are not quite as stable as they once were.

I wish some of y'all could see/understand the software industry a bit better. I have been in it for 20+ years, and delays are part of the norm. Do you want a busted game? Do you think that ED is intentionally holding the release back just to exert some form of control over their users? Do you think that they are delaying the fix to that backlog bug because SoAndSo wants it real bad? I call BS. There is never a guarantee in development. Numerous factors, some out of your control, always play into every release. ♫ One bug down, pass it around, 27 more bugs found in the code. ♫ Calm down. This is not heart surgery; no one is (hopefully) going to die because you couldn't fly your new airframe in whatever week of the month that you thought you would be able. Just stop with the overly dramatic drama. Don't uninstall; don't come here just to tell the devs off; stop flailing your arms. This happens every single time a release is delayed. Accept the things that you cannot change... </2¢> Take care, and be excellent to each other.

@YoYo Isn't that the "Missiles Per Code" on the "Weapons BIT/Set-up Page"?

It has to "call home" when you launch it (to verify your account). If you don't do this step, it will enter "offline mode" and you can only play for a certain amount of time before having to authorize your account.

It was working in multiplayer the last I knew. It must be installed for each client to use the new functionality. These are LUA files, not EXE files, but safety first I suppose.

Made this a while back for someone to address this issue, if anyone is interested: https://github.com/chump29/DCS_Mod?tab=readme-ov-file#awacs--wingman-addons

I think that the closest you will get is the "circuit test" button to the left of the dial. AFAIK, you cannot cause a real ejection sequence without actually ejecting the crew member, only test the different stages. I say, let the blades break as they will. If you are wanting a hard landing vs ejection, I've never actually seen the physical blades cause any issues with the craft hitting the dirt and surviving.

I know, I know, another BS3 alignment topic (sorry @BIGNEWY, but hoping this will be a thing that someone can answer right away, or that someone can take back to the development team). This is only meant to address this simple question: When I join a random server and hop into the Black Shark, is there a way that I can tell what the map maker/server owner selected for INS alignment, or is it up to my discretion (maybe even overriding what the map preset was)? Thank you in advance.

This script is a few years old, but I would guess that it still works (see attached). You assign the SeaEagle target on the F10 map using a text mark that says "seaeagle". It could probably be done a bunch of different ways, but you get the idea. Install this plus MiST in the mission. seaEagle.lua

My bad. I do not know how to change the color of the HMCS. Anyone figured that out?

There was a post about it here: https://forum.dcs.world/topic/154935-hud-color/?do=findComment&comment=3096034 The updated path for A-10CII is: /Mods/aircraft/A-10C_2/Cockpit/Scripts/HUD/Indicator/HUD_init.lua The line number is still the same: 383 if you are changing the day color, 384 if changing the night color. Black font color for day setting would be: day_color = {0, 0, 0, 255/255}

That is not correct. Maybe it is a cancelled/upcoming feature?

Instead of setting the flag, why not just use TransmitMessage right there?

It is labeled as control_priority. My guess would be, "(F)ront"? Or, off/nothing is displayed there if the rear seat has priority.

I believe that this is a display bug in DCS (please correct me if I'm wrong, @Devrim). Have you tried resetting the weapon system before selecting the next configuration? I thought that this was the solution as-is.

There is this topic:

2023-07-31 13:53:39.413 INFO APP (Main): CPU cores: 6, threads: 12, System RAM: 16328 MB, Pagefile: 33792 MB 2023-07-31 13:54:33.119 INFO APP (Main): gDescription: "NVIDIA GeForce GTX 1080" gVendorId: 4318 gDeviceId: 7040 gMemory: 8072 MB 2023-07-31 14:19:24.453 ALERT EDCORE (10168): Out of memory in ed_malloc for 5592592 bytes. Unfortunately, 16GB OS and 8GB GPU isn't going to cut it these days. Time to upgrade, my friend.

I believe that you have the correct Group category attribute name for this to work. Group.Category = { AIRPLANE, HELICOPTER, GROUND, SHIP } I noticed that MiST is trying to find the matches by criteria, but category is spelled incorrectly in the code. I have opened an issue for it here: https://github.com/mrSkortch/MissionScriptingTools/issues/78