okopanja

I think SD-10A looks better now, especially in terminal guidance it does not loose target so easily anymore. Range is nothing to brag about. Conditions: - Target: F-16, low, size: small - 2xSD-10A + ECM pod - Launch altitude: 12800m - Launch speed: Mach 1.45-1.5 Conditions: - Target: F-18, low, size: small - 2xSD-10A + ECM pod - Launch altitude: 14600m - Launch speed: Mach 1.2-1.26 I gather where there is SD-10A, there must be SD-10B in future?

For non-maneuvering target it looks almost identical.

v1.5.2 Important update to fix the hijacking of hotkeys in Mission Editor. Please update to this version. What's Changed Fixed issue with hotkeys being active when SharkPlanner is hidden in #112 Full Changelog: v1.5.1...v1.5.2

Su-30 has fixed the issue already.

Go here: https://discord.gg/codename-flanker-community-839196573228335185

They did fix it.

No I tried myself and it still hangs at the same place. I think that NVIDIA splash screen.

Any news on this issue? Please confirm it at least.

Still no fix with 2.9.2.49629.

Hint: you may place FARP (static objects -> helipads) and it will bring you the flat surface you need to deploy the launchers & co.

The capability to reacquire is still there and not removed. The actual expirience depends on weather person plays in SP or MP. If later the things become tricky due the network latencies on shooter, server and target side. This often leads to the situation that trajectories of the same missile in the 3 "universes" are not the same, including the speeds, position and movement angles. As for RWRs some of them are too precise. If they had up to 10-12% of variance notching would have been more difficult. On the other side RWRs often give warning in MP too late or not at all, due to desync(they are operating in target universe).

48 km/h 25.9 knots is the Doppler filter speed for AMRAAM seeker?

Just to confirm that I manage to use the Keepass2. You need the secret seed (remove spaces) that you can get on reconfigure screen of your account. Note: this is not officially supported, but it is an alternative if you do not wish to have Microsoft/Google Authenticator on your phone. One hint to ED: if I need to login to both username/password and code in web browser, the page reloads which makes it tricky to login on mobile device.

It should be possible to use keepass2 instead of mobile app. They are essentially TOTP compliant and the only thing needed is secret seed used to derive time based codes.

Updates?

Any update?

Well this concludes the topic. I just hope we do not find they were wrong.

I would say we stop arguing and ask ED and Magnitude 3 to clarify at least in this particular case what is the correct behavior. They both have access to documentation and Magnitude 3 had team member who was actually Mig-21bis pilot.

Last time I checked the warning was going off once TWS2 was replaced with mode guiding 2 missiles on launch (I do not thing they were pitbul). I did not test this recently. lapsus linguae. I corrected it, but kept also original. Regarding the general topic of RWR warnings: in DCS many of these things were implemented on assumptions and initial balancing and subsequent nerf wars had a lot to do with it. In this case I am pointing out this is very likely pulse guided missile (while others believe theory of additional signals or switching to CW), which means there is no difference between STT and after when the missile goes out. Again I will remember that range of both the radar and missile are within visual range. Not really the need to go after fancy stuff. To give launch warning you need some change in the operation of radar: e.g. sudden intensity burst or other detectable change. Bottom line: the RWR should give launch warning only if this is detectable. In DCS this is simply if then line, but in reality you might not be able to detect this.

Which signal? Again talking based on assumptions. This is not AIM-7 and later company.

We have similar exception in form of AIM-120 for which there is no indication of the launch, although it is well know that the signal is there. R-77 also has the signal, but that one gets detected . In both cases until certain point signal is a secret until the other side figures it out. ED is assuming that this signal is known (they may be even right, since the soviet radar program was compromised in 80s). However with pitiful R-3R, there is no evidence that the main radar carrier changes to CW (except for sending pulses) or that it encodes the hidden signal. Simply put for 8km distance you do not need to bother with this. It's actually within visual range and you will simply see the smoke. In theory as @GGTharoshas suggested we can talk about pulse vs CW, in which case CW would offer somewhat better flare chaff resistance and better clutter resistance. This could be even supported by the fact that first soviet SARH on KUB in later variant did support CW to deal with clutter, but this does not appear to be modeled in DCS. RP-22 radar itself is not meant for work in radar clutter, in fact it's directed upwards in order to avoid this. Hence, I do not see the reason why would missile need CW. CW could offer somewhat better flare chaff resistance if the target is notching, but in this case time for reaction is rather limited. It's more likely that e.g. F-5 pilot would maneuver before it enters into firing zone of the mig-21 head on.

I am not the one grasping here at straws, but rather you trying to hint that there is a "signal" for the radar/missile in order to accommodate the assumption that RWR is able to detect something. This is an early SARH, fired from limited platform and expectations of fancy features are probably not based on reality. Again this missile is fired within visual range, if you have a documentation for radar/missile and the corresponding RWR, then it would have made sense to argue about giving RWR warning. On the contrary, the initial claim of this topic is that RWR should give launch warning, so understanding what is detectable if at all is rather important. I would agree with @Pavlin_33that most likely the pilot would assume the missile was fired if they were in STT and certain maximal range from the target, or based on the signal level.

I would like to point out that we are talking about the missile that was developed from short range heat seeker, by replacing guidance with SARH, thus giving it all aspect capability. At such range and weapon weight having the additional signal would kind of pointless and wastful. This is not a soviet AIM-7. The RWR could therefore not distinguish STT from launch. It should be noted that radar lock and launch authorization occur at different ranges. This is due to 2 reasons: kinetic and ability of seeker to receive the signal pass s/n threshold(missile antenna is tiny compared to rp2322). The only possible method to signal the launch with RWR is to pass certain signal threshold, and even then aspect would complicate the things. Realistically speaking the pilot would launch in PPS with r-3r, since in ZPS he would likely use a heat seeker. Therefore for this era the most reliable "RWR" are pilot's eyes trained to spot the smoke.

When it comes to the lights there is a whole class of devices that can be used to provide indications outside of the DCS: other stick/throttle manufacturers devices with controllable lights, e.g.: keyboards, those with groups of LED lights or even LEDs for individual keys, mouses, Alienware devices (e.g. monitors, keyboards, cases), different LED based external solutions Great effort, although I do not have the Thrustmaster devices it is amazing that they do care. I recently asked VKB to provide command line utility to switch the profiles for their device, however I got the negative answer since it is too much effort from them to code this. Although I am extremely satisfied with Gladiator EVO, I am seriously considering to obtain Warthog throttle instead of certain new throttle option, mostly due to non-existent interface other than what is provided with standard DirectX devices.