Matchstick

If it's still available I'll take the whole package

That is fantastic, a pack of those has done the trick perfectly with enough spares not to worry if I strip any more heads. Cheers,

There should be code to do that in this post https://forums.eagle.ru/showpost.php?p=4087679&postcount=1051

Cheers for that - I'd screwed up the item name for teh asterisks on Line 3 so they were being triggered by ths asterisks appearing on Line 2. As with the CMDS and Backup UHF Radio the change has been sumbitted but if you want to make the fix yourself search for the line DEDLayout_l3["STEERPOINT Latitude Asteriscs_both"] = {7,1,20,"","I"} and replace it with DEDLayout_l3["STEERPOINT Longitude Asteriscs_both"] = {7,1,20,"","I"}

I'm guessing you are talking about the Numbers on the CMDS and Backup UHF Radio displays. I've created the code for this and passed it along to be added to the main release. In the meantime if you want to add the code manually you should add the following to the DCS-BIOS F16C_50.lua script (I put it at the bottom just about the Externals section) ------------------------------------------------------------------CMDS Display-------------------------------------------------------------------------------------- local CMDS_O1_Amount local CMDS_O1_Amount local CMDS_O2_Amount local CMDS_CH_Amount local CMDS_FL_Amount moduleBeingDefined.exportHooks[#moduleBeingDefined.exportHooks+1] = function() local cmds = parse_indication(17) CMDS_O1_Amount = " " CMDS_O2_Amount = " " CMDS_CH_Amount = " " CMDS_FL_Amount = " " if not cmds then return end CMDS_O1_Amount = coerce_nil_to_string(cmds.CMDS_O1_Amount) CMDS_O2_Amount = coerce_nil_to_string(cmds.CMDS_O2_Amount) CMDS_CH_Amount = coerce_nil_to_string(cmds.CMDS_CH_Amount) CMDS_FL_Amount = coerce_nil_to_string(cmds.CMDS_FL_Amount) end defineString("CMDS_O1_Amount", function() return CMDS_O1_Amount end, 4, "CMDS", "CMDS O1 Amount Display") defineString("CMDS_O2_Amount", function() return CMDS_O2_Amount end, 4, "CMDS", "CMDS O2 Amount Display") defineString("CMDS_CH_Amount", function() return CMDS_CH_Amount end, 4, "CMDS", "CMDS CH Amount Display") defineString("CMDS_FL_Amount", function() return CMDS_FL_Amount end, 4, "CMDS", "CMDS FL Amount Display") ------------------------------------------------------------------UHF Display-------------------------------------------------------------------------------------- local function get_UHF_CHAN() local UHF = parse_indication(11) if UHF and UHF.txtPresetChannel then return coerce_nil_to_string(UHF.txtPresetChannel) else return " " end end defineString("UHF_CHAN_DISP", get_UHF_CHAN, 2, "UHF", "UHF CHAN Display") local function get_UHF_FREQUENCY() local UHF = parse_indication(12) if UHF and UHF.txtFreqStatus then local UHF_Freq = UHF.txtFreqStatus local UHF_dot = UHF.txtDot return UHF_Freq:sub(1,3)..UHF_dot..UHF_Freq:sub(4,6) else return " " end end defineString("UHF_FREQ_DISP", get_UHF_FREQUENCY, 7, "UHF", "UHF Manual Frequency Display")

Hi, I'm currently doing work adding the DED display to the DCS-BIOS module and it's working but I'd like to request that devs working on the module try to ensure they use unique names for different fields especially ones that appear in different places on the display. All the info defining what's displayed on the DED and where is held in then .lua files under \mods\aircraft\F-16C\Scripts\Displays\Common\indicator\DED\Pages The main page is defined by CNI.lua and that contains the item addText("WPT IncDecSymbol", "a", {19, 0}, nil, nil, {{"DED_CNI_IncDecSymbolPos", 0}}) which is the up/down arrow and will be shown on line 1 in postion 20 (in programming half the code has lists begin at 0 and the other half has them begin at 1 - this code looks to be the former) However the ALOW page contains addText("WPT IncDecSymbol", "a", {23, 0}, nil, nil, {{"DED_CNI_IncDecSymbolPos", 0}}) and the CMDS_BINGO page contains addText("WPT IncDecSymbol", "a", {23, 0}) Both of which display the same symbol on line 1 but at a different position and since there doesn't look to be obvious metadata indicating which page is being displayed it's getting tricky to work out which version of the item is the correct one to display. There are also other items that share names on the COM, IFF & ALOW pages so anything that help remove these duplicates names and avoid them in the future would be a big help/ This is a REALLY small hill to die on I know but once complete the DED will contain thousands of possible data items so anything that makes itv

the code I'm using in F-16C_50.lua to is local generalReplacements = { ["a"] = "@", ["o"] = "^" } local formatReplacements = { ["*"] = "×", [" "] = ";", ["0"] = "À", ["1"] = "Á", ["2"] = "#", ["3"] = "$", ["4"] = "%", ["5"] = "&", ["6"] = "\'", ["7"] = "+", ["8"] = ",", ["9"] = "-", ["."] = ">", ["a"] = "<", ["o"] = "°" } ----------- ------------------------------------------------------------------DED Display Main Function------------------------------------------------------------------------- local function buildDEDLine(line) -- Get Layout Information for line being built local DEDLayoutLine = DEDLayout[line] -- Get Exported DED Objects local DED_fields = parse_indication(6) local layout local label local value -- Base Output String local dataLine =" " -- Check for present of Objects that indicate Duplicate Key Names that need resolving local guard = DED_fields["Guard Label"] local mode = DED_fields["Mode label"] local event = DED_fields["Event Occured"] local alow = DED_fields["ALOW label"] local bingo = DED_fields["CMDS_BINGO_lbl"] --Loop through Exported DED Objects for k,v in pairs(DED_fields) do -- Handle Duplicate Key Names on COM2 Guard page items if guard ~= nil then label = guard.." "..k -- Handle Duplicate Key Names on IFF STAT page items elseif mode ~= nil then label = mode.." "..k -- Handle Duplicate Key Names on IFF POS & TIM page items elseif event ~= nil then label = event.." "..k -- Handle Duplicate Key Names on ALOW page Line 1 items elseif alow ~= nil and line == 1 then label = alow.." "..k -- Handle Duplicate Key Names on CMDS Bingo page Line 1 items elseif bingo ~= nil and line == 1 then label = bingo.." "..k else label = k end --Get layout data associated with current key layout = DEDLayoutLine[label:gsub("_inv","",1):gsub("_lhs","_both",1)] if layout ~= nil then local tempValue --If layout value 6 is present then use this value to override the value returned from DCS if layout[6] ~= nil then tempValue = layout[6] else tempValue = v end --If layout value 5 is present then use this value to populate the Format section of the output otherwise return "" if layout[5] ~= nil and (layout[4] == "" or layout[4] == label:sub(#layout[4]*-1)) then if layout[5] == "I" then value = tempValue:gsub(".",formatReplacements):lower() end else value = tempValue:gsub(".",generalReplacements) end -- Add Value to dataLine using mergeString because some values are are supposed to fit within others dataLine = mergeString(dataLine, value, layout[1]) --If layout value 3 > 0 we need to duplicate this item at position specific in value 3 (this is for "*"s marking enterable fields if layout[3] ~= nil and layout[3] > 0 then dataLine = mergeString(dataLine, value, layout[3]) end end end return dataLine end In practical terms it just checks that the data needs inverting (either the end of the label is "_inv" or the field is always inverted) and then substitutes characters in the string so I pick up the correct custom character from the custom font

I have inverted text working for the DED but only by using a custom font. When I tried getting the Arduino to programatically turn on and off the inverted text it was taking so long the line was being updated before it completed printing so over the weekend I created a Custom version of the default Adafruit GFX font containing the inverted character. Unfortunately this custom font isn't compatible with the custom font that DCS-BIOS contains because I'm using a different graphics library, but if you are set up to use the Adafruit GFX library I can pass you over what I have.

Got it - I hadn't spotted that the ALOW and CMDS BINGO pages had identically name Steerpoint and Steerpoint Inc/Dec symbol items with different positions and the export was picking up the layout info from those items when displaying the CNI page. I've updated my code to make sure those fields have unique names so that should go live in a future update but if you want the updated code in the meantime give me a shout

Yeah there's something weird there. The layout should be putting the up/down indicators before the Steerpoint so I'll have to have a look at what's going on later today.

Lovely, looks like that can be mapped onto the Cougar HOTAS pretty much identically to the F-16

I've created some code to do basic export of the DED panels and that will hopefully be availablein the DCS-Flightpanel fork of the code soon. It currently only exports the data without formatting like inverse and oversize characters because I haven't found a way to render that on the Arduino fast enough to avoid problems with the data being updated while it's still being written to the screen.

I need some replacement for the 4 Centre Screws on the Cougar Throttle, does anyone know the details of what type of screw they actually are ?

I'm almost exclusively an SP player so I definitely like the look of the realistic IFF modes but from watching discussions of MP IFF issues on Reddit and Discord, etc I also think there has to be an option to switch to a simplified system (And if time is an issue I'd lean toward implementing the simplified system first.)

