Rex854Warrior

Further testing showed that the Eclair pod doesn't add or consume more flares, the maximum without the eclair pod is 112 chaffs and 42 flares, and maximum with the eclair pod is 130 chaffs and 58 flares, so for DCS that's 18 chaffs and 16 flares missing meaning that do get the count right the double counting should stop at 94 (112-18 ) chaffs and 26 (42-16) flares and sure enought it did.

Here is a track, It is weird because with the eclair pod equiped, the number of CM used is doubled until a specific number of flare/chaff is reached, it will then use only one chaff for one dispensed when this number of chaffs is left, same goes for flares. DispenserTest.trk

More complex variants of RSIU-4V can do the following comms: a) simplex comms in one channel and guard comms in the second channel b) duplex comms c) simultaneous simplex comms in two separate channels d) simplex comms in one channel and guard comms in second and third channels Provided by ZHeN EDIT : He also told me that just below this paragraph there should be a description of the most common modes used in the main variant of the RSIU-4V radio.

Hello, While the hydraulic pumps (1, 2 and Aux), the Hydraulics alternators (1, 2), the engine alternators (1, 2), Aux Transformer, Oil system, battery and INS might be present somwhere in the airframe, when using the mission editor to make those items fail, nothing happens and this seems to also be the case if you get hit. The only equipement that can fail, and that does frequently when taking a hit, are the RWR sensors. The mission report confirms that those items have failed. Track Attached. Regards, Rex. 1. All failures (appart from the RWR sensors) do not have any effect on the aircraft. 2. Attached 3. It happens whether you suffer damage or force the concerned items to fail through the Mission editor. 4. Attached

This is still an issue.

I will try to do some more testing.

Hello, The pilot model for the Mig-29 is not available. Regards, Rex.

So will the logic of the SNP-2 mode be corrected in order for R-77 to not give a warning before the missile goes active ?

Should be yes.

TWS multi target mode I think, СНП-2 on the HUD if you've kept it in Russian.

Intresting, what is the INS used for then ?

The track was broken after today's update, probably because the FM changed slightly. I never lock the target nor fire at it, I hit the ground instead.

The target was an Su-25T hot on me at 50kms, slightly lower, using AVT mode for the PRF.

This looks like more of a seeker/missile problem then AI, trying to fire it manually did not help. Wasn't fixed in the last update.

Alright, I'll have to get used to it :) Thank you.

Hello, The R-77 is supposed to have inertial navigation and so it should be possible, just like with the AIM-120, to fire the missile in TWS mode and guide it via radio command for the initial stage, the missile then goes active when it is close enough to the target. Currently the Mig-29's TWS mode automaticaly hard locks the target when it is in range and gives off a launch warning to the opposing aircraft, even if the missile still hasn't gone active yet. (Track attached, first flight). The same should apply for the R-27ER/R, both equiped with inertial navigation, are guided by radio commands (soft lock), then a hard lock is required for the final kilometers since they are Fox-1s. Regards, Rex. P.S. : The multiple target TWS, when it has chosen two target and one of them is in range, switches to hard lock, nothing unusual here, but it does so for both targets, so both of them get a hard lock tone, which seems weird, unless the radar can track AND lock multiple targets at a time. R-77TWS.trk

Hello, It seems the R-77 (and maybe the AIM-120, but we haven't done enough testing with it) is immune to notching. When the missile is being notched and is active, the sensor still manages to keep the lock and intercept succesfully it's target. I confirmed using tacview that I was indeed notching the missile. Track attached : First flight the missile missed but was still tracking even though I was behind the sensor, which was really weird. Second flight the missile detonated near my aircraft. Regards, Rex. server-20181024-154853.trk

This should really be looked at

Hello, I noticed that when using the vertical lock and boresight mode, I had to press the lock button when the target was inside the search cone of each respective mode. It kind of defeats the point of an ACM mode, is it supposed to be like that ? Regards, Rex.

Hello, When trying to hard lock a target (STT and not using TWS) pressing the lock button seems to inconsistently not work. After some tests with another player, he gets the lock warning on his RWR for a very short time after i've pressed the lock button. And that even if on my side nothing happens. Here is a track (there are some other tests but the first flight should be it) : You can see that when I tried to lock him nothing happens, I had to switch to TWS to continue what we were really testing that night. He did say that when I pressed the lock button, he heard the lock tone for about 1 second then nothing. Using TWS to achieve hard lock works though. This happens almost all of the time and with targets on different aspects. I had that bug on Blueflag and on my squadron's server during one of our missions. Regards, Rex. server-20181024-010848.trk

While ED is a small team, not every single one of their programmers is working on the F/A-18 since we are getting updates for the game itself and not even trying to contact ED is surely not going to help. If Polychop has already done so then waiting is the only thing we can do.

Perhaps polychop should get in touch with ED to make the Mistral Missile on par with it's real counterpart.

The missile stays at over 1000knts all the way and while thrust decreases the missile is definitely still burning. Whatever the target is doing, if it's in range (the advertised 7 kms) the missile will hit. This is a bug, a missile that still has 1000knts of energy at the "max" range means it's far from maximum range. EDIT : And in the OG post's video you can clearly see the missile burns for a very short time, like all missiles, max range is a value achieved under very good conditions.

I'll make new profiles then, yesterday when I redid some keybindings it looked like it was a mix of two profiles (mine and the ED's), some keybinds like head movement weren't deleted when loading my profile. I might have had that when starting the game today which is why it was messed up.

I have adjusted my profile since the last update yes, was I supposed to use the imposed keybindings ? Joke appart it's annoying but as long as the next update for the release branch doesn't mess it up, the open beta branch will have served it's purpose well.