Rex854Warrior

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.

The latest hot fix messed up my controls again and my older profiles don't work anymore... Hopefully this doesn't go into release tomorrow.

Hello, I've attached three tracks where in each an M48 Chapparal fires on a different aircraft (AV/8, Mirage 2000 and F/A-18 ) flying straight toward the SAM 5000ft above. The missile burns for a good amount of time and has alot of energy but the AI fires it at a rather close range (about 2 miles) and is still burning at that point which means it has troubles maneuvering. But what is even weirder is the way the MIM-72G approaches a target, it flies straight at the angle the SAM launched it until the last second when it pops up to intercept the target. With proximity fuzes still not really working, it misses every time. The seeker performance is what limits the range I think. The range at which the M48 fires on a Mirage is considerably smaller (around 1 mile), which at this point makes is almost impossible for it to hit anything. Regards, Rex. P.S. : Another missile I've done some testing with is the 9M333, while it doesn't behave in the this way, the missile has less range and has slightly worse perfomance overall then a FIM-92C, it really seems odd considering the stinger was made to be used for MANPADS, the seeker is probably better but more energy ? MIM-72GM2000.trk MIM-72GF18Test.trk MIM-72GAV8.trk

It is probably related to multiplayer, did a bit of testing in solo and the missiles hit just fine with STD parameters. Quick question, does the RB-15F pop-up on the target like the harpoon ?

Here is a track BxWPtest.trk

Thank you very much, this worked and already looks better. There is really one last thing that I need to tweak and it's the LOD for lights, tried to mess around with the terrainoptions file but it doesn't seems to do what I want.

I have tried it and while it indeed increases the range at which the buildings are rendered, the same is not true for lights. Light poles, house lights dissapear first and even the sort of light halo around cities dissapears at some point too.

It's been quite a while, nothing much has changed, will we see an improvement of lighting ? Particularly the distance at which light sources can be seen.

This is the case with both land rovers and the rapier SAM.

It seems this feature is still very inconsistent, some servers hit the ping limit, some don't even if the ping is higher then the ones that do.

Still an issue.

That would be awesome !

Unfortunetly, I don't know what happened at ED, this week's updates for the hornet have not been implemented, the radar still sticks and the TDC goes back to the top left corner of whatever screen the radar is displayed on after unlocking a target.

Here is a short video where I try to explain how this happens (on BF PG server) : This bug used to happen with missiles and aircraft names too not sure if it's still the case. In short if an airfield is neutral or ennemy, the icon and name are supposed to not be visible, but there seems to be a problem where it will reappear briefly for everyone. When it dissapears, the airfields that you were looking at and that had their icons hidden will have their names stuck on the same position of your monitor until the bug occurs again. They will then go back to their correct position and get stuck after the icons dissapear again and the cycle goes on.

Doesn't seem to work for me.