Virpil have just annoucned they are doing an update of the T-50CM throttle. New version look to have a be smaller smaller base & be cheaper but with somewhat fewer controls (particularly on buttons and rotary axis) No mention of detents so presumably this version won't have them, either. https://virpil-controls.eu/vpc-mongoost-50cm2-throttle.html There's also a bracket for fitting it to Warthog throttle mounts https://virpil-controls.eu/vpc-mongoost-50cm2-throttle-tmw-throttle-mounting-adapter.html Plus they are now releasing a 200mm S-bend extension and will no be taking Credit Card payment for Pre-orders https://forum.virpil.com/index.php?/topic/897-pre-orders-update-and-unveiling-the-vpc-mongoost-50cm2-throttle/

It would seem a pity for any new Mig-29 module to continue using the non-clicky cockpit & simplified systems of the current FC3 Mig-29.

Back at the original topic of the thread the Warbrd base and grip are no longer on sale but the MongoosT-50CM2 Grip is now10% off

Personally I don't care about the texturing compared to the system, avionics, flight modelling etc. If it looks nice that's a bonus but it's no even closer to the heart of a sim for me

I'm trying to wire up a couple of rotary encoders to control the Comm1 and Comm2 knobs on the F/A-18 (and AV8BNA) UFC. The ones I have in my bits drawer were a couple of KY-040 encoders but these appear to be triggering the channel change 4 times per detent (is the code actually firing with each of the individual changes per encoder pulse ?) Has anyone encountered and solved this problem ? Or am I better off ditching these encoders and getting something better - which case what part suggestions do people have ? Cheers EDIT -- Forget all about that, I just found the stepsPerDetent_ parameter in Encoders.h and the fact it defaults to 1. Sorry about that.

I know this is a year old but in case anyone else finds this thread trying to get Witchcraft running, you need to delete the contents windows\nodejs folder that's included in the Mod and replace it with a more recent version of node.JS I downloaded LTS 32Bit Windows Binary version from here https://nodejs.org/en/download/ then extracted all the files and folders into the mode windows\nodejs then ran windows.cmd again and it worked first time.

Wonder if that dual trigger could be mapped to operate the safety on the Viggen ?

Which 7" displays are you getting ? I'm currently using an 10.1" 1080p display with 2 MFDs on it side by side but I'd like to add an extra one for the Hornet AMPCD

That's just what I'm thinking - it won't appeal to simmers who want the most accurate sticks possible but for people looking to support both flight and space sims in a single grip it looks like it could be a great option. (For me at least a CM2 with twist axis, 8-way hat swapped for an analogue stick and a button swapped for a rotary encoder wheel would look to tick a lot of boxes for a lot of different roles)

If anyone is also looking to get the numeric Nav panel data via DCS BIOS it looks like the changed I came up with to add them to the export have been added to the DCSFlightPanels fork of the code https://github.com/DCSFlightpanels/dcs-bios