Blackfyre

Balance here is adherence by all modules to the same standards and common sense. You shouldn't give a very "realistic" radar to one aircraft and imagined and gamey capable to other. In DCS they should be both as realistic as possible, or neither. This is the balance I'm talking about. I don't believe that Hornet's radar is way way worse than F-16's, JF-17's, Mig-29's(!) and all others.

Well, it should be. Modules don't exist in vacuum, they influence each other in the World. And making one module artificially stronger or weaker than others breaks that world and makes crafting online missions/servers way harder than it needs to be. Such vital systems as a radar should be simulated equally for every fighter in game. P.S. I can't fly my favorite module (F-18) for two months now because she has a broken radar in one way or another and this simply would kill it for PvP environment altogether, unless all modules would obey the same set of rules.

Через DTC

Есть куча сервисов, которые генерируют морзянку. Менее удобно конечно, зато более гибко.

I have included a track replay. As short as possible. It is easily reproducible.

Так и должно быть. Когда активны Маверики или Хармы обе кнопки на контейнерах не работает. Так как они используются данными типами вооружений для своих целей.

When AWACS, hence a datalink, is present then LAR indication on a radar is utterly wrong(too short) while target speed is too high (indicating 1.2M for an An-30 for example). Target speed at the SA page is correct. Everything is fine without donors contribution. Track is attached. wrong-LAR-and-target-speed.trk

Наводились вроде, но только по подсвету с другого Ка-50. "Коды" и вообще система кодировки лазера вполне могут и не совпадать с НАТОвскими. Я бы сказал скорее всего не совпадают.

CH-47F Chinook politely disagrees. She was barely flyable at the start, and also she has been without a rudder trimmer option for almost a year.

It is possible to look around using head tracking (say TrackIR) while driving a tank. It could be enabled by "TrackIR on external view" option. It works fine in isometric view, but breaks in first person view - sight is moved by the head instead of mouse. head-tracking-breaks-aiming.trk

In order to work, Patriot site's ECS must have line of sight to a target, which, I guess, is wrong. It is the only manned vehicle in a site, why would it require to be exposed? It used to work fine without line of sight, but then it has been changed without a mention in patch notes, so assume it is a bug. P.S. I would imagine it must be somehow connected to radars and launchers, but it isn't the case in DCS, which is fine because it helps to offset AI stupidity (smart AI is very hard). ECS-LoS-Patriot-engages.trk ECS-no-LoS-Patriot-does-not-engage.trk

Да.

Stationary ground unit can be seen by the Apache's radar at a range greater than 6 km if this unit is controlled by a player. Steps to reproduce: 1) First client spawns in the Apache; 2) Second client occupies ground unit 3) This unit appears on the Apache's radar 4) Second client either leaves unit or toggles autopilot 5) Unit disappears from the radar. Track from both clients and server are attached. apache-radar-sees-stationary-controlled-unit-apache-client.trk apache-radar-sees-stationary-controlled-unit-server.trk apache-radar-sees-stationary-controlled-unit-taccom-client-ca.trk

I don't use VR, I don't even have it.

If you use DTC in single player mission then track always does not work with the following error: nullSteps to reproduce: 1) Spawn in DTC-capable aircraft. 2) Open DTC interface. 3) Close it and quit mission. 4) Try to watch track.

Subj. When using DTC screen, every enemy and friendly ground and aerial unit is shown on the map, despite the "Map Only" option is selected. The same happens with other similar options: "A/C Only", "Allies Only". Statics are hidden as they should be. The same happens in multiplayer too. Unit's options "Hidden on MFD" and "Hidden on Planner" don't affect visibility. One could argue that DTC screen is a sort of a planner rather than F10-map. I can't post a track, since there is another bug, but it is very easy to reproduce. Mission attached. Steps to reproduce: 1) Spawn in DTC-capable aircraft. 2) Open DTC. 3) Observe all units you are not supposed to in real time. This is very critical for certain servers and massive events. Right now, we effectively can't play the way we were intended to because of this bug. dtc-godeye.miz

Хм, я такого поведения мыши ни в одном интерфейсе не видел. Меня бы такое точно с толку сбивало.

Клавиша "/" это не радио, а что-то типа вербальной связи, работает, только когда у тебя батарея выключена. Сразу после включения батареи нужно использовать назначенные клавиши для первого и второго радио, они располагаются на РУДе, соответственно в настройках ищи там, куда назначено. По умолчанию что-то вроде Alt+\ и Shift+\.

В сообщение @USSR_Rik DEDICATED... заключен в знаки %, означает, что вам надо искать не конкретно это значение, а какое то свое, по умолчанию, кажется, DCS_server. И там уже создавать autoexec.cfg с webgui_port и возможно другими опциями. Второй сервер будет использовать папку, которую вы зададите параметром -w в ярлыке/командной строке.

Участвовал с Израильской стороны. Дроны сбивал как минимум. В рамках DCS не вижу большей разницы с точки зрения сценариев с теми же F-16 или F-18, F-35 можно будет использовать там же. Плюс абсолютно вымышленные сценарии никто не отменял, все равно приходится всегда натягивать сову на глобус, даже в случае попытки отыгрыша какого-то реального сценария, ибо полного набора техники в нужных модификациях и/или карт всегда не хватает.

Если вы в строю с ведомым, то нет никакой разницы между указания по часам или азимуту, скорее часы предпочтительнее, ибо не дают ложной представления о точности. И я обычно понятия не имею какой там азимут у цели (его надо рассчитывать через как раз часы), если я ее вижу только визуально, почему бот должен знать - не знаю. Если ведомый не в строю, то удобнее ориентир.

С погрешностью в 180 градусов

Имелось ввиду в игре (наверное).

I had to google what your abbreviation means... I mean that 1.5M and 40k feet are preferable parameters for the Hornet before the first engagement. Viper will be 1.7-1.8 45-50k, and Hornet will have an upper hand due to better radar, you can turn away at 70 degrees after launch, Viper only 60, it seems small difference but it is huge.