All Activity

Not sure if this belongs here or on the Cold War Germany forums... As the title already describes, I'm finding that ground units are tracking and firing at the enemy through dense forest. This is the case for tanks firing shells, but also for SAMs tracking and then firing missiles through dense forest. The attached track first shows an engagement between two tanks. Then a SAM tracking and firing through the trees. groundai_forests.trk

Yes it is. 4 regiments of S-300s is nothing for a country with a size of 2+ Texas states. And I wouldn't even mention outdated and half inoperable aircraft So, my point stands

I've got the same and some other error page null

No, it is not! "Peasants" don't have S-300 SAMs and Integrated Air Defences and Mig-29s and etc, etc... for F***ing Christ Sake! No, it is not! It's preferable not to have a F-35 at all than have a Block 1 or Block 2B or Block 3i.

Команда в радиоменю с прошлого года не работает, салютуйте хоткеем.

Зачем вам видеть цель на ИЛС? )) Это же не тундра, ага?) После захвата вам показывает кружок, который вас ориентирует, куда лететь для перехвата цели. Техника на гранях фантастихи я считаю.

Drop your DCS log file here after replicating and we'll see if anything obvious jumps out. Doesn't even get to the main in-game menu I'm assuming? I've seen the hour glass once before (this is the one at the bottom right of the headset, like from the headset itself and not a Windows thing?) but wasn't anything permanent like you mentioned.

As I am struggling with configuring TelemFFB for the Rhino, would somebody or Heatblur be kind to point out for me where we can find a comprehensive list of all the FFB effects implemented by HB for the F14? I am not referring here to the effect controlled by external software such as TelemFFB, only to the effect triggered directly by DCS, such as the offset position of the stick. I am specially interested in the implementation HB made of stiffening the controls with increase of Gs or speed. Many thanks in advance, y.

Basically yes, but COOP doesn’t matter. You don’t need IRST to launch R-27T, it is just an IR fox 2 treated just like R-73 and R-60. You could tear the IRST from the jet and it wouldn’t stop you from getting LA with R-27T in radar mode becuase LA with R-27T. It’s just like any other fox 2, the radar cues the seeker head, when the missile can lock you get LA signal and can fire. No IRST involved. All COOP is doing in radar mode is picking up lost radar lock if it can. It doesn’t do anything for missiles except tell them where to point their seeker if the radar hasn’t already. Becuase you mentioned “shoot R-27T as soon as IRST has acquired” is why I said “the trick is knowing when IRST is locked,” becuase one COOP trick is to get radar lock, switch SUV knob to IRST mode when you are pretty sure IRST has lock. And lock will transfer from radar to IRST so you don’t warn the enemy RWR. If you change modes before IRST locks, the lock drops. You have multiple ways to aim a Fox 2, radar, IRST, Helmet, and Phi0. If you lock with Radar, you will get LA when R-27T locks on and in range. If you lock with IRST and no range, and R-27T locks, you will get flashing LA to tell you that you R-27T is locked but doesn’t know if it’s in range. If IRST locks with range from laser or radar, and you get solid LA, R-27T is in range and locked on. Same for helmet, if LA flashes the fox 2 is locked but doesn’t know if in range. Solid LA means missile is locked and in range. All fox 2s work like this.

Good luck. There are multiple factors which may contribute to visual problems which may require a lot more details, anyway.

Коллеги, если хотите принять участие в новом проекте на карте Афгана, прошу Вас ознакомится с этой темой на форуме =ТУК-ТУК=

Предлагаю (настаиваю) создать миссию по мотивам афганской войны 1979–1989 годов. Она будет посвящена вертолётной эскадрилье и пройдёт на карте Афганистана. Реализацией займусь я, а от вас жду идей и желаемых заданий для вертолётной группы. Опишите, что вы хотите увидеть в миссии. Сейчас на этой карте почти два года ничего путного по миссиям нет, и я хочу в месте с вами это исправить. Моя цель — не заработать деньги на этом проекте. Я просто могу это сделать и хочу реализовать задуманное вместе, раскрыть потенциал карты. Опишите, каким вы видите идеальный вылет в Афганистане. Я знаю Ваши пожелания помогут создать живые, разнообразные и увлекательные задачи. ПОДСКАЗКА,что предложить: - Типы заданий (транспортные, штурмовые, разведка, поисково-спасательные, ...) - Расположение и тип противника (пехота, техника, ДШК, засады, ...) - Точки интереса (кишлаки, перевалы, караванные тропы, ...) - Особые условия (ограничения по топливу, ограничения по высотам, ...) - Опишите, что вы видите по ходу выполнения задачи. Алгоритм миссии: Это отнюдь не один боевой или транспортный вылет, это компания внутри с выбором заданий самолично: - Будет возможность сохранения прогресса, при помощи главного меню в игре, - Выбор задач будет в меню F10 Другое... В большинстве игр с редактором миссий уже есть подобные совместные и готовые проекты. Так что же останавливает НАС ? что то подобное мной реализовано тутмана, но от идеала еще очень далеко, и для этого нужна ваша помощь ! ЭСКАДРИЛЬЯ, НА ВЗЛЁТ! КОД — ЕСТЬ, КАРТА — ЕСТЬ. ЖДЁМ ТВОЮ ИДЕЮ ДЛЯ УДАРА!

