All Activity

Currently we have it when we spawn in a MiG-29 in mission that all the heatseeking missiles are just starting their cool down, and are therefore unavailable for about a full minute. Can we please have it that upon a airstart, all R-27T R-73 and R60m's have already finished missile prep, and can be used as soon as spawning in? Thanks

With regards to getting DCS and peripherals like TrackIR and VR to run under Linux etc has anyone tried WinBoat? Unfortunately I don't know enough about Docker which WinBoat uses, and so far I haven't been able to get it to work. https://www.winboat.app/ Yes, I know it kind of defeats the purpose, as WinBoat creates a virtual instance of windows, but I'd be interested to see if anyone uses this or gets to work so we can ditch Windows completely which includes no longer needing a dual boot setup.

If your doing a air start engagement your R-73 will need a full minute to cool and become ready to slave to the IRST after you start and the mission unpauses So if you set up the airstart engagement close together in mission editor your R-73s won't work till well past the merge. For any other gameplay this a zero factor issue. Because you'll almost always hit master arm well outside a minute before engaging anyone...well at least hopefully. Also like with the French magic missiles there is no growl that increases with pitch. Once the seeker locks on you get a lock tone and the pylon station number of the locked on missiles will show on the bottom of your hud I've created a new topic for this in wish list, back to regular scheduled programing

Народ, извиняюсь, что поднял древнюю тему, но у меня попутный вопрос. Если позднее перестаешь пользоваться определенным джоем и созданная в настройках управления игры колонка для этого джоя начинает мешать, то есть ли вариант каким то образом эту колонку удалить, оставив только необходимые, скажем, для рус, руд, клавы и мыши?

Use PTT This thing is fun but pretty close to a SS if you know what I mean.

Hello, great campaign!!! For mission 8: 1) I tried the mission 8 twice but the JSOW never get a score, is there anything to kill on the DMPIs? 2) elevation for DMPIs are not correct in DTC, 273ft on kneeboard. 3) n4 landing first killed as well the guy at the de-arming area (not stopping).

When cold starting, you salute twice. First you report ready for engine startup, get a thumbs up, then you report ready to taxi once that's done. Also, you need to make sure the brownshirt is there to get startup permission. Sometimes, he'll be over at some other aircraft and you need to wait for him to walk over. He'll only react to the salute once he's at your plane.

Unit.getByName("Tank") → here "Tank" must be the Unit name, not the Group name. Group.getByName("Tank") → use this only if the Group is named "Tank" in the Mission Editor. I’m guessing the issue is that your unit might already be named "Tank". If that’s the case, let me know so we can fix it properly.

In the next DCS update, the F/A-18 will be getting a new DTC feature: RWR Reprogramming. The F/A-18 ALR-67 radar warning receiver (RWR) can only display 16 radar symbols on the DDI/AMPCD EW display or Azimuth Indicator; unless the LIMIT button is enabled on the ALR-67 control panel, which limits the display to 6 radar symbols. With these display limitations, the RWR automatically prioritizes these threats to ensure the most relevant radar threats are presented to the pilot. Up until this point, the F/A-18 RWR prioritized threats based on three tiers, with each subsequent tier out-weighed by the tier listed above it: Threat Lethality - All radars that are detected to be in a "Launch" mode in which the radar is likely guiding a missile are of a higher priority for display than those radars that are only in "Tracking" or "Search" modes; and all radars that are in a "Tracking" mode are of a high priority for display than those radars that are only in "Search" mode. Threat Type - The type of radar is prioritized according to the threat table uploaded to the RWR software. Those that are higher in the table are prioritized for display over those below it. Signal Strength - The strength of a radar's signal is weighted against others of the same radar type. If two radars of the same type are detected, the stronger signal will be prioritized for display over the weaker signal. These tiers of prioritization remain un-changed with this new DTC feature, but now players and mission makers have direct control over tier 2 and can reprogram the threat tables to suit the mission or their individual preferences. The F/A-18 RWR is reprogrammed by accessing the Threat Tables/Countermeasures (ALR-67) partition of the DTC and selecting the DIS TYPE tab. Five independent threat tables may be uploaded at once: NORM, AI, AAA, UNK, and FRND; and may be selected from within the cockpit at any time using the DIS TYPE knob on the ALR-67 control panel. Each individual radar type can be moved up or down in the displayed table using the arrow buttons along the right side of the table itself. The Display checkbox determines which threats are actually programmed into the RWR database. If any of these boxes are un-checked, the RWR will not be programmed to recognize these radar types. In this example, only the friendly coalition is equipped with Patriot SAM batteries, so that radar is un-checked to de-clutter that friendly radar type from the RWR display. The FRIEND checkbox determines which radar types are classified as friendly by the F/A-18's avionics. This not only affects the symbol presentation on the DDI/AMPCD EW display, but it also determines which AI threats (airborne radars) may be decluttered from the SA and ATTK RDR displays, depending on the FRIEND setting below PB 8 on the SENSORS sub-level of the SA display. The ASPJ XMIT checkbox determines which radar types are jammed by the F/A-18's onboard self-protection jammer if those radar types are detected to be in "Track" or "Launch" modes. This may be useful to focus your electronic attacks against specific threat types or to avoid shutting down your own FCR due to the ASPJ is transmitting when it would not be ideal. These threat tables are uploaded along with the CMDS programs by pressing the ALR-67 PB on the MUMI display.

