Chump

@RaisedByWolves I was merely pointing out that limestone maybe shouldn't catch fire right away (unless I was dumping fuel and creating a spark with my skids). A damage model for the pyramids, sure thing! I will give you credit for the creative use of a bombing range... @Slippa Please lower your voice. We wouldn't want @OnReTech to think that we were using one of painstakingly-recreated Wonders of the World as anything other than a tourist destination for sightseeing.

Under the trim hat, on the lower right.

Track or it didn't happen™. j/k I fly the BS3 the most, and unless I'm evading/being aggressive with the controls, I've never seen the HUD speed disappear. Do y'all have more details on this, or can we safely assume that over-steering (throwing off radar/gyros) might be the case? I could not find a 10° reference in the manual.

... removed ...

In TV/Indicator/init.lua, right? Are you using LEFT_MFCD in your monitor setup as the viewport name in your multi-monitor config? I believe that you added the correct line of code to export the TV.

Check out this thread: I think we all had a bit of confusion when trying to purchase the upgrade.

Two weeks™. I can't wait! Thanks for all of your hard work, @The_Fragger

@OnReTach So, I noticed that if you don't quite stick the landing on the Great Pyramid and slide down it backwards, that the pyramid is on fire afterwards. I'm not sure the correct way to deal with this, but wanted to report that my helo flying broke a pyramid that has been around for 4,500 years.

Wishlist item: someone (such as @Rudel_chw) makes all functional/realistic SAM site templates on the map, when they have some free time, of course. </2¢>

Norton AV (hey, stop with the name-calling, I know) did not detect it as treacherous. It normally would, it seems. In my experience, newer file signatures that haven't been approved are flagged. I agree with @Rudel_chw % that ED is not purposefully trying to sneak a Trojan onto your PC or anything nefarious. When in doubt, submit the file so that it can start being whitelisted by the AVs. When really in doubt, grab a drink and watch the sunset.

SP always comes in last, unfortunately. I don't know the dev's intent, but I'm guessing that it was more important to push the changes as-is than focus on a minority of user base. I'm not sure the percentage, but look at how SP has been more and more abandoned in favor of MP/PVP in all games currently. I don't think that the dev team specifically said, "F these guys," but that's just how it seems to roll when there is a bottom line. The only caveat might be that PC will get to it, if their PM isn't all up on them about daily Scrums/Kanban and meetings-to-have-meetings so they can get back to work. *fingers crossed* Maybe we'll see auto-hover return in the next patch? Cheers PC. Thanks for the update, don't get me wrong.

@BaronVonVaderham May I ask why you don't like Lian Li cases? I've found them to be quite nice. I've only had one, so I'm not a brand pusher. Just curious why the exclusion.