Just what I was about to suggest. If in doubt - go back to basics. Even to the point of going back to one monitor - get it working then add in the other incrementally. May be obvious but helps understand what is going on in the weird world of windows. I run my screens left to right - 2 screens main display, screen 3 helios and screen 4 MFD outputs - adding them in incrementally when first setting up. If i attempted it in one hit it would be a steep learning curve. Out of curiosity you haven't got any 3rd party software in use have you - sometimes people use it as a norm but don't think it affects things - DCS can be an unforgiving beast. (Spent a while with someone who was having issues - who after a few weeks declared when I disabled such and such it all worked). This worries me: What is the 'mirroring' bit about 'Use a displayport dummy and mirror middle screen onto the dummy' - is that causing the issue? Can you not display direct to the screen?

The tests I have seen mentioned that the sweetspot and edge to edge clarity was smaller on the 57ppd Crystal Super than on the 50ppd Crystal Super. I have the 50ppd Crystal Super and also still have my Crystal OG. Both the field of view, sweetspot and edge to edge clarity is better on my Super than on my Crystal OG. So - your observations seem to fit with what I have read and seen in reviews about the 57ppd. Personally, the 57ppd does not make much sense to me. Much smaller field of view, smaller sweet spot, the 57ppd is only in the center and so on... When you get to 50ppd, like on the first Crystal Super (that I have), I thin that any ppd value above that gives diminishing returns, and not worth sacrificing the nice field of view and edge to edge clarity of the Super 50ppd. The OG is still a nice headset. (The only thing I hold against the OG Crystal is the battery). But my Super 50ppd is a real step up in all areas. As for the night missions - I haven't spend much time in that. But the Crystal Super (at least the 50ppd - but I think the 57ppd has the same panels) can show nice dark areas. So, it's a DCS problem I think. I have played other games, like Skyrim VR modded with a light mod that makes the nights and caves truly dark -unless there's a light source, and it's dark... and when there are torches and lights in the caves and such, those lights fit in real good I think. In DCS you have to lower the gamma, and in Pimax Play you have to find the place where you adjust the brightness for right and left eye separately, and turn that down to -1 or -2 - for both eyes of course. The overall brightness slider I haven't really done so much with, if I remember correctly. Don't trust the auto IPD. On my Super I get the best results when setting the IPD about a 1 or 2 above what the headset thinks. But that would be different from person to person I think. Hope you can return your headset without any problems.

Warehouse > Tank 1 - rails are rendered depending on the view angle, while the other side is not visible, but after rotation these parts are visible, while the other not Structures > Chemical Tank A - rails are desynched with ladder about 90 degrees of object rotation Structures > Fuel tank - the dirt under the tank is semi-transparent for self model tanks.trk

@AeriaGloria Does the launch authorization in COOP mode appear regardless of an IRST lock, and is it solely based on whether the R-27T is in range, not based of if IRST has lock? If that's the case, it would explain why I thought the enemy had just manuvered my missiles, while in reality I was stupidly firing them without a lock xD Edit: I just checked first I locked on with the radar in COOP mode, fired as soon as the LA appeared, and the missile hit, so I don't really understand what's is the trick knowing when IRST has acquired . And It was at around 20km locking from back so it is sooner than I managed to acquire lock manually - around 15km

Which is exactly the type of opponent I wrote about I believe ED removed those capabilities for a reason which made some people start to whine. So, isn't it better to get at least a limited F-35 then none at all?

Not a big problem. but the manual states you can use both point and area track in order to do a TGP FIX. I've attached a LOONG mission in order to replicate the problem, and as you can see, I can only make a new delta with point track. F-16_flight_path_drift_tgp_area_track.trk Aand ignore the name of the file. "flight_path_drift" has nothing to do with this, it was probably the last name I used when I saved a track file.

Just found this report, but for Sinai map:

Will give it another go and maybe with a different helo/map to see if there any differences first - but very interesting few seconds!

I’m trying to reconstruct majority of motors involved in Shrike missiles and currently three of four are clear, early Mod-s of Mk39, Mk39 Mod.7 and Mk53 Mod-s. Clear and fully understood, all belonging to AGM-45A. Mk78 of AGM-45B is still in progress, quite of puzzles are collected and close to be puzzled together. Interesting motor this could be, one of several coming from US kitchen in form which can come only from this kitchen, although not exactly unique because few motors share similar concept. Of course, only if my thesis is correct. I’m looking for, if it exists, any reliable data source saying something about burn time of this dual thrust motor in AGM-45B. This will help in puzzling, in placement of boost and sustain propellant layers (of grains) one to other respectively. Momentarily I’m more on layers, concept similar to grain in Hawk’s rocket motor, at least and after all, same or very similar propellant grades these two motors share

Is the wake turbulence option turned on? If yes, have you already tried it with this option disabled?

It's like... a little plug you plug into the graphics card and it pretends to be a monitor. It's a fake monitor. I did see that you set the main monitor as the left one in the file. that didn't fix anything though. I have deleted those files in the local appdata folder in an earlier step as well There's some weird going on. No idea what it is but I am definitely not gonna touch it anymore after it is working somehow xD

Ganz genau. Ah, Mist, da sagst du was! Ja, das Problem ist dass deine Eingabegeräte neue USB-IDs bekommen (das kann sogar passieren, wenn man Windows auf der selben Hardware aktualisiert). DCS verwendet diese USB-IDs, um die Geräte zu erkennen. Da wird es tatsächlich ein bisschen frickelig. Mehrere Wege können zum Ziel führen. Für mich am einfachsten ist dieser (deshalb habe ich das auch aufgeschrieben, weil ich den Mist alle paar Jahre selber brauche )