okopanja

Affects only visual representation or actually maneuverability?

It would be nice if we could get the original FC3 Icon back together with wallpaper and music cover. Would this be possible?

Yes, I got too used to that, and kind of the icons are low effort for red modules. Still was interesting to see different screen backgrounds.

If you linked Steam to ED account, you can go tou your ED profile and click on Get Licenses. Click on Transfer button and the aircraft will be individually transferred. Side effect: FC3 turned into individual aircrafts

Other factors that should be accounted: - variable RCS - S/N (especially in low level flight). Would be interesting if any of the modules models this depending on the actual terrain (hills, mountains, buildings, tree etc). - all that traffic that happens on the ground that generates reflections with doppler shift. E.g. cars, trucks, buses. Naturally you do not have that effect in desert. Pretty sure DCS does not model this. with western RWR, expecially if you export it it is easier to achieve this. The larger your make RWR the easier will be for human to spot the angle difference to 90 degrees. Flankers/Fulcrums can bring it close, but they are mostly guessing.

clearly lower speed is beneficial, since it leads you to a wider angle that can fit the notch. also note that this is just assumption that attack goes nose on. what should be asctually taken as angle at which his radar beam crosses the target heading.

You do not need to be perfect radial speed would be: Vr = V * cos(theta), where theta is the angle between 2 headings. Therefore it does not have to be perfect, especially if you lower your speed.

null Both sides were elevated by bringing sand and other material. Essentially prior to the war they both raced to get a higher position, with Israel at the end building fortified concrete which at the end mend that their side was 2m lower than Egyptian side. The was also a notable usage of water cannons by Egypt to undermine the eastern side of the channel, and collapse it. I do not have the Suez map, so I can not really check if they modeled this into the map.

just attach your original tacview, since server deleted it already. You can find file name in your own video.

You jump to conclusions, while the TELAR can be standalone it can be easily 10km away from search radar and still receive updates. This way BUK can cover larger volume.

go to the action table in DCS. Open any action, hit the button on STECS, then click on combo box and you should see along normal button presses additional button OFF events. I used this once for one of the detents for engine to IDEL that I could not get to work any other way.

One thing you can try, is to experiment with OFF event in DCS itself. Aside from the regular push event, there is also an OFF event. Still I agree with you: this is more of the workaround.

1. Can you export your VKB config for STECS please? I assume you are trying to use white up/down lever in left-most-bottom-most position. What is interesting is that that level maps to different physical position on my STECS. ( ) E.g. I got: physical 63/64 (UP/DOWN) mapped to 58/57. The middle position I got as an output of AND logical function mapped to virtual 98. In my case the 57, 58 and virtual 98 are holding the signal all the time. In addition, whenever I move the lever to different position, the stick sends the Pressed signal for new state and Released signal for old state. One thing that you may try is to convert the UP/DOWN from Button into Pulse Generator. This way when you flip the switch to UP/DOWN, it will generate a pulse(s). There are different types of pulses, but e.g. you can use GT generator to specify the length of the pulse. See second picture I added here GT generator with 10x10ms x 10 (results in 1000ms). This way the UP/DOWN will generate 1 second hold, followed by transition to low. nullnullNote that 98 will keep behaving like as permanent HOLD since in my case it does take physical input.

Both KUB and BUK can move rapidly. From the early on they were designed to move along the troops and deploy at shortest time. Some more time would be need for cables if you use them (at least for KUB it's recommened). @ustio an alternative is to have Combined Arms, in which case you should be able to command the vehicles to move.

Does it have crew?

Now look at that funny thing...

LOL, but it had the favorite redfor controlling fins: grid fins! Everyone "love" those on R-77.

All radars are directional radars, however, some may rotates and thus provide 360 coverage where the main beam scans the area. This means that majority of energy is direction into a single directions, but aside from the main beam there are side lobs and back lobe which for some of the radars may be strong enough to guide a missile on. If your missile can pick up only the main lobe then it's update interval is pretty high and this may lead to imprecision. Aside from this, some of the radars rely on the reflections from the ground. This can also create a "field" effect where you do not have precise information on where exactly the radar is located. nullSee the attached image. Note these diagrams are expressed in dB, so do not assume the linear proportion between e.g. main/back lobe. Turning off radar is effective measure both IRL and in DCS. You can counter this by firing the missiles that rely on different means of guidance.

I believe that Р-27П was part of official loadout specified in of the updated manual. So it's not a ghost.

Producers of SAMs specify the standard norms for reload and deploy/movement for properly trained crew. However IRL the crew themselves may find shortcuts and cut this time. Plus they may do the things outside of normal standards.

I meant the code used to transmit corrections for R-27

Is the modular system granular enough for the implementation of Barker-7?

I read many of those blogs and they all container highly speculative generic information. Nothing to actually draw firm conclusions on. My understanding is that these missiles are pretty much in legacy state in Russia. In UKR they simply did not have a better idea/resources and simply tried to replace the seekers in the meanwhile. Regarding to R-27ER: I hear the same claims repeatedly about it being nerfed and so on. I must say I do not agree to this, at least not fully. Sometime during last week I fired R-27ER in HOJ mode on F-15C at about 12km altitude ( I was around 11km, Mach 1.5-1.8), and it hit him nicely from 109km distance (close to 60 seconds, he reduced his altitude to 8000m in the meanwhile and started to turn). Also in the past I haved fired R-27ER at jamming F-15C at high alt from 150km distance (tacview). The missile did not reach him, but my estimate was that if I waited longer and fired from 110-130km, the missile would have hit him at Mach 3-3.5 speed. Therefore the limitation of the R-27ER in DCS does not come from the kinetic performance but rather from the fact that after 60seconds power supply is turned off and missile stopped This dude did not maneuver much, pretty much thought he was safe to accelerate straight to spam amraams at the people who were taking off. The moment the target starts to maneuver the energy losses will occur, and this is also something that limits the range. If we are talking about true reasons why R-27ER is of limited use , main reason is the launch warning in DCS which assumes that missile guidance signal is detectable, this is what leads to target going instantly into notch position and loss of lock. For the FF Mig-29 the ED will have to rework the missile itself, so hopefully for good or bad these concerns will be clarified.

While this statement is interesting, I do not believe that statement about versions with 1 is accurate: http://roe.ru/esp/catalog/las-fuerzas-aeroespaciales/misiles-de-aviones/r-27er1/ The linked page is in russian tld domain, hence these appear to be a russian updated versions. At minimum I would expect them to use more modern components even if basic operation would remain the same.

Maybe this helps, but sadly no trk/tacview from me. About 2-3 months ago, there was a player flying the hornet. He would take of steeply with high AoA, G, climb, launch the missile and than land to refuel/rearm. Meanwhile his missile flew in: his client, server, all other clients. The missile in his universe finally arrived and hit me (he targeted spawning slot). The later examination of the server tacview showed that Tunguska's did destroy in server universe all missiles. This was true for the I recorded as well TRK as well. So in his own universe the missile kept flying and hit me. I do think that this desync can be triggered intentionally, and it seems that hornet client is especially prone to this (aggressive paddle use?). Sadly I can not contribute with TRK/tacview since I deleted it, and still it's his TRK that would probably matter in this case. About the TRKs: I observed that they do not recording 100% accurately what was happening. E.g. try driving through the grass while taxing and most likely you will never be able to get the accurate reproduction of original flight. I am pretty sure that within simulation you have some randomness in some parameters that do not get recorded within the TRK files.