Search the Community

Hello, I'm new here, but not to DCS World. My father loves DCS World but one thing pretty much takes away his ability to do many missions that require a hot jet. His game, regardless if it's in the air or on the ground hot setting, is ALWAYS cold and dark. For example, we start him in the air for a quick mission, cold and dark jet. Instant action on the catapult??? Cold and dark jet. I was able to help him get setup since his DCS download was incomplete. It didn't even have a Run.exe program. As far as I know it doesn't have an updater.exe but I can check with him. He's reinstalled twice to my knowledge but the problem persists. What do you guys think it is? Should I just tell him to raise a ticket? Or, since my DCS is doing well, just transfer some main files over to him? Thanks everyone, Sabre65

Is there any page or instruction covering the current damage model of the f-16? I am not sure if it's done properly or just you-get-hit-you-go-boom at the early access stage? Best,

Hi all, first post here on the DCS forums but have been at DCS for a while with the Hornet, Harrier and Viper, I'd like to share one of my creations! Should bring some nostalgia to some of you!

Playing a mission on Syria, I dropped 4 JDAMs from my f-16 and right when the 4th impacted I got a crash to desktop. Log zip folder included. dcs.log-20220327-012658.zip

yall ever notice the jingle when you turn on the RWR in the viper is to the tune of the first three notes of the theme to A Space Odyssey?? idk if its intentional or not lmaooooo, imagine the engineers designing the system having watched the film being like, hehe lets put that as the jingle XD