This had me intrigued, so I looked into it. It seems that the problem lies in the radio modulation definition in \CoreMods\aircraft\A-10\A-10C_2.lua: panelRadio = { [1] = { name = _("UHF/VHF: ARC-210"), range = { {min = 30.0, max = 87.975, modulation = MODULATION_FM}, {min = 108.0, max = 135.995, modulation = MODULATION_AM}, {min = 136.0, max = 155.995, modulation = MODULATION_FM}, -- HERE {min = 156.0, max = 173.975, modulation = MODULATION_FM}, {min = 225.0, max = 399.975, modulation = MODULATION_AM} -- AND HERE }, In \MissionEditor\modules\me_panelRadio.lua, if it finds a frequency within a defined range (in this case, 136-155.995), it will populate the combo box depending on the radio's modulation. Given that it is set to MODULATION_FM and MODULATION_AM, respectively, that is all that is populated and then it is disabled: if a_type == DB.MODULATION_AM_AND_FM then local item = ListBoxItem.new(cdata.modulationName[DB.MODULATION_AM]) item.modulation = DB.MODULATION_AM a_comboList:insertItem(item) local item = ListBoxItem.new(cdata.modulationName[DB.MODULATION_FM]) item.modulation = DB.MODULATION_FM a_comboList:insertItem(item) a_comboList:setEnabled(true) else local item = ListBoxItem.new(cdata.modulationName[a_type]) item.modulation = a_type a_comboList:insertItem(item) a_comboList:setEnabled(false) -- HERE end To get it to drop into the IF logic instead of the ELSE logic, ED will need to alter the frequency range's modulation to MODULATION_AM_AND_FM. That leaves the issue of how it will set the default modulation since it is not provided anywhere. Something like this would work: panelRadio = { [1] = { name = _("UHF/VHF: ARC-210"), range = { {min = 30.0, max = 87.975, modulation = MODULATION_FM}, {min = 108.0, max = 135.995, modulation = MODULATION_AM}, {min = 136.0, max = 155.995, modulation = MODULATION_AM_AND_FM, default = MODULATION_FM}, -- notice the dffault property {min = 156.0, max = 173.975, modulation = MODULATION_FM}, {min = 225.0, max = 399.975, modulation = MODULATION_AM_AND_FM, default = MODULATION_AM} -- and here, based on Table 1 (shown above) }, Then one would need to alter the IF/ELSE logic in \MissionEditor\modules\me_panelRadio.lua to something similar to: -- found in getModulationOfRange() if a_frequency >= v.min and a_frequency <= v.max then return v.modulation, default -- return the default property also -- found in createRadio() local frModulation, mod_default = getModulationOfRange(radio.range, channel.default*koef) -- capture the default property -- a bit later in the same function... local function fillModulationList(a_comboList, a_type, mod_default) -- pass it into the function that populates the combo box -- found in fillModulationList() if not mod_default then -- if default modulation is not provided a_comboList:selectItem(a_comboList:getItem(0)) else -- if it is setModulationInComboList(a_comboList, mod_default) -- then set it end Obviously, this will not pass IC at this time. I hope this will help ED fix this issue so that it can be released in a timely manner.

@markturner1960 Try something like this: https://www.timeanddate.com/moon/georgia/batumi?month=6&year=2016 Just change the location and year/month close to what you want and you can see the moon phases for specific days. Set that date in the mission editor and it should reflect it in the mission.

@SC_SquadCentral You are using the same ID (1) for both circles. Try using another ID, like this: local ref = trigger.misc.getZone("Krymsk") trigger.action.circleToAll(-1, 2, ref.point, ref.radius, {0, 0, 0, 0}, {1, 0, 0, .7}, 0, true) -- notice the second parameter is now 2 Than you can use that ID to alter the color: trigger.action.setMarkupColor(2, {0,0,1,1}) -- there is no third parameter Also, trigger.misc.getZone() only takes a single string parameter. local ref = trigger.misc.getZone("Novo", "Krymsk") -- only one zone at a time! I'm not seeing that you are actually using MiST (or CTLD) at the moment...

If you don't have the update, you will still have the same basic map, just with low-res areas: Normandy 2.0 FAQ

I use J-PEIN mounts for my desk. They are very solid (important so that the mounts don't move/twist when evading/maneuvering) and fit my TMWH just fine.

@cfrag I appreciate you catching my mistake (not enough coffee yet?) before I confused more than I helped! Maybe it should look more like the following, for simplicity: local function allGroupsDead() for _, groupName in pairs(groupList) do local group = Group.getByName(groupName) if group and group:getSize() > 0 then return false end end return true end

@MrBill If you know for a fact that there is only a single unit in a group that you want to keep track of, I'd suggest working at the unit level. Working at the group level is mainly for when you have an unknown number of units in groups. Keep it simple. If you know the unit names, as in your unitList variable, there is no need to use Group functions (unless you are doing something more complex). It seems like the question that you are trying to answer is, "are these two units still alive?" event.initiator is at the Unit level also, making it easy to determine what is going on in this case.

Here is some code to tell if units or groups are still alive: -- for units local unitList = {"Bandit1", "Bandit3"} local function allUnitsDead() for _, unitName in pairs(unitList) do local unit = Unit.getByName(unitName) if not unit or not unit:isExist() or unit:getLife() < 1 then return false end end return true end if allUnitsDead() then trigger.action.outTextForCoalition(coalition.side.BLUE, "All units dead!", 10) else trigger.action.outTextForCoalition(coalition.side.BLUE, "At least one unit alive!", 10) end -- for groups local groupList = {"myGroup1"} local function allGroupsDead() for _, groupName in pairs(groupList) do local group = Group.getByName(groupName) if group and group:getSize() > 0 then return false end end return true end if allGroupsDead() then trigger.action.outTextForCoalition(coalition.side.BLUE, "All groups dead!", 10) else trigger.action.outTextForCoalition(coalition.side.BLUE, "At least one group alive!", 10) end To answer your last question, if you only know the groups, then you need to evaluate each unit in each group. If you only know the units, then you can evaluate each of them.

I will be running DDR5 on Win10 next week as well (waiting for all the parts to arrive). We should have lots of feedback on real-world results.

MOOSE uses trigger.action.radioTransmission() under the hood, which accepts a vec3 point of origin. This point does not move once created. The transmission will always emanate from that singular point in the map.

fontdescription["font_MFCD"] = { texture = IndicationTexturesPath.."font_MFCD_A10C.tga", So the full path would be: [DCS]\Mods\aircraft\A-10C_2\Cockpit\IndicationTextures\font_MFCD_A10C.tga

I don't see a Gen5 M.2 for DCS in that list!

@Bog9y I know that @Elphaba did some research on how this could be accomplished, but it is ultimately up to ED to make the changes to the internal code: