All Activity

Yes it can be used in STT mode. Think of it as missile not working like SAHR/fox 1, but the radar using STT to send out datalink Do you have some source saying it can’t be used STT? AMRAAM can

There's a lot of bugs with radar, but what does it have to do with HSD data being rotated around 20 degrees?

Huh where you here this? My big question is will they fix the low G of the 29 from 870-1000 kmh. It can only pull like 7.5 G at best here. Real MiG-29 should be able to sustain 20 deg/s turn rate but right now only does 18.1 deg/s.

Talking about other navaids, I noticed that in the late 60's, Frankfurt had a vortac (58 "FFM" 112.1) who seemed to be near the middle marker of the runway 25.

Oh what... No way, here i was thinking I was about to be cool

DCS World developers should read it.

Most real female gamers that I've met, prefer to use non-femenine Nicknames and avatar pictures, to avoid unwanted male attention, so my hunch is that this one is probably not female ... maybe a male still in the closet?

There's also a small bug in mission 13, also similar. Since we're starting from the air, Armed is already active, so turning the switch to OFF and Arm doesn't cause the icon to disappear. It only worked for me when Radio F10 worked. A similar issue occurs at the end of the mission. Fence out - I turn out by Radio F10 menu, but the icon doesn't disappear at all until the next message related to the new PRI setting (hint about Radio).

It's still actively being worked on, just the Discord link is invalid. Maybe they'll make a more permanent one so it's easier for people to join

Discord invite is invalid. Has a halt on downloading this module been put in place? I've been trying for two days now.

yeah.... Nice! I read that story to my students. I make em sit though it

all these random new females bringing up old or dead thread with a new account that has 2 post... Obviously DCS is becoming a thing that women like now! Nice.

Den Thread gibt es doch schon länger ...

Hi, no I have not looked at Canted Rendering, please can you share what you have adjusted ?

не понял,как это не существует? У меня на ось шаг-газ назначено на РУДе вэкэбэшном и всё работает ...или ты про виртуальной рукой или тачем взяться за рычаг? я тачи не использую вообще,только РУС,РУД,пендали и мыкой в кабине тыкаю по кнопкам и тумблерам

Good workarounds, thank you!

dragonus said: Others say the resolution is similar, but they like the Q3's field of view and large sweet spot. Thanks for the reply, but at the risk of sounding like a loser! What is the sweet spot? And what's the difference between the Quest 3's and the G2's field of view?

@diego999 Dude! Thank you so much for helping me figure this out - Here is my mission so I am 90% sure it's human error! Can you help me figure it out? Russia_Finnish_Conflict.miz

Yes

В реальности Х-66 применялись только с МиГ-21ПФМ. Там был сделан специальный режим БРЛС для применения этой ракеты.

SYRIAN INCIDENT - DYNAMIC CAMPAIGN SQUADS vs. SQUADS From the creators of SATAC and pioneers of the first-ever squad dynamic campaign and public server with integrated stats dating back to 2011, 51st MDT proudly presents Syrian Incident, a groundbreaking event designed to revive large-scale squads vs squads multiplayer dynamic combat in DCS. Syrian Incident is not another public mission. It’s a fully dynamic, squads-versus-squads battlefield where your actions shape the outcome of the war. This campaign demands precision planning, flawless coordination between the squads, and exceptional execution. Each participating squad will follow carefully planed flight plans, crafted by their faction’s generals and commanders, as both sides fight for dominance in a constantly evolving battlespace. The time has come to signup and take part in the testing phase, where we evaluate not only the mission itself but also the readiness of the squads who will fly the campaign. This is your opportunity to prove your squad's capability in A2A, A2G, MR or Logistics operations while paving the way for what will be the most immersive campaign DCS pilots have experienced. The Syrian Incident is entering its final phase of development, ready to showcase what DCS was truly meant to be: a demanding, highly tactical experience where skill, strategy, and teamwork define victory. 1. Structure: The Syrian Incident is a squad vs squad multiplayer campaign based on the Fowl-Dynamic Campaign System, featuring strategic command options for participating coalitions. It offers an immersive and realistic combat experience set within a complex geopolitical military scenario. 1.1. The Syrian Incident consists of multiple events (referred to as “days”) in which squads participate. Assuming the role of one side of the conflict throughout the campaign, expected to run for several months. Each day is conducted once a week, with missions lasting approximately six hours. 1.2. Each coalition includes 8+ DCS squadrons specializing in both air-to-air and air-to-ground operations. 1.3. The Syrian Incident will feature major scripted events, introduced when tactically appropriate to enhance immersion. The timing of these events will be determined collaboratively by both campaign moderators and commanders, primarily for balancing purposes. 1.4. The Syrian Incident is subject to future updates and expansions under the Fowl-Dynamic Campaign System. 2. Basic Rules: Each coalition must appoint two individuals to serve as Commanders (Generals). These appointments may be revised later in the campaign if the original Commanders (Generals) are unable to fulfill their duties. 2.1. The position should preferably be assigned to a high-ranking and responsible squad member, capable of strategic planning, coordinating ground and air assets, and managing the distribution of reinforcement resources. 2.2. Each week, the Generals make critical tactical decisions by planning and executing operations that can significantly alter the operational landscape in the following Syrian Incident day. Sound strategic judgment is essential to achieving combat success. 2.3. Each coalition may field a maximum of 25 participating pilots per mission day. Pilots are limited to one life per mission. A disconnect occurring after takeoff will be considered a loss of the aircraft. Reserve pilots may be used to replace those who have been eliminated. 2.4. Mission conditions, including weather effects, will change randomly each day of operations. Time will advance in six-hour increments per mission day. SIGNUP: Signup on the 51st PVO Regiment Discord - https://discord.gg/Xm3h99jz8x Syrian Incident - Standard Operation Procedures - https://www.51pvo.com/s-i SI_Stinger.mp4