Всем привет. Некогда посетила меня идея попробовать сделать с нуля MFD панели как у F-16 с дисплеями. Хочу поделиться с сообществом результатом моих экспериментов. Возможно этот пост вдохновит на создание подобных элементов кокпита других вирпилов или может кому-то поможет упростить этот процесс, получив большую часть необходимой информации в одном топике. Вдохновило меня на это - видео от GENA PILOT: Настройка LCD экранов под TM COUGAR MFD для DCS. Идея заключалась в следующем: На 3D принтере сделать рамки MFD панелей с кнопками. На базе одного Arduino сделать схему джойстика на 56 кнопок под 2 MFD панели. Запрограммировать Arduino с помощью MMJoy. Разработать схему печатной платы под тактовые кнопки, которые поместятся в MFD рамки. Сделать печатную плату из фольгированного текстолита по ЛУТ-технологии. Найти подходящие LCD дисплеи на Ali Express и собрать все в кучу. Настроить кнопки и отображение MFD экранов из DCS на LCD дисплеях. 1. 3D печать рамок и кнопок. За основу были взяты 3D модели рамок с сайта: https://www.thingiverse.com/thing:3327543/files. Однако, модель имеет не оригинальные размеры, поэтому модель пришлось подгонять под чертежи. Кроме того, в модели есть множество мелких и не очень нужных элементов и пазов, которые могут криво напечататься, а использовать мелкие сопла или более дорогие виды пластика может существенно увеличить цену изделия. Также кнопки не имеют фасок и кнопки-качалки плоские, а в реале они вогнутые. В общем, методом тыка и с помощью какой-то матери я подогнал 3D модели под свою задачу убрав лишние и плохопечатуемые детали, а также немного улучшив модели кнопок: 3D модель MFD рамки 3D модель квадратной кнопки 3D модель прямоугольной кнопки-качалки Рамки решил печатать черным пластиком, а кнопки - прозрачным, с расчетом на то, чтоб сделать им еще подсветку. Важно! 3D модели кнопок имеют размер 1 в 1 под отверстия в рамке, поэтому их нужно печатать в масштабе 95-94% от оригинала, чтоб был зазор, иначе кнопки придется долго и нудно обтачивать на этапе постобработки, чтоб они "сели" на свои места в рамке. Результат получился таким: 2. Arduino и схема подключения В качестве основы для контроллера джойстика решил взять Arduino Pro micro на базе чипа ATmega32U4. Девайс вроде минимальный по размерам, а контактов достаточно для создания нужного числа кнопок. Каждая MFD-панель имеет 28 кнопок, соответственно для двух панелей необходимо по крайней мере 56 кнопок. В Arduino для настройки множества кнопок применяются схемы в виде матрицы состоящая из "строк" и "столбцов". Выглядит это примерно таким образом: Как видно из схемы для каждой кнопки также нужно подключать диод для того, чтоб Arduino смог определять какая из кнопок в "строке" нажата. Путем нетрудных расчетов для получения 56 кнопок нам необходима матрица из 8 строк и 7 столбцов. Итоговая схема для 2 панелей у меня получилась такой: 3. Программирование контроллера с помощью MMJOY Для программирования контроллера я использовал информацию и софт с сайта проекта mmjoy. Вкратце опишу процесс подключения, настройки и загрузки прошивки в контроллер исходя из текущей схемы. Скачай архив с актуальной версией MMJOY2 и распакуй в корень диска C (не рекомендуется, чтоб в пути к MMJOY была кириллица или пробелы). Подключи плату контроллера Arduino к компьютеру. Устройство должно определиться как Arduino Leonardo и должны установиться драйверы. Если драйверы не установятся, то установи их вручную через диспетчер устройств (devmgmt.msc), указав папку разархивированного MMJOY2 в качестве источника драйверов. Переведи в режим bootloader, для этого на плате ProMicro нужно кратковременно замкнуть и отпустить два контакта GND и RST. При этом в диспетчере устройств пропадет Arduino Leonardo и появится новое устройство Arduino Leonardo bootloader и в диспетчере устройств запомни номер COM порта, который отобразиться рядом с именем устройства. Через 8 сек. Arduino вернется в обычный рабочий режим. Запусти MMJoySetup.exe из распакованного архива MMJOY2. Перейди на вкладку "Прошивка". Укажи следующие значения в полях: Файл прошивки: C:\MMjoy2\Firmware\Firmware_lufa_[MMJOY2_ATMEGA32U4].hex Чип: ATmega32U4 Загрузчик: Arduino Порт: COM порт из предыдущего шага, например, COM4 (у тебя может быть другой порт!) Теперь переведи Arduino в режим bootloader замкнув кратковременно контакты RST + GND. После того как bootloader определится в системе поле с номером порта должно стать зеленым. В этот момент нужно сразу нажать "Загрузить прошивку". Если все сделано верно, то появится окно с терминалом cmd.exe в котором будет отображаться процесс загрузки прошивки. В результате в системе должно определиться новое устройство MMJOY2. Выбери устройство в "Список устройств и конфигурация". Изображение джойстика слева должно стать синего цвета, это будет означать, что MMJoySetup определил контроллер с новой прошивкой и готов к программированию. Перейди на вкладку "Настройка кнопок". И задай такие значения для рядов и строк, а также укажи напротив полей "Кнопка 1" - "Кнопка 56" соответствующие номера 1 - 56: Ряды и колонки соответствуют таковым из принципиальной схемы, которую я приводил выше. Только название контактов несколько отличается, от их маркировки на плате. Приведу, на всякий случай, схему какому контакту на плате соответствуют адреса в конфигураторе MMJoySetup: Нажми "Записать в контроллер". На этом программирование завершено. 4. Разработка печатной платы Печатную плату я решил делать сам "по старинке": фольгированный текстолит + трафарет на лазерном принтере перенесенный утюгом на плату + хлорное железо. Теплая, ламповая, Классика! Однако метод изготовления не принципиален. У меня было несколько идей какую именно конфигурацию платы использовать. Сначала я хотел сделать квадратную цельную плату, которая помещалась бы полностью внутрь рамки, однако из-за того, что у меня не оказалось подходящего инструмента, чтоб аккуратно выпилить такой квадрат в текстолите, и после нескольких неудачных попыток от такой идеи я решил отказаться, а вместо этого сделать 4 отдельные платки на каждую "грань" MFD панели, которые планировал соединить друг с другом проводами. Для реализации схемы нужен двусторонний текстолит, так как схема достаточно плотной получается, и на одной стороне все контакты не помещаются. Ближе к делу. Трафарет я нарисовал в sPlan6. На всякий случай выложу 2 варианта: Вариант цельной платы (требует доработок, так как в корпус MFD-рамки она не влезет!) Вариант цельной платы (PDF версия для печати) Вариант с 4 отдельными платами Вариант с 4 отдельными платами (PDF версия для печати) Background для sPlan схемы Нужно распечатать один из вариантов (рекомендую вариант из 4 плат) в 100% масштабе, желательно, на термотрансферной бумаге. Я печатал на мелованной бумаге (тоже пригодна для ЛУТ-технологии изготовления плат). Трафарет подготовлен таким образом, что при складывании листа одна сторона платы будет как-раз на своем месте над обратной стороной. При переносе тонера на текстолит, нужно очень точно расположить трафарет и желательно проверять "на просвет" что все дорожки на своих местах. 5. Делаем печатную плату Печатаем трафарет, утюжим, травим платы в хлорном железе: Лудим сплавом розе. Далее нужно аккуратно распилить плату на 4 отдельные, просверлить отверстия сверлом в 1 мм. Я использовал такую микродрель с цанговым патроном (на фото установлена фреза вместо сверла ). Отверстия в плате рассчитаны под тактовые кнопки TACT 6x6-4.3, высотой в 4,3 мм: Запаиваем кнопки и диоды по схеме. Диоды желательно использовать минимального размера. Впихнуть на плату их не просто. (Фото итогового результата распаянных элементов, к сожалению, я не сделал). 6. Подбираем LCD дисплеи Здесь я пытался найти 5-дюймовые квадратные дисплеи, чтоб максимально уменьшить колхоз, и приблизиться к оригиналу, однако ничего подобного я найти так и не смог. Поэтому остановился на аналогичном варианте на AliExpress, который предлагал GENA PILOT в своем видео (спасибо ему) в полной комплектации. LCD приехали ко мне за месяц: Робит! Убедись, что у тебя найдется 2 лишних HDMI порта на видеокарте 7. Сборка, настройка, проверка Платы спаиваем по схеме тонкими проводами. Фиксируем их на плате спермотермоклеем, так как они легко отрываются от посадочных мест. Проверяем, что все кнопки работают, и нигде не ошиблись на этапе пайки/прогроммирования. Тестировать удобно в MMJoySetup, выбрав контроллер из списка и перейдя на вкладку "Настройка кнопок". Нажми также "Считать из контроллера". Нажатие кнопок будет отображаться красным цветом. Подгоняем пластиковые кнопки и устанавливаем их в корпус MFD-панели. Если нужно дорабатываем их напильником надфилем и наждачкой. Устанавливаем платы в корпус MFD рамки. Фиксируем немного термоклеем по краям. Нужно убедиться, что кнопки встали ровно и нормально нажимаются. Если необходимо, "подравниваем" кнопки на плате, особенно это касается кнопок под "качалками", если впаять кнопки криво, то они могут плохо нажиматься. Если все ок - приклеиваем термоклеем основательно. LCD дисплеи я также аккуратненько по краям посадил на термоклей. Плату управления и контроллер LCD с обратной стороны экранов прикрепил на толстый двусторонний скотч. По 4 "жвачки" по углам платы, чтоб был зазор и плата как бы висела в воздухе (тут желательно под плату положить еще диэлектрик, так как корпус LCD металлический и можно легко замкнуть что-то на плате). Подключаем USB + HDMI к компу. Теперь нужно настроить расположение LCD экранов в конфигурации мониторов DCS. Для этого в папке DCS World\Config\MonitorSetup необходимо создать новый файл конфигурации мониторов. Здесь все индивидуально и зависит от разрешения и конфигурации ваших мониторов. В моем случае конфигурация такая (маленькие LCD в настройках Windows я развернул в вертикальное "книжное" положение, по умолчанию они используют "альбомное" отображение). Глобальные координаты рендера в DCS отсчитываются из верхнего левого угла самого левого дисплея. Поэтому необходимо подгадать координаты таким образом, чтоб каждый дисплей ровно отображал информацию и "вписывался" в свое место. В моем случае координаты получились такими: _ = function(p) return p; end; name = _('Camera + LMFCD + RMFCD + Custom'); Description = 'Left MFCD on the left, Right MFCD on the right and camera on the center' Viewports = { Center = { x = 768; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920 / 1080; } } LEFT_MFCD = { x = 60; y = 280; width = 688; height = 688; } RIGHT_MFCD = { x = 2748; y = 280; width = 688; height = 688; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Запусти DCS: Установи разрешение экрана исходя из суммы ширины всех дисплеев и высоты самого высокого. В моем случае это 768+1920+768 = 3456x1080. Выбери конфигурацию мониторов. Назначь кнопки OSB1 - OSB20 а также GAIN +-, SYM +-, BRT +-, CON +-. Результат Также записал коротенькое видео (снимал на кусок текстолита, за качество сорян) Имеющиеся косяки и планы На текущий момент я сделал только 1 MFD (для второго жду необходимые материалы, текстолит и прочую мелочь). Нет крепления, его я не продумывал и поэтому пока колхоз. Дисплеи не всегда с первого подключения определяются в системе (возможно у меня плохой кабель). В корпусе не предусмотрены нормальные посадочные места для платы, поэтому все держится на термоклее. Подсветку планирую сделать, но пока не знаю как. Внутри все довольно плотно, но что-то придумаю. На кнопках нет символики. Я планировал сделать трафарет и покрасить кнопки серой краской поверх трафарета, чтоб прозрачными были только символы и при наличии подсветки все было бы аутентичненько, но я пока не знаю как сделать такой мелкий трафарет с буквами SYM, GAIN и т.д. Внутри текущей рамки, есть посадочные места и отверстия под крепление, которые видимо планировал использовать автор 3D модели, однако мне они помешали и мне пришлось их спилить фрезой. Поэтому 3D модель, вероятно, придется оптимизировать с учетом этого недостатка. Расходы 3D печать 2 рамок с кнопками - $ 35 2 x LCD панели - $ 78 Текстолит, хлорное железо, диоды (FR207), кнопки (TACT 6x6-4.3) прочая мелочь ~ $ 10 Arduino Pro Micro - $ 8 Ссылки на файлы одним архивом: Яндекс Диск Google Drive MMJOY2 Конфиг дисплеев Camera+LMFCD+RMFCD+Custom.lua Пост писал на одном дыхании, так что мог что-то забыть/упустить. Задавайте свои ответы если что, буду рад ответить

