All Activity

For me it's still like pulsating sound of turbulent air.

@NineLine bump....

Minor correction: see also 01.0.320. R-73 as well

Um nochmal etwas "harte" Fakten beizusteuern: Mir ist nur ein einziger belastbarer Direktvergleich zwischen aktuellen AMD/Intel CPUs in DCS bekannt. Ich glaube das war 12te Generation Intel gegen die damals aktuelle AMD Konkurenz. Weiß gar nicht mehr wer da die Nase vorne hatte, aber das Interessante an dem Benchmark war, dass die Performance mehr oder minder der erwarteten durchschnittlichen "Gamingperformance" entsprach. Dass DCS sich jetzt vollkommen anders verhalten soll als übliche Spiele schien damit also widerlegt. Von daher scheint AMD erstmal die bessere Wahl zu sein. Wenn du ne Intel CPU aber stark reduziert bekommst, kann Preis/Leistung natürlich trotzdem sehr gut sein! Ich würde ne aktuelle AMD X3D Variante mit Single-Chip-Design empfehlen - also nicht zwingend die Größte, die dann aus zwei Chips zusammengeschustert wäre...

It's done when it's done. I'm confident that Aerges has full control. Correct me if I'm wrong, but they said the new updated radar model will come with the M and trickle over to the other versions? Pretty sure this is what takes up most of the time and efforts. Sent from my SM-A536B using Tapatalk

Modelling suppression fire mechanics against AI. Would be very cool in helo ops but useful for any type of vehicle or aircraft your playing as, would be especially cool when flying the CH-47 or Mi-8 into simulated hot LZs or passing near enemy infantry in wooded areas. Lay down a little cover fire in the general vicinity, to cause the AI to pause for a few seconds and rethink their virtual life.

Еще заметил что пуск Р73 в горячем старте в воздухе не возможен по истечении 1 минуты после старта миссии, то есть у нас при старте оружие не готово и скорее всего оно охлаждается. Также не возможен пуск ракеты без предварительного захвата КОЛС, если захватывать с помощью тгс ракеты. Потом уже можно и тгс ракеты наводить и стрелять Так же почему то сектор захвата ракеты ограничен +-45 гр. В гс3 миг29, проверял сегодня, команда ПР выдается тоже в этих пределах, но можно снять ограничение на пуск и стрелять вплоть до+-60гр сколько шлем по азимуту предоставляет

Приветствую вирпилов и разработчиков, после последнего апдейта заметил что при использовании ракет Р73 в режиме ШЛЕМ, когда смотришь на цель более 30 градусов относительно носа и пытаешься произвести захват, то на шлем ничего не выводится и нет звукового сигнала и надписи на ИЛС "ПР". Хотя при этом появляется на ИЛС номер ракеты которая захватила цель и ее можно пустить. nullnull R73andHELM.trk

The tracer is optional and enables visual tracking of R-27 and R-60 which is indicated by the fire of red or orange color. for R-27 tracer is placed in the wing. For R-60 in tail section. Can this be added to the weapon load dialog when re-arming? 01.VTUP.001 01.0.319

Thanks. I am familiar with this document on the basis of which you created the video. And I know these nuances. My goal was that the indication of the sights is not entirely correct, there are other documents in the public domain, one of them describes the operation of HMS. The picture with dotted rings, this is the designation of a flashing ring in the documentation, and not a real dotted ring. Structurally, sights are formed on two prismatic mirrors, on one side of both there is a template of a symbol as a stencil, and above it a lamp. A solid aim ring mark and a solid signal cross mark, and no dotted lines like a module. You can still find such documents on various specialized forums on the Internet, but they are in poor quality and written in Cyrillic.

Okay, so I got a success this time. I shot down 6 bombers between myself and my wingman and I made sure that all - or at least most - missiles hit the base. What I didn't realize was that I needed to say "winchester" to AWACS. That's what started the dialogue for me to land at the nearby airstrip. So it's possible on my previous attempts if I had just said "winchester" I could have got the remaining dialogue and succeeded.

Is there a setting I'm missing somewhere or are torque effects not modeled? I shouldn't be able to pull into a steady hover with no pedal inputs.

When starting mission in air, I try to lock target with helmet mode without IRST and here no sound and proper indication on monocle, but on HUD I see what R73 is locked on and I can fire. I guess this is a bug, because before update indication was fine. And here few more bugs: 1. I cant fire R73 (rockets seeker has lock) until I got IRST lock, after that I can fire it. Fire without IRST lock 2. When I spawned in air, R73 starts cooling process what takes 1 min. Weapon not ready and I cant fire, after 1 min I can. One more thing about boresighting R73 with helmet. In FC3 Mig29A I get "ПР" signal If I lock target within ±45° off-boresight sector, but I can override this by pressing allow launch button and fire missile on ±60° angle. In FF Mig I can only lock and fire R73 in ±45° sector. Auto\manual switch dont allow me to lock 45°+ R73andHELM.trk

Okay I think I have found a workaround: 1 - Choose a STPT that is far away from you and make sure the range is showing 'B'. 2 - Set your AG radar off by choosing OVRD. 3 - Set your desired STPT and perform the attack. If you skip step 1 and you OVRD your AG radar while in 'F' units, your range will get stuck to a constant value and will never change no matter which STPT you cycle to. I think this is a bug now.

Teaser WIP screenshots of winter textures...

You have va switch to release a pair or all of them

The only thing I notice it’s turning behavior. According to charts it should hit sustained 9 G right at 900 kmh, and maintain max G until supersonic speed. Right now it stops maintaining 9 G will before supersonic speed

Wait WHAT? Why? What's going on over there? What images services are not blocked?

If you watch my latest video, I let out the symbology differences much clearer

I'm getting this same issue on Syria at present. Any target with a building as backdrop is effectively invisible to Petrovitch. nullIt's admittedly crude but I include an image of the target area of a (botched) attack run here, from the rough direction of the attack run. Targets on the road or in more open spaces (green)were easily acquired and engaged by Petro. Ones which had buildings behind them, even if not particularly close (in red, that BMP-1 on the right strikes me as a particularly bad example) were not targetable, even at very close range. Somewhat disappointingly, I tried to reproduce this to generate a short .trk - but was unable to. I've had this happen twice over the course of this week in multiplayer, but it works fine in singleplayer, apparently. I don't know if any of that is helpful, but I really hope so, it's been a bit of a drag.

Are you aware how to adjust the range for TD degree elevation? If you go to radar elevation chapter of my latest video there are some Tips for it

Could we please get some confirmation? In the current public build there is obvious huge barometric altitude input, and no evidence of using the laser when bombing. Is this intended (and can more information be given on how to deal with it), or a bug?

hello. not definite though likely to be a DNS issue. can you share two bits of info? one is the output of IPCONFIG/all from command prompt. another is the output of NSLOOKUP www.digitalcombatsimulator.com also from command prompt.

Commands are doubled because Keyboard/default.lua and Joystick/default.lua doesn't match