Я подписан на итальянскую ветку самолета. Там точно такие же сомнения синхронно наблюдаются. Это нормально. Спокойно отношусь к рискам сторонних разработчиков, учитывая, что ED вряд-ли бы вообще когда-нибудь дошли до Геркулеса. С другой стороны, есть ведь транспортный Чинук от ED, до которого они дошли. Но тут уже вступает в силу тот факт, что у ED самая монопольно-правдоподобная симуляция вертолётов.

If you don't mind me hijacking the thread a little, there are also some issues with NDBs on the map. Many of the NDBs located at the middle/outer markers for various airports have the same operating frequency in both runway directions, but the markers and NDBs are not interlocked based on the active runway (which they would be IRL, just like ILS). This is not an issue for the markers (which are all at 75 MHz) since they radiate a narrow beam straight up, but the NDBs can be difficult to identify by their ident codes (as the morse code for the two NDBs overlap) at long range, and are unstanble at short range, since your ADF will show erratic bearings. This may or may not be fixed when ED release their new ATC, but until then, I propose adding a 1kHz offset to every duplicate in the list below (where it doesn't cause any other frequency conflicts). E.g.: 313000 airfield2_2 LG Altes Lager 314000 airfield2_4 BM Altes Lager 645000 airfield2_0 L Altes Lager 646000 airfield2_1 B Altes Lager The duplicate list: Freq. BeaconID ID Airfield Notes 205000 airfield1_0 G Wittstock 205000 airfield1_4 O Wittstock 421000 airfield1_1 GJ Wittstock 421000 airfield1_6 OR Wittstock 219000 airfield15_0 P Templin 219000 airfield15_8 I Templin 451000 airfield15_4 PG Templin 451000 airfield15_6 IK Templin 221000 airfield101_0 - Sperenberg Invalid ident 221000 airfield101_3 NZ Sperenberg 254000 airfield101_1 Ch Sperenberg 254000 airfield101_2 - Sperenberg Invalid ident 295000 airfield118_7 X Holzdorf 295000 airfield118_8 H Holzdorf 609500 airfield118_2 XH Holzdorf 609500 airfield118_4 HX Holzdorf 300000 airfield22_7 Z Mahlwinkel 300000 airfield22_8 Z Mahlwinkel 620000 airfield22_3 NU Mahlwinkel 620000 airfield22_6 ZW Mahlwinkel 313000 airfield2_2 LG Altes Lager 313000 airfield2_4 BM Altes Lager 645000 airfield2_0 L Altes Lager 645000 airfield2_1 B Altes Lager 325000 airfield10_1 NZ Damgarten 325000 airfield10_5 M Damgarten 668000 airfield10_0 MA Damgarten 668000 airfield10_7 NW Damgarten 330000 airfield13_3 G Garz 330000 airfield13_5 G Garz 679500 airfield13_0 GZ Garz 679500 airfield13_4 ZG Garz 345000 airfield4_1 Z Zerbst 345000 airfield4_5 K Zerbst 708000 airfield4_3 KJ Zerbst 708000 airfield4_6 ZB Zerbst 350000 airfield82_1 GX Kothen 350000 airfield82_2 RX Kothen 718000 airfield82_0 G Kothen 718000 airfield82_4 R Kothen 365000 airfield157_2 LU Allstedt 365000 airfield157_3 BZ Allstedt 376000 airfield84_0 UU Parchim 376000 airfield84_3 AS Parchim 398000 airfield169_1 DK Merseburg 398000 airfield169_7 KD Merseburg 412000 airfield24_2 W Neuruppin 412000 airfield24_3 G Neuruppin 842000 airfield24_0 GK Neuruppin 842000 airfield24_1 WO Neuruppin 423000 airfield25_3 NE Peenemunde 423000 airfield25_4 EN Peenemunde 425000 airfield171_3 M Leipzig 425000 airfield171_4 S Leipzig 426000 airfield236_1 G Mockau 426000 airfield236_2 L Mockau 430000 airfield26_2 M Schönefeld 430000 airfield26_8 S Schönefeld 442000 airfield12_1 OM Finow 442000 airfield12_2 RG Finow 460000 airfield23_2 T Neubrandenburg 460000 airfield23_3 DK Neubrandenburg 476000 airfield21_0 U Lerz 476000 airfield21_4 B Lerz For the WSL or mingw64 users, all frequencies in the beacon file can be listed using grep "frequency" beacons.lua | sort (There is probably also some unnecessarily convoluted powershell command that can do the same thing)

Soviet livery, North Korean, GDR, Vietnamese livery -