Hi there, my question is kinda self-explanatory. I am a bit out of the loop regarding the F-16 flight model improvements. I believe there were *some* adjustments made in the second half of 2021, though I do not remember how significant those were. So, are more changes to the FM to be expected in 2022 or does ED consider the work on the F-16's FM to be fully complete by now? I am asking because I was surprised of how easily every single modern jet manages to get on my 6 in both 1 and 2 circle dogfights. I know the Viper is considered to be a great ratefighter (2C) and I *think* I am doing everything right, especially maintaining my speed, around 420-440kn in a sustained turn, yet I get killed over and over. I am by no means the best dogfighter, but frankly, neither are my friends, yet I always end up on the losing side whenever they get inside something different than an F-16. This is why I decided to ask here, hoping that someone more experienced would clear things up, as well as getting some info on the state of the Viper's flight model accuracy. Any feedback is appreciated!

Okay everyone thanks to @Middlefart for his main code, my wife for her expertise, helping me with this code for everyone looking for the F-16 Total Fuel gauge. All you need to do is add your code for your motors for the FWD/AFT pointers and your backlighting for your gauge. Easy and done! Hope this helps everyone!! This does work great on my seeeduino XIAO controller (DEFAULT_SERIAL only). Mega, nano, etc will work with IRQ_SERIAL. /* F-16 Total Fuel Gauge Thanks to: Middlefart (Original code), Fusion and Fusion's Wife (software engineer) Code is for the 128x32 oled i2c display. All you have to do is add your motor pins and guage backlight pins if desired. Hope this helps others! DCS-BIOS has made things far easier for DCS than software made to drive simulator components in FalconBMS. Glad to be apart of the DCS world. Matt "Fusion" G. */ //#define DCSBIOS_DEFAULT_SERIAL #define DCSBIOS_DEFAULT_SERIAL #include "DcsBios.h" #include <Wire.h> #include <Adafruit_GFX.h> #include <Adafruit_SSD1306.h> #include "characters.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); int AB; float Value1; float Value2; float Value3; float Total; unsigned long time = 0; unsigned int i = 0; //Comment for barometric pressure #define ALTIMETER int updateInterval = 100; //the number of milliseconds between updates struct scrollDigit { int digit; //The digit that is displayed int y; // The vertical position of the digit }; struct disp { Adafruit_SSD1306 display; int width; int numberOfDigits; scrollDigit digits[5]; }; //disp oled = {Adafruit_SSD1306(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, OLED_RESET), 24, 5, {{0,0},{0,0},{0,0},{0,0},{0,0}}}; disp oled = {Adafruit_SSD1306(SCREEN_WIDTH, SCREEN_HEIGHT, &Wire, OLED_RESET), 16, 5, {{0,0},{0,0},{0,0},{0,0},{0,0}}}; void setup() { if(!oled.display.begin(SSD1306_SWITCHCAPVCC, 0x3C)) { // Address 0x3C for 128x32 for(;;); // Don't proceed, loop forever } DcsBios::setup(); } void UpdateDisplay() { oled.display.clearDisplay(); for (int i = 0; i < oled.numberOfDigits; i++) { printScrollingDigit(oled.digits[i].digit, oled.width, oled.digits[i].y, i + 1, &oled); } //Clear the area below the the numbers if we are using the small font if (oled.width == 16) { oled.display.fillRect(0, 30, 127, 7, BLACK); } oled.display.display(); } int YPos() { return ((oled.width + 9) * -1); } void printScrollingDigit(int digit, int width, int y, int pos, disp *oled) { int x = (width * pos) - width + pos + 30; y +=5; switch (digit) { case -1: oled->display.drawBitmap(x, y, c16_0, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_1, 16, 24, 1); break; case 1: oled->display.drawBitmap(x, y, c16_1, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_2, 16, 24, 1); break; case 2: oled->display.drawBitmap(x, y, c16_2, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_3, 16, 24, 1); break; case 3: oled->display.drawBitmap(x, y, c16_3, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_4, 16, 24, 1); break; case 4: oled->display.drawBitmap(x, y, c16_4, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_5, 16, 24, 1); break; case 5: oled->display.drawBitmap(x, y, c16_5, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_6, 16, 24, 1); break; case 6: oled->display.drawBitmap(x, y, c16_6, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_7, 16, 24, 1); break; case 7: oled->display.drawBitmap(x, y, c16_7, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_8, 16, 24, 1); break; case 8: oled->display.drawBitmap(x, y, c16_8, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_9, 16, 24, 1); break; case 9: oled->display.drawBitmap(x, y, c16_9, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_0, 16, 24, 1); break; default: if (pos < 3) { oled->display.drawBitmap(x, y, c16_0, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_1, 16, 24, 1); } else { oled->display.drawBitmap(x, y, c16_0, 16, 24, 1); oled->display.drawBitmap(x, y+25, c16_0, 16, 24, 1); } break; } } void onFueltotalizer10kChange(unsigned int newValue) { unsigned int mappedValue = newValue / 6553; unsigned int y = map(newValue, mappedValue * 6553, mappedValue * 6553 + 6553, 0, YPos()); if (mappedValue == 0) { mappedValue = -1; } #ifdef TEST Serial.println(mappedValue); #endif oled.digits[0].digit = mappedValue; oled.digits[0].y = y; } void onFueltotalizer1kChange(unsigned int newValue) { unsigned int mappedValue = newValue / 6553; unsigned int y = map(newValue, mappedValue * 6553, mappedValue * 6553 + 6553, 0, YPos()); oled.digits[1].digit = mappedValue; oled.digits[1].y = y; } void onFueltotalizer100Change(unsigned int newValue) { unsigned int mappedValue = newValue / 6553; unsigned int y = map(newValue, mappedValue * 6553, mappedValue * 6553 + 6553, 0, YPos()); oled.digits[2].digit = mappedValue; oled.digits[2].y = y; oled.digits[3].digit = 0; oled.digits[3].y = y; oled.digits[4].digit = 0; oled.digits[4].y = y; } DcsBios::IntegerBuffer fueltotalizer10kBuffer(0x44e4, 0xffff, 0, onFueltotalizer10kChange); DcsBios::IntegerBuffer fueltotalizer1kBuffer(0x44e6, 0xffff, 0, onFueltotalizer1kChange); DcsBios::IntegerBuffer fueltotalizer100Buffer(0x44e8, 0xffff, 0, onFueltotalizer100Change); void loop() { DcsBios::loop(); time = millis(); if (time % updateInterval == 0) { UpdateDisplay(); } }