Last I heard because Saab doesn't really need money right now

I know at one point Heatblur was proactive in asking SAAB. If I recall the datalink was the hold up?

Yes, it will be available for MSFS and DCS.

In the next DCS update, the F-16 will be getting a new DTC feature: RWR Reprogramming. The F-16's ALR-56 radar warning receiver (RWR) can only display 16 radar symbols in OPEN mode or 5 radar symbols in PRIORITY mode. With these display limitations, the RWR automatically prioritizes these threats to ensure the most relevant radar threats are presented to the pilot. Up until this point, the F-16 RWR prioritized threats based on three tiers, with each subsequent tier out-weighed by the tier listed above it: Threat Lethality - All radars that are detected to be in a "Launch" mode in which the radar is likely guiding a missile are of a higher priority for display than those radars that are only in "Tracking" or "Search" modes; and all radars that are in a "Tracking" mode are of a high priority for display than those radars that are only in "Search" mode. Threat Type - The type of radar is prioritized according to the threat table uploaded to the RWR software. Those that are higher in the table are prioritized for display over those below it. Signal Strength - The strength of a radar's signal is weighted against others of the same radar type. If two radars of the same type are detected, the stronger signal will be prioritized for display over the weaker signal. These tiers of prioritization remain un-changed with this new DTC feature, but now players and mission makers have direct control over tier 2 and can reprogram the threat table to suit the mission or their individual preferences. The F-16 RWR is reprogrammed by accessing the Threat Tables (ELINT) partition of the DTC and selecting the RWR tab. Two independent threat tables may be uploaded simultaneously, HIGH and LOW, which can be toggled from within the cockpit at any time using the ALT button on the Threat Warning Auxiliary control panel. Each individual radar type can be moved up or down in the displayed table using the arrow buttons along the right side of the table itself. The Display checkbox determines which threats are actually programmed into the RWR database. If any of these boxes are un-checked, the RWR will not be programmed to recognize these radar signals. In this example, only the friendly coalition is equipped with Patriot SAM batteries, so that radar can be un-checked to declutter that friendly radar type from the RWR display. The SEARCH checkbox determines which threats are hidden from the RWR display when the SEARCH button is not enabled on the Threat Warning Auxiliary control panel. These radar threats will still be recognized by the RWR, but will only be displayed and inserted into the priority ranking when the pilot enables SEARCH. This can be useful to hide any radars that cannot perform tracking or missile guidance functions, but can also be used to selectively hide any friendly radars while retaining those types within the programmed RWR database. The UNKNOWN checkbox functions identically to the SEARCH checkbox, but corresponds to the UNKNOWN button on the Threat Warning Prime control panel adjacent to the RWR Azimuth Indicator itself. This can be useful to hide any radars that the player wishes to selectively declutter from the display, such as friendly radars, naval radars, etc. These threat tables are uploaded by pressing the ELINT OSB on the DTE MFD format.

