Matchstick

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

Guessing from the look and LEDs this is intended as an replacement/upgrade to the Constellation grip ?

From what I've read the over the shoulder launch was at a target designated by a wingman via Link 16. Whether that strictly counts as LOAL or LOBL I'm not qualified to judge :)

Would an IR/UV MWS not give a warning if it comes within range while the missile motor is still burning ?

I know this is pretty old but if someone runs into the same problem with the UFC Comm Display, it looks like the issue is with how DCSBios is outputting the 1x and 2x characters. The 1 is being sent as with a "`" and the 2 is being sent as "~" There's probably a very good reason for this and all I did to get around it is use Switch & Case to detect the characters and swap them out - that's in the cleanUpCom method of the code below, which is what I'm currently playing with to display both Com values on a single OLED. (note I'm using the smaller 128x32 OLED display so if you're using a larger one you'll need to change the SCREEN_HEIGHT definition) #define DCSBIOS_IRQ_SERIAL #include <DcsBios.h> #include <SPI.h> #include <Wire.h> #include <Adafruit_GFX.h> #include <Adafruit_SSD1306.h> #define SCREEN_WIDTH 128 // OLED display width, in pixels #define SCREEN_HEIGHT 32 // OLED display height, in pixels // Declaration for an SSD1306 display connected to I2C (SDA, SCL pins) #define OLED_RESET -1 // Reset pin # (or -1 if sharing Arduino reset pin) Adafruit_SSD1306 display(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, OLED_RESET); void setup() { count = 0; display.begin(SSD1306_SWITCHCAPVCC, 0x3C); display.clearDisplay(); display.setTextSize(2); display.setTextColor(WHITE); display.setCursor(0,0); display.cp437(true); display.print("Start"); display.display(); DcsBios::setup(); } void loop() { DcsBios::loop(); } String comDisplay[2]; void updateComDisplay(int changed,char* newValue) { comDisplay[changed] = cleanUpCom(newValue); display.clearDisplay(); display.setCursor(0,0); display.print(comDisplay[0]); display.setCursor(35,0); display.print(comDisplay[1]); display.display(); } char* cleanUpCom(char* newValue) { switch (newValue[0]) { case '`': newValue[0]='1'; break; case '~': newValue[0]='2'; break; } return newValue; } //Comm 1 void onUfcComm1DisplayChange(char* newValue) { updateComDisplay(0, newValue); } DcsBios::StringBuffer<2> ufcComm1DisplayBuffer(0x7424, onUfcComm1DisplayChange); //Comm 2 void onUfcComm2DisplayChange(char* newValue) { updateComDisplay(1, newValue); } DcsBios::StringBuffer<2> ufcComm2DisplayBuffer(0x7426, onUfcComm2DisplayChange);

Just retested and Training Mission 02 wasn't letting me get beyond SAAHS test. BTW is there any way to update the training mission so that selecting the MPCD buttons via Cougar MFD panels is detected in the mission and you don't always have to click on the button in the 3D view ?

Did seem to be stopping the mission for me I'll try to retest tonight and confirm if that is the case.

JUst to mention I'm getting the same problem with the SAAHS BIT test section of M02. Is there at least a way to skip past this and continue with the mission ?

Hi, would you consider selling the grip if you don't have any luck finding a swap ?

If the updated default.lua file is fixing the problem binding keys does that mean the Visor button can now be changed to a different key to Magic Select ?

Mounting 2 side by side on a 11.6" 16:9 monitor is probably the simplest solution at the moment but one day someone will find/make a display that fits perfectly and there will be much rejoicing :)

That's weird, is it a module that's transferable from Stream so you could maybe get it that way if nothing else works ?

I've just picked up a Virpil WarBRD base and I'm looking for a half decent grip to go with it, so if anyone has a Warthog Grip they don't need after upgraging to the F/A-18 or evem a MongoosT-50CM2 Grip let me know. I'm looking for UK or EU since the postage cost are likely to be a problem elswhere

PM sent

I'm probably being really really stupid but while the HUD is showing you are at the correct altitude in the screenshots isn't the Flight Directory needle on the ADI showing you are below the commanded altitude (horizontal indicator above the horizon line) ?

Yeah I'd expect the C and maybe E to be the first version released and the M to only come along a while later to allow for development of the extra toys.

Quick play with the dimensions of MFD listed on the diagram on here suggests you'd be looking for a monitor about 400mm wide. Plugging that into here suggests an 18.5" 16:9 monitor might do the job There look to be a reasonable number of cheap monitor out there of that size but they tend to be low resolution - 1366x768 or so - which I think would give you something around 350x350 pixels for each MFD

The fact people are selling them for that much, doesn't mean anyone is actually buying them :)

While that sort of capability is restricted to a relatively small number of graphics cards it doesn't seem practical to have as anything other than a single player only option.

There's an update in the usual thread in Chit-Chat https://forums.eagle.ru/showpost.php?p=3936888&postcount=2527

Welcome to the internet :)

It might just as unexpected to ED as it is to us.

Just watching the latest JSOW Training video from Wags and that's showing multiple colours on the Right DDI.

I don't think so, I think he's referring to people who have any version of BS2 getting a much cheaper upgrade to BS3 than people will pay to buy a brand new copy of BS3

I don't know much about modern helicopter doctrine but I'm guessing your primary defense against fighters would be making the most of ground clutter and terrain masking.