When performing a full aileron roll, with only lateral stick input, at the end of the roll the FLCS "pulls up" automatically up to a couple of Gs to bring back the nose (it seems) to the initial attitude. E.g. if you start the roll from a 10 degree nose up attitude and during the roll the nose naturally drops, at the end the aircraft automatically pulls the nose up to 10 degrees again, without any pilot input. This is not how the FLCS works, it never commands more than 1g by itself, and a roll should be just like in the Hornet or Mirage. See video and track (P.S. ED you shoudl REALLY increse the 5mb limit!) https://wormhole.app/d1QaN#qb6vr9jR_4tfw98iz7GncA

The 311 Squadron, is now recruiting for both the Fighter wing which currently use the F-16 Airframe and also the display team which is undergoing development as we speak. Join our discord today. We are not as intense as some groups and are looking for relaxed like minded pilots to join our ranks, we have a dedicated server, weekly missions and squadron liveries for you to enjoy. https://discord.gg/EGjycSZv2h **All pilots must be within 1 hour +/- of GMT to allow us to organise sorties**

Looking for a squadron with weekly campaign missions, realistic IADs, a great community to hang out in, and place to learn your aircraft? https://tvalhalla.com Join Us on Discord! Task Force Valhalla was founded as a place for DCS members to fly together in realistic, coordinated operations while minimizing the milsim nature of most DCS squadrons. While we do have ranks, they are solely tied to the proven proficiency in your airframe, and our squadron commanders are chosen by community vote for their dedication in their airframe. We try to democratize as much as possible in the Task Force and have representatives from all squadrons provide input and vote on any changes that affect everyone. We'd like to think our missions are unique, and we hope to get more active mission makers to increase the storytelling and depth available to our members. We currently use HighDigitSAMs integrated with Skynet-IADS in all of our missions, and implement realistic ROE and border patrols. We try to flesh out the ground environment as much as time allows and are experimenting more and more with voiced AIs! Currently we're midway through our first campaign, which is a police action in Georgia as Ossetian and Abkhazian forces attempt to obstruct the construction of a new pipeline in Georgia and unify as the Alanian Republic. Our campaign nights are FRIDAY, 9PM CST with briefing ramping up 30 minutes beforehand. We also have weekly scheduled training nights every Monday at 9PM CST. We just have a few basic requirements to join • Must be 18 years old to join • Must own the F-16, AJS37 Viggen, A-10CII Tank Killer, or Mirage 2000C OR be willing to own LotATC if you'd just like to GCI. • To fly in weekly ops, we require all members to pass a basic type rating in their chosen aircraft. This basically boils down to being able to takeoff, navigate, use the aircraft's most basic weapons, and land. Most people that have been flying the aircraft for about a week should be able to at least stumble through it successfully and you'll have someone who will help you through it. We're more than happy to train you even if you've never flown the module before or are new to DCS! • We have no attendance requirement, but we do require you to RSVP every week to let our dedicated mission makers have an accurate head count so they can tune the campaigns properly. 93rd Tactical Fighter Squadron "Outriders" Commander: Capt. Hex Director of Ops: M. "D20" Shepard Roster Limit: 18 Slots Available: 2 The 93rd Outriders were founded in September of 2020 as an offshoot of Carrier Strike Group 8, comprised of pilots that were looking to fly in Air Force operations with the F-16. The 93rd specializes in SEAD, DEAD and precision strike missions. We currently have 12 pilots on active roster and are always looking for more! 357th Fighter Squadron "Wyverns" Commander: Capt. R. Greyson Director of Ops: Vacant Roster Limit: 12 Slots Available: 4 The 357th Wyverns were founded in October of 2020 shortly after the 93rd. Much could be said about the 357th, but primarily it specializes in BRRRRRTing and supporting our allies armored divisions on the ground. We currently have 10 pilots on active roster and are looking for 2 more highly active individuals to fly weekly with us! 332nd All-Weather Fighter Squadron "Valkyries" Commander: Capt. Kora "Kortana" Director of Ops: N/A Roster Limit: 6 Slots Available: 0 - Recruiting Closed The 332nd Valkyries was founded by our fearless head of mission making Kortana in an effort to bring the joys of Mirage-ing to the masses. There was a noted gap in American time zone based communities for the Mirage and Kortana saw an excellent opportunity to put together a squadron for her favorite aircraft. Although aging and simpler than the F-16, the 332nd has been providing accurate and aggressive CAP for Task Force Valhalla with minimal losses. In the future we expect the 332nd to include the Eurofighter on it's release. F10 Angelholm "Ragnerok" Commander: Capt. K. Sakhir Director of Ops: Capt. R. "Bean" Green Roster Limit: 9 Slots Available: 0 - Recruiting Closed F10 Ragnerok brings the Viggens to a American friendly time zone and is Task Force Valhalla's surprisingly fastest growing squadron. F10 holds the special distinction of providing all of Task Force Valhalla's precision intelligence. Their ELINT missions are the only reason any flight can use a pre-planned target or has knowledge of the precise location of our adversary's mobile SAM network. When not performing ELINT, F10 has proven themselves as the best deep strike package in all of TFV. >>Our Website<< Discord Currently we institute an application process to screen members before they join. We do this because we want to make sure that applicants meet our age requirement, and that our operations actually meet the experience that they're looking for. It's also a good time to ask any questions you might have! Our application process is pretty straight forward: 1. Apply on our website 2.Join our Discord 3. Do 5-10 minute interview with someone from our recruiting team.

Hi Everyone, After the completion of the F-16CM Block 50, I'd like to request another F-16 variant; the F-16CG Block 40 circa late 80s/90s, before the CCIP (F-16CM) standard. I've chosen this F-16 variant in particular, because it is both a.) a historical variant suitable for a Balkans/Kosovo conflict (if we ever get an appropriate map for it), but also because the workload required to deliver such a variant should be fairly low at least in comparison to say, an F-16A (though I'd love that one too). Largely identical external model - the only differences being the removal of the JHMCS sensor and a different HUD, there'd also probably have to be a different pilot model. The only other difference that I can think of are the IFF antennae forward of the canopy, but don't hold me to that (AFAIK AIFF came with CCIP, though it's not like DCS models IFF with much fidelity anyway). Identical RADAR, as well as most other avionics: it has the exact same APG-68(V)5 FCR we have currently it has the same RWR (or at least a minor difference (ALR-56/ALR-56M, compared to the ALR-56M we have currently). The main difference would be no Link 16 and no MIDS, it also might have a different IFF system, though again, it's not like that is simulated with much fidelity anyway (though hopefully it will in the future). Identical FLCS and FDM; the only differences being the slightly lower thrust (but only by very little) F110-GE-100 on the Block 40, compared to the F110-GE-129 on our Block 50. AFAIK the F110-GE-400 on the F-14B, is essentially just an F110-GE-100 with a tailpipe extension. Pretty much identical cockpit, apart from the obviously the larger holographic HUD (with the ability to project NAVFLIR imagery from LANTIRN) and monochromatic MFDs though they have identical symbology AFAIK (just its all green, like that Tomcat's TID, instead of being mostly white). There are some other minor differences, namely the removal of the JHMCS sensor and control knob; as well as the removal of the DL and MIDS switches from the avionics power panel, the EHSI is replaced by mechanical one (identical to the one in the F-5E-3 AFAIK, with a control knob to the left instead of the single mode button). The rest of the cockpit is largely completely identical in form and function, the only other thing I can think of is that maybe the location of the oxygen control panel might have moved to be in between the avionics power and anti-ice panels, though the function and switches will be identical. We already have most of the stores and weapons already; just no LITENING, no AIM-9X and depending on the exact year you choose, you might not have AMRAAMs (AIM-120A was in service in 1991, B in 1994/1995 and C in 1996/1997). There would also be no JSOWs. The only other things we're missing are more fleshed out modes for the HARM, it doesn't have HTS compatibility AFAIK, but it would have GBU-24 (+ variants, at least the base GBU-24/B with a Mk84 warhead and the GBU-24A/B with the BLU-109 penetrating warhead). The main addition would be the inclusion of LANTIRN, including the AN/AAQ-13 navigation and AN/AAQ-14 targeting pods; the former includes a terrain-following RADAR (TFR), which can be coupled to the F-16s autopilot, allowing for automatic NOE flight at high speeds, its imagery can also be displayed on one of the MFDs (TFR page); it also includes a navigation FLIR (NAVFLIR), which can be projected onto the HUD or on the MFDs (FLIR page AFAIK); the latter TGP is broadly identical to the one currently present on the Tomcat, with only FLIR (which is lower resolution, with 2 FOVs + a digital zoom level) and a LTD/R (no TV or LST). The one in the Tomcat though is modified (known as LTS) to have an integral GPS/IMU and a ballistics computer, to generate coordinates and provide weapon release cues; now I'm not sure if the base AN/AAQ-14 can do this, though in any case the aircraft's native systems are able to provide this information (which isn't the case in the Tomcat).

Hi guys we are a virtual coalition group under the name DCS ANZUS a group based on the Australia, New Zealand and United states defence treaty. We are formed under two groups, The VRAAF (Virtual Royal Australian Airforce) and the USVDF (United States Virtual Defence Force) The modules we use are the Persian Gulf Map and for any carrier based Squadron we use the Super carrier. We are based in the AEDT and EST time zones in Australia and America respectively. We fly multiple Jets over two different services. RAAF Squadrons * 75th Squadron* Mirage 2000C * 68th Squadron* Shore based F/A-18 Hornet USVDF Squadrons VFA-143 Pukin Dogs Carrier based F/A-18 Hornets * VF-213 Black Lions* F-14B * 13th Fighter Squadron Panthers* F-16’s * 14th Fighter Squadron Swordfish* A-10C *12th Rotary Wing - Mi-8, UH-1 Huey We run Missions and Squadron training and are looking at running campaigns in the future. Most group activities occur at 1300 AEDT Sunday’s / 2100 EST Saturday. We have a dedicated scripted server and have Skins for each squadron and look forward to seeing you guys join. https://discord.gg/9xtmJ4tXFB

Hey everyone, I WILL UPDATE THIS REGULARLY WITH WHAT I AM WORKING ON NEXT Just making a quick post to inform all the Viper drivers that I have started a more advanced tutorial series for the F-16C in DCS. So far, I have gotten through the start-up, which is by what I have seen one of the most accurate and detailed videos on starting up the F-16C, I also just got done with a Taxi and Take-off video and I am currently working on the landing video. I am going to do a separate video going over more advanced portions of taking off and landing (i.e., taking off and landing with an asymmetric loads and belly landings). The videos I have currently made have already gotten a good reaction which is why I am making this post. My videos are aimed towards beginners and are even for people who have been flying the F-16 in DCS since release but even if you have been flying since release you might still learn something new. If you watch any of my videos, please feel free to correct something that you feel is incorrect or feel that it should be added. I know there are a bunch of tutorials and I have just about watched them all and none of them go into as much detail as mine, so I feel that what I am offering is new and refreshing especially if you want to operate and fly the F-16 to as close to its real-life counterpart as possible. So, check out the link below if you want to. DISCLAIMER: I am not a real-world fighter pilot by any means but due to my job as a Weapons Troop (AKA: Load Toad or 2W1) I have the amazing opportunity to talk with real-world fighter pilots of F-16s, F-15s, and even the F-22 (current jet I load on) and F-35. This opportunity allows me to cross reference a lot of info to make my videos as accurate as possible but yet easy to follow for even the newest of FNGs. Edit 20201224 - Landing Tutorial Released (Tried a different Resolution for phones) 20201224 - A2G Dumb Bombs ON HOLD 20220110 - JDAMs INW https://youtube.com/playlist?list=PLQ8wVOAAmWi1GbMSZk2u9godHWAjWLT47

After taking quite some time off on this project, it is time for a reboot. (wow that was in 2018 https://forums.eagle.ru/topic/188571-tm-cougar-sealed-magnetoresistive-hall-sensor-kits/?do=findComment&comment=3680810 ) This time a good friend of mine (trace) has joined forces with me and we have significantly improved the design structurally as well as the workflow. Since I was too lazy to 3D print these, now he is in charge of that. The pedals are plastic 3D printed, shaped to original F-16 specs and have two different settings for width adjustments of around 25mm (~1 in) difference. Print time is a ridiculous 22h per pedal. Each pedal has 4 high quality Ruthex metal inserts which are molten into the 3D print and can take quite a lot of force (over 2000N pullout). Furthermore, there is no wear after several screw cylces, so you can trial your favorite foot distance with good conscience. The surrounding structure of the inserts is significantly reinforced, so that torsion forces can be absorbed. Summarized, it should be rigid as hell! We have made one golden set of pedals just to show off, the production units are silver like the real deal. Here are some low quality pics my prototype version from 2018 installed on the Crosswinds. On the first pic it looks like the wider width setting was used, second pic shows the smaller width setting. They are printed of a filament which is a sort of chimera between PLA and PETG. They have pretty thick perimeters & top/ bottom layers and (I believe) ~30% infill. However, the internals are reinforced along internal force paths with an interesting method based on FEM. I borrowed the idea from this youtuber: https://www.youtube.com/watch?v=q0YsC53mFvY Please check out the videos demonstrating the strength of our construction below: click me Trace is doing the serial production, but printing will be on demand. The pedals are 50€ and shipping is about 20€ tracked internationally (depending on your country). Please send trace a PM if you are interested in a set!

JTF-111 is recruiting! Who are we: JTF111, is a US based - Air Force semi-milsim group. We are a laid back community who like to goof off and joke around in discord but we take it somewhat serious in the jet. We are primarily flying the F-16C, with plans to fill some A-10CII seats in the near Future! What we offer: Dedicated server at a datacenter in the Midwest LotAtc server with key Combat Flite mission planning. Custom Liveries OVGME Repository Our Aircraft: Our Primary Focus is the [F-16C] but we are actively seeking pilots for the A-10CII in support for the CAS role. Requirements for Joining: ((Age 18+)) Hotas, Head Tracking (VR, TrackIR, etc) English speaking, and own Persian Gulf, Syria, and NTTR maps. (Modules and Equipment may be acquired within 30days of recruitment) The majority of our Operators reside on the East Coast but we do not have restrictions on your geographical area as long as you can make Training and Mission nights. Our Trainings are currently held on Tuesdays 20:00 EST and our Missions are on held on Saturdays 20:00 EST. We do understand people have lives outside of DCS but we do ask that you give at least 24hrs notice before a scheduled flight if you will be absent as we will need to make adjustments in mission planning, etc. How to Join: Fill out an application at www.JTF111.com, join our Discord, and schedule an Interview with one of our Admins. If you have any questions feel free to join us on our Discord Channel. https://discord.gg/Crswbm8TPs

Unique to DCAF, we offer our Briefing And Training System(BATS). DCAF members will have a registered account, in which they can access our courses, independently study, be assessed, and track their progress. Additionally, users can view the overall roster of DCAF and view briefing documents for the upcoming weekly operations. As an insight, you can see what training for the pilot looks like(an additional post showing the training scope for controllers will be completed shortly): Having been enrolled to their airframe and registered on BATS, the user will have to complete V1. V1 is the training and assessment course needed to attend our weekly operations as a wingman. Although pilots joining will commit to their aircraft of choice for the duration of their training, DCAF’s training syllabus and SOPs are universalised as much as possible, being based on the principle of airmanship. V1 students will go through the V1 Learning Plan, as shown below: Each section contains lessons, which students are expected to read prior to assessment. Lessons include custom documentation, information and literature about the relevant subject. Once read, the student can contact an instructor of their airframe at any time for clarification, practice, or guidance. Once ready, students can sign up to be assessed in the activity. Instructors are more than happy to help energetic students who want to do more, and students should never feel guilty about chasing up someone to get an instructor slot! Below is a breakdown of each training objective within V1: Flight Familiarisation Flight familiarisation is often what other groups would define as a check-ride in demonstrating basic understanding. For us, we verify familiarity with the cockpit layout, startup, taxi, takeoff, straight and level flight, turns, climbs and descents, climbing and descending turns, steep turns, maintaining AOA in the landing configuration, low speed flight, stall recovery, spin recovery, descent and landing. This also tends to involve basic navigational competency. Visual Circuits Touch and go, touch and go, touch and go. Students will practise the military visual circuit, and the comms necessary to communicate intentions from startup to shutdown. Departures & Arrivals Building on the former, this reinforces understanding, and includes the procedure to leave the Military Aerodrome Traffic Zone, and how to appropriately rejoin it. Formation & AAR Arguably the most difficult part in core piloting skill. Cadets will be instructed and assisted in formation flying with appropriate references to their aircraft, and orderly departures and arrivals. Next, day and night air to air refuelling are on the agenda(!). Preview of one of the AAR graphics. Combat Operations This part starts to become more specific to the airframe. Instructors will teach you the individual weapon systems involved and how to effectively employ them. On completion, you will conduct your combat readiness assessment, to ensure that you meet the requirements as a wingman to take part in ops. Once complete, you have passed V1 and can take part in Thursday operations! After V1: From there, you have additional courses you can take, such as: - V2 – flight lead qualification - V3 – Instructor Pilot Qualification - V3* - Squadron Lead Assimilation - CLO – Counter Land Operations - AWI/BVR – All Weather Intercepts/Beyond Visual Range - BFM – Basic Fighter Manoeuvres - ACM – Air Combat Manoeuvring - CQ – Carrier Qualification - VSTOL Airframe Specific Training: Though the bulk of our training is universalised, there are numerous chapters available for your airframe of choice. These include ground school, SOPs, emergencies, and weapons employment. These are go to guides and instructional points to better adapt DCAF flows with the aircraft of your choice. A preview of some of the lessons one would find in airframe specific(F-14 Pilot Familiarisation) Expectations At the end of the day, the people we’re looking for are those who are keen to learn, and progress. It doesn’t matter where you are starting from, or how new you are to the sim. We have all the time in the world for members who want to actively improve themselves, and take advantage of everything we have to offer. If you’re someone who wants to learn, develop and build on skills to employ the aircraft at the most it has to offer, then our training syllabus and instructors are well positioned to get you there. For us we do this not only because we want more pilots in our ops, but because we take great enjoyment in teaching people. Training commitments are flexible, but you would be best served trying to keep a regular pace of training so you don’t fall back on the training you’ve already achieved. Regular Ops are conducted every Thursday 1830 GMT/BST Training: Sunday 1530GMT/BST and Wednesday 1830GMT/BST, and by appointment We employ the F-14, F-16, F/A-18, AV-8B, and are open to more controllers. If you’re interested and want to find out more, don’t hesitate to visit our website, and message us on our Discord: https://dcafoc.wixsite.com/home https://discord.gg/dcaf Want to apply?: https://forms.gle/fhxwzxAJVBjYfU779 After application, if we have capacity to take you on, we will provide you with an introductory presentation where you can learn more about what we do, and ensure that this is the right place for you. We want to make sure that everyone gets the best out of their hobby, and the introduction is part of establishing that. I look forward to hearing from you, Peter ‘Parker’ Anson

https://www.digitalcombatsimulator.com/en/files/3326132/ The aircraft consists entirely of Custom textures.

Before the FM update, the aircraft was underpowered, we can all agree on that. However after the FM update, it seems to me that the acceleration is way too high. I think they overdid it. Our variant block 50 shouldn't have such performance and I am worried that it's due to pressure from DCS' Nato community to get sales. I hope it's not the case and was wondering if anyone else thought the same or had other ideas about the F-16's current performance. I would welcome another look over and FM adjustment.

As it says in the title. The Physical switches within the cockpit in regards to external lighting do not appear to work correctly. The Fuselage Dim/Bright switch controls the tail light and the Wing/Tail light controls the Fuselage lights. It is impossible to change the lights on the wingtips without turning all external lights off. Anti collision lights seem to work as intended in that it does change blinks and can be turned off properly. Formation light brightness has no functionality and there are no formation lights. (This might not be implemented yet). When setting the aircraft to formation lights instead the wings blink white along with the anti-collision lights. When set to A-C, and all other lights off, the formation knob will adjust color strength on the wingtips. I honestly can't imagine that this is how the lights work on the actual F-16, there's no internal consistently at all.

Nothing really game breaking but just something I noticed. (F-16 Exhaust Demo track) When you place a F-16CM (1st in the line up) on the ground and make it uncontrolled it will have the correct nozzle position for a cold start. When you place a F-16CM as a "static" (2nd in the line up) aircraft it's nozzle position is showing it was shutdown in SEC mode. The "static" F-16CM nozzle position is incorrect and should be like that of the uncontrolled F-16CM. All the other "static" F-16s appear to be incorrect as well but they are much older statics so the texture looks a bit weird. At the end of the track I jump into the jet, start up, then place the engine into SEC and shutdown. What happens in DCS is the engine nozzle opens back up. What should happen is the nozzle should stay in the closed position. (F-16 Exhaust after landing Demo track) When you are flying and place the engine into SEC, then land and shutdown the engine nozzle again opens back up instead of staying in the SEC position (closed). I know the F-16 is not completely finished yet so this might get fixed eventually just thought I make a forum post because there does not appear to be one. F16 Exhaust Demo.trk F16 Exhaust after landing Demo 2.trk

is there any page on MFD or DED which suppose to show the Weight On Wheels ?

As per title, Ex: F-16: Engine Feed OFF - Oxygen Supply OFF - Mode 4 both out - Air Source OFF - Anti ICE OFF ... F/A-18: Oxygen Knob OFF - Bleed Air OFF - IFF Master OFF , Mode 4 OFF ...

A flyover has been requested by Las Vegas Speedway this weekend and your unit has been tasked with performing the show. Use the ToS/ToT feature and on your jet, communication and timing skills to perform a precise flyover for the National Anthem. This is a great way to train for Time on Target missions, or for those who love airshow flying. - Perform a precise flyover for the National Anthem at Las Vegas Speedway. - Fly either an F-18c or F-16c_50 - Approx. time: 25min (you'll spend about 10-15min holding and turning circles if you get up in the air too fast. This is designed to help people get into formation/position) - Practice holding in a position to wait for the ToT/ToS call. Try to maintain 45-60sec turns. - Fly either A 4-ship formation where your Lead is the only one concerned with ToT/ToS Or fly to separate waypoints and meet up over the center of the stadium at the exact time. - Communicate with your wingmen to deconflict altitude. The stadium already as fireworks and doesn't need more. - Don't rely on the carrot symbol on your HUD, but follow your directed Ground Speed to be more accurate. NOTE: This mission was made using Hasard Lee's youtube video "How Flyovers Work" as reference. I am not an actual pilot. Any comments/suggestions welcome. Thanks!

After seeing a VFC-13 livery for the MiG-29S on the User Files, I decided to see what a USAF clean-sheet 4.5 generation replacement for the F-16 might look like if it was a twin-engine design (unlikely, but possible). So I present the Bell/Boeing F-29A Kingcobra II, a 4.5 generation single seat, twin engine lightweight fighter for the USAF. If I can get hold of a suitable cockpit for this thing, I will make it available for download, but until then it will remain private. F-29A Kingcobra II Specifications: Crew: 1 Length: 17.32 m (56 ft 10 in) Wingspan: 11.36 m (37 ft 3 in) Height: 4.73 m (15 ft 6 in) Wing area: 38 m2 (410 sq ft) Empty weight: 11,000 kg (24,251 lb) Gross weight: 14,900 kg (32,849 lb) Max takeoff weight: 18,000 kg (39,683 lb) Fuel capacity: 3,500 kg (7,716 lb) internal Powerplant: 2 GE F424-100 Adaptive Turbofans (16,000lbf thrust dry, 29,000lbf thrust with afterburner) Armament: 7 pylons for up to 14 AIM-120 or AIM-9 air to air missiles, 20mm M61A2 Vulcan with 578 rounds Max Speed: Mach 2.5 Service Ceiling: 70,000ft Range: 1000 miles G Limit: 9 Thanks to Wyvern for the USAF Have Glass livery.