You will need both these in the description.Lua. The first is for the pilot in the plane and the other is for the pilot out of the plane. They use the same texture and texture file name but one is "details" and the other "getails". I'm not sure if ED made a typo or if it was intentional. Also is that my desert flight suit? {"pilot_F16_hmd_details", DIFFUSE , "pilot_f16_helmet_details", false}; {"pilot_F16_hmd_details", NORMAL_MAP , "pilot_f16_helmet_details_normal", false}; {"pilot_F16_hmd_details", SPECULAR , "pilot_f16_helmet_details_roughmet", false}; {"pilot_F16_hmd_getails", DIFFUSE , "pilot_f16_helmet_details", false}; {"pilot_F16_hmd_getails", NORMAL_MAP , "pilot_f16_helmet_details_normal", false}; {"pilot_F16_hmd_getails", SPECULAR , "pilot_f16_helmet_details_roughmet", false};

Der Schinderhannes - Die Geschwaderzeitung des Jagdbombergeschwader 35 Bericht der Woche 12.10.2025 - DCS REFORGER Die vergangene Woche markierte einen richtigen Meilenstein für das JaboG35. Wir haben nämlich erstmals eine DCS REFORGER Übung nach einem vollständig abgehaltenem Trainingszyklus abgehalten. Das bedeutet, dass wir als Geschwader eine ca 3 monatige Periode durchlaufen haben in der wir uns voll und ganz auf das Erlernen und Erhalten unserer Kernkompetenzen als Jagdbombergeschwader konzentriert haben. Diese Kompetenzen wurden uns im Zuge der DCS REFORGER Fighter Weapons Competition BULLSEYE'89 in einem mehrere Stunden umfassenden Sortie abverlangt, in dem wir beweisen konnten was wir können. Die durch das JaboG35 veranstalteten Events aus der DCS REFORGER Reihe stellen die Übungen dar, auf die das Personal des JaboG35 jeweils ca drei Monate lang hin arbeitet. In dieser bis zu 70 Teilnehmer umfassenden Übung positive Bilanz ziehen zu können bedarf alle Anstrengung die jeder Pilot aufbringen kann. Dieses mal sind wir als Aggressor Piloten für die durch technische Probleme verhinderten MiG-21 Aggressor Piloten eingesprungen. In unserem Sortie, der ca 3h lang dauerte, haben wir je Pilot ca 30 000 lbs Treibstoff vom Texaco Tanker im Luca Track gezogen und haben uns mehrmals mit den an dem Wettkampf teilnehmenden Geschwadern im 2v1 ACM Szenario gemessen. Mit 5 Air Traffic Controllern waren wir flugsicherungstechnisch ebenfalls bestens versorgt. Falls auch ihr Interesse an den DCS REFORGER Übungen habt könnt ihr hier mehr darüber nachlesen: Und wie gewohnt gibt es jetzt ein paar Bilder zur Veranschaulichung unseres Events vom vergangenem Wochenende. Viel Spaß damit! Von der Ramstein AB aus ging es erstmal in den LUCA AAR Track Dort waren wir auf Abruf bereit die beiden Lanes in der TRA205 mit jeweils einem Aggressor auszustatten Hier die Lead Maschine unserer Formation im Merge mit dem 2 Ship Harrier des 801st NAS Und das Engagement mit den 'Toros' des ALA17 in ihren MF-1EE Maschinen Die Kameraden vom 526th TFS haben bei der Competition einen hervorragend guten Eindruck gemacht Wenn dir dieser Post gefallen hat und du auch Lust auf das Fliegen in der Phantom in einer Milsim Staffel hast, die sich den 80er Jahren widmet, dann melde dich gerne bei uns auf dem Discord, oder bei mir hier im Forum via Direktnachricht. Das JaboG35 ist immer auf der Suche nach neuen Piloten und WSOs und wir freuen uns auf deine Bewerbung! Vielen Dank für's Lesen und bis bald, Rohrkrepierer o7

Der Schinderhannes - Die Geschwaderzeitung des Jagdbombergeschwader 35 Bericht der Woche 12.10.2025 - DCS REFORGER Die vergangene Woche markierte einen richtigen Meilenstein für das JaboG35. Wir haben nämlich erstmals eine DCS REFORGER Übung nach einem vollständig abgehaltenem Trainingszyklus abgehalten. Das bedeutet, dass wir als Geschwader eine ca 3 monatige Periode durchlaufen haben in der wir uns voll und ganz auf das Erlernen und Erhalten unserer Kernkompetenzen als Jagdbombergeschwader konzentriert haben. Diese Kompetenzen wurden uns im Zuge der DCS REFORGER Fighter Weapons Competition BULLSEYE'89 in einem mehrere Stunden umfassenden Sortie abverlangt, in dem wir beweisen konnten was wir können. Die durch das JaboG35 veranstalteten Events aus der DCS REFORGER Reihe stellen die Übungen dar, auf die das Personal des JaboG35 jeweils ca drei Monate lang hin arbeitet. In dieser bis zu 70 Teilnehmer umfassenden Übung positive Bilanz ziehen zu können bedarf alle Anstrengung die jeder Pilot aufbringen kann. Dieses mal sind wir als Aggressor Piloten für die durch technische Probleme verhinderten MiG-21 Aggressor Piloten eingesprungen. In unserem Sortie, der ca 3h lang dauerte, haben wir je Pilot ca 30 000 lbs Treibstoff vom Texaco Tanker im Luca Track gezogen und haben uns mehrmals mit den an dem Wettkampf teilnehmenden Geschwadern im 2v1 ACM Szenario gemessen. Mit 5 Air Traffic Controllern waren wir flugsicherungstechnisch ebenfalls bestens versorgt. Falls auch ihr Interesse an den DCS REFORGER Übungen habt könnt ihr hier mehr darüber nachlesen: Und wie gewohnt gibt es jetzt ein paar Bilder zur Veranschaulichung unseres Events vom vergangenem Wochenende. Viel Spaß damit! Von der Ramstein AB aus ging es erstmal in den LUCA AAR Track Dort waren wir auf Abruf bereit die beiden Lanes in der TRA205 mit jeweils einem Aggressor auszustatten Hier die Lead Maschine unserer Formation im Merge mit dem 2 Ship Harrier des 801st NAS Und das Engagement mit den 'Toros' des ALA17 in ihren MF-1EE Maschinen Die Kameraden vom 526th TFS haben bei der Competition einen hervorragend guten Eindruck gemacht Wenn dir dieser Post gefallen hat und du auch Lust auf das Fliegen in der Phantom in einer Milsim Staffel hast, die sich den 80er Jahren widmet, dann melde dich gerne bei uns auf dem Discord, oder bei mir hier im Forum via Direktnachricht. Das JaboG35 ist immer auf der Suche nach neuen Piloten und WSOs und wir freuen uns auf deine Bewerbung! Vielen Dank für's Lesen und bis bald, Rohrkrepierer o7

Questions here should be related to the FAQ if you are having issues or needing help, you would be better off starting a new thread. Thanks!

I can't really blame them feeling this way when the team has gone away and the CEO is nowhere to be found. People will always assume the worst because we aren't getting any clarity or signs of life. We have the entire RB situation and the grim reality of losing these 4 modules soon, and now the future of PC's modules from your customers perspective is that of uncertainty. I wish it could be taken a bit more seriously and ED as a company should try reaching out to PC for answers, if they're not fulfilling obligations to customers on their product. Please try to understand simply sending PC feedback of our concerns and having no tangible response to the myriad of concerns is not good enough in our eyes, and it should be taken pretty seriously by you as a CM and ED as a company. Just my thoughts, I'm trying to be as constructive with my concerns as possible. I really enjoy the OH-58 and would hate to also lose a 5th module (not saying it'll happen, but we will always assume the worst until we get a clear answer, and I hope you sympathize with us on this.)

I played alot around with the R-73s. I tried to engage ai ace MIG-23 with R60Ms and R-24s. i was nose hot until i saw smoke of his R-24. Then i cranked around 20-25 degree, put the nose down and set up for HELM mode. As we were closing to each other i got the dashed circle from the IRST, but i was never able to launch the R-73. Even under 5 miles. I repeated this, did the same, but this time i turned hot on him around 7nm. Same thing. No chance to release the R-73. It seems like a front aspect limitation to me. I dont know. Another big unsolved mystery for me is, that I never ever heard the typical sidewinder growling tone in that airplane.