Matchstick

Not a problem - I'm certainly not interested in doing anything with your hard work without explicit permision :) Just a thought about tracking changes to the Misisons, would it be possible to add the date of the current version of the mission to the relevant section of the first post so people can compare manually even if it can't be done automatically ?

@Rudel_chw I've bundled up the Missions together with config to add them to a specific section of the Jf-17 Training Missions menu into an OvGME compatible zip file for my own use. Would it be OK to make this available to other people if they'd find it useful ?

If it wasn't available on the specific version of the F-16C Blk 50 ED are modelling (USAF/ANG 2007) then it's unlikely to appear in sim because ED have always stated they want to model that specific version as closely as possible rather than mix and match features . Maybe down the line they'll get to model other specific versions (personally I'd love a Blk 40 Night Strike version)

I still wasn't seeing the message pop up but "check JTAC status" did the trick - thanks for that :)

Brilliant, cheers for that :)

Is there a trick to getting the JTAC to trigger in Mission 07 - I gave it 10 minutes (I was playing with the AG RADAR GMTI in the meantime) but the JTAC didn't report in and I never got a designation to track ?

Brilliant (just to clarify I'm the UK but hopefully that won't cause a problem yet)

If you take the base I'd be very happy to buy the grip.

Hi, if the throttle is still for sale I could be interested - I'm in the UK so technically that doesn't count as EU any more but hopefully that wouldn't be an actual problem yet.

I'm definitely interested in these and in the UK. How much are you asking for them ? Cheers

Is there a definitive list anywhere on the net on payload info for the various versions Aviodev intend to model ?

If you have the Mi-8 and NS340 installed then you get two sets of Missions displayed on the Training Missions and Single missions page. You can also recreate the problem with a Custom Module containing missions with a attachMissionsToMods setting in entry.lua (I've attached the NS340/Mi-8 entry.lua file as an example) However on the Training Missions page there is a problem when you select from the second set where the selection bar is White rather than light Blue so you can't read the selected text (as shown in screenshot training_missions.PNG). Additionally on both the Training and Single Mission pages you can a missions selected from both sets of missions making it unclear which mission is the actual selected one. (As shown on both screenshot training_missions.PNG & single_missions.PNG) entry.lua

So what information do you have that says that this behaviour by the DCS HARM is incorrect ? It may well be that there's a problem so if you have an authoritative data source you can point to then maybe ED can include that information and improve the game.

Are you seeing any difference between the actual scan elevation positions in RWS vs TWS ?

I've spotted teh Vive Cosmos is down in price (on Amazon UK at least) to about the same price as the Reverb. Is that enought to make it a viable alternative to the Reverb ?

It'll be just fine for escorting attacking aircraft

I've created a modified version of the project with support for JF-17 UFC, Radio and AAP panels (also HUD display controls but only the Standby Reticule buttons work as there's no keyboard support for the others yet) . However the buttons are pure text at the moment because my artistic skills are somewhat.... lacking (though I did manage to create a logo for the front page) My fork of the repository is https://github.com/MatchstickUK/dcs

This would be same the day Windows 7 leaves support.... Whoops.

The Adafruit_SSD1306 supports I2C displays a well so if youre display works with that you could use the same code, just change the display definitions and constructor. eg replace #define OLED_MOSI 9 #define OLED_CLK 10 #define OLED_DC 11 #define OLED_CS 12 #define OLED_RESET 13 Adafruit_SSD1306 display(OLED_MOSI, OLED_CLK, OLED_DC, OLED_RESET, OLED_CS); with something like #define SCREEN_WIDTH 128 // OLED display width, in pixels #define SCREEN_HEIGHT 64 // 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); To find out what your display needs I'd try the I2C demos for the SSD1306 library and see what works for you.

Always good to have a spare F/A-18 when ones in the shop after a bad landing :)

DCS explicitly models in-flight INS alignment in the AV-8B N/A. It can take a long time and is suspended while the aircraft is pitching or rolling too much so it's preferable to align while stationary on the ground but it's an option when necessary

If DCS would like to follow up a competed Block 50 aircraft with a Block 40/42 one then I'd definitely be interested.

Are the Due/Zero compatible with the current version of DCS-BIOS ? It's on my list of projects to grab one for testing but there's quite a few things ahead of it :)

Sound like you may be running the older branch of DCS with the separate SOCAT app for communications. That version has now been superseded by the 0.10.x branch of DCS which is more of an integrated package that doesn't use a separate CMD app for communications. If you are still running the older version I'd suggest seeing if upgrading to the newer version fixes the problem. https://github.com/dcs-bios/dcs-bios/releases/

It's also a quick way to designate a secondary target in the same vicinity if, for whatever reason, you don't want to attack the primary.