TobiasA

I did, it was different and now I am wondering if it was coincidence or not. I will try again. It looks like this here. Approach was from right to left. Too long, too short, too short, too short, way too short so the last approach is even further off. Attack height 25k. So even worse with the last approach being closest release, but hits further away.

Did you lase prior to each drop?

It probably is

The precision is higher because the TGP error is smaller. JDAMs seem to fall shorter when you pickle from a larger distance.

I have the same issue- when a JDAM is used from 8nm slant range, the resolution of the system is so bad that it makes JDAMs unsuitable for anything harder than a truck. Even with lasing. The effect is coming from the system, the error is decreasing with slant range getting smaller. Yes, I am laser ranging, yes, i pointed at the bottom of the vehicle, but they still fall long or short most of the time. When dropping them from lower altitude or later in the DLZ they become more precise. It probably is the way it is.

Some things I have learned: Do not exceed 400 feet per minute sink rate in a hover. Just don't. You can have slightly more if your intend to stop with the ground effect. You often don't need full tanks. Most of my flights start with 60% fuel which is enough for more than an hour and gives a lot of agility. If you need to leave a hover fast, tilt to one side, swing the tail around and put the nose down. Recover the dive with forward speed instead of risking VRS. It js also changing your position faster and less predictable than trying to sink with 400fpm to evade an incoming missile or die of VRS. When coming up below a hill, aim for a low climb rate which is easier to stop precisely. Use the hover hold and altitude hold modes. They make life so much easier When descending from a hover, ease off on the collective until you almost have your desired sink rate, then go back to almost the same power setting to "arrest" the sink rate. Avoid sharp adjustments on the collective. Those won't be compensated by SAS. Try to be gentle with the collective and if you have to evade, try to use the cyclic instead. Course changes are more effective than altitude changes with the collective if you go evasive. If you hear "ZSU, 12 o'clock, tracking" and don't touch the cyclic for 5 seconds, you die.

This can't be overstressed. When in a hover, trim and do a small wipeout. I usually do a small circle on the stick and do a small left-right kick on the rudder after trim hat up to make absolutely sure that the release to center is registered. Otherwise, it will swing violently to the side... You should however not do that while your CPG is lasing a missile in hover.

Well... Thanks! So... it isn't me.

Hi, is there any possibility to adjust the radar elevation up/down sensivity? When assigning it to a button, it moves by a pretty large amount. I wanted to map it on a button instead of the warthog's slider axis, but it is far too fast to map it to a button... Thanks!

Optimum mach is about 0.7 to 0.8 in most configurations. You can hang around for hours if you are gentle on the throttle. The Viper is awesome. Started in 1999 with the same sim back in those days and loved it ever since.

Edit: Nevermind, I misread your question on the mobile phone. Why do you want to use CCRP when you have no bombs? Original Post: You can use CCRP on any point, it does not require a TGP. Switch to CCRP and it will drop on your SPI, marked by the square in the HUD. Possible ways to create a SPI without a TGP: Radar cursor when radar is SOI Steerpoint Markpoint, created by HUD box, HMCS, radar lock HTS (this is most probably not precise enough for most weapons other then CBU's) manual entry of a steerpoint Remember that every markpoint and received datalink point is a steerpoint- select it, CZ and there you go. The other option is to DTOS and have basically the same as CCRP by marking your target in the HUD.

There is no workaround for maverick boresighting, you simply can't boresight them as of now. I have not even once succeeded with boresighting them. Wonder how this is supposed to work. Never ever boresight them as of now. They will at least look in the general direction instead of moving to the gimbal limit after three unsuccessful tries. And for the RWR... Just enable search radars. I have some hope for a hotfix next week. I don't care if they revert the whole thing to prior the patch, just bring back mavs and fix the RWR. However, the only way around such things is to go to the stable branch. Open beta means that you are a tester, and as such there will be things that are major flaws to be discovered by you. I can understand how the RWR bug made it through, but how the mav align bug could pass makes me wonder if there is a routine that does actually work. There must be one working way to do it, and I would be interested in what the tester did because... This would be the workaround.

Yeah, same here. F-16_mav_align.trk

They do. Try it. They do the wrong thing, but... They work. Just... Different. The good news is that if my theory is correct that we can in fact fly the F-16 until it is fixed by enabling the search radars. It is still wrong though. That's just coincidence because I killed that Su-30 before. I had airborne emitters being detected. Not super-duper-100% sure that all of them showed up though, but it seemed to be working. But... I gotta go to bed now, can't test anymore. I still don't know why this happens in multiplayer... But probably the number of search radars is an issue. Who knows...

See that picture. The filtering is wrong, it doesn't filter the search radars but it filters something else, almost all of it.

Yes, that's the issue. It is wrong. But the reason is that the filtering is wrong. I can't attach pictures here for some reason... Try enabling the search radars and you see what I mean.

Guys, its the search radars... I enabled the search radars and my RWR shows a lot more indications

Can you check and toggle priority mode once if that is the issue?

I am unsure if anything even exists... Time to make one

Well I am sad that someone did use exploits to a point that made it necessary to include the ALE settings into IC, but... It is what it is. I am hoping for the DTC soon then.

Can we please come back to having custom sequences again? At least unless we have a DTC? Would really appreciate it, I don't want to edit the sequence each time. Thanks in advance for that!

That is exactly the issue, the above trackfiles are both the missing one for this issue as well as a supplemental to the linked threat. Thank you very much for that!

It looks like that issue, however, if I toggle the option with Comm Switch In <.5s, it does not remove the radar blips in my simple test mission. I watched your track, and this is exactly what is happening (guessing from the symptoms). What inputs did you make? Or the issue only appears when a Link16 host is in the mission..? I will try to toggle that input and see what happens. Thanks a lot for that hint!

I will test that, thanks!

It happened in 2.8, just yesterday I think. I will try and see if the track works.