okopanja

@uboats likely this is a low hanging fruit...

yes, sorry for not replying. The TWS lock was lost due to target changing direction, so first missile went to the moon. Second one did hit.

Patience the devs did showcase FM today:

The only difference in MAN mode is that once you get the tone, you need to uncage the missile yourself. Also be aware that you can select front/rear aspect.

Perhaps, the bottleneck might be the way the textures are loaded from main RAM into the card itself. BTW upgrading to 64GB is not waste of money. It will make your machine work way less with the disk, since OS will cache lot's of files. In addition it will reduce the wear out of the disk itself (e.g. lower temperature).

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.