foxwxl

There is some problem trying to slew the TGP when your aircraft is not level, because of the transform of the input coordinates. It will be fixed at a later point, right now, better to slew the TGP when you have your A/C leveled.

Viewports = { Center = { x = 1921; y = 0; If the x and y for center viewport is not 0/0(ie, second monitor is on the left side of the main screen), the LSO station will black out.

Can confirm this, with 2 monitor lua selected, LSO screens are blacked out.

LSS is modelled for JF17. In the test several weeks ago, we have tested 17->17, 17->18, 18->17 buddy lasering, they all worked as intended.

Not receiving any report on adjust BRM value in this patch.

I've tested on my side, Chaparral did have some problem, rocket impact around the target with a quite high percentage. Will discuss with the team.

Try flying overhead some IFVs, those cannon will mostly damage your plane but not kill your pilot.

Some target may behind obstacle for direct aiming, or SPI could be a obvious land mark for ingress reference.

Most MP servers I flew have enabled the MAGIC IFF mode, which give a FC3 sytle instant IFF no matter what mode you are in. So basically after you turned on the IFF, mode is not important.

PL5 uncage allow the seeker to slave to radar LOS and begin pattern scan, if a heat source is available, the seeker will automatically track on. If caged, the seeker will stay at ADL, but will still auto track on a heat source if it enter the seeker FOV. AIM-9X on F/A-18 will salve to radar LOS by default, and with JHMCS it will auto uncage when the heat source is strong enough. AIM-9X on F-16 still have some cage/uncage bug last time I flew, but since it is quite a while ago, I don't know if it has been fixed now.

Nope, the flight was recorded full time that I'm inside F1 cockpit view to demostrate how the BRM really worked, F6 view is not used. As you can see, I only pull 3-4G at the launch phase, at the terminal phase when the rocket does not have too much energy left, I'll keep the LOS as steady as possible. And I've tried M2 M113 and other type, not making much difference.U can area track the ground in front of the target to see if there is any improvement. And U can upload your ACMI, and we will see what's the problem on your side.

This is really the highly experienced pilot saying.:thumbup:

U are correct, we are trying to correct the wrong value for the ARH, but it did not work. After all, seeker still need the work from ED. At the moment, all ARH seeker has very larger FOV or very fast scan speed(just like AESA, I can not tell which one, or they are all messed up).ARH can capture a 40deg off boresight target the moment it entered seeker range(15km/8nm), even without any DL support(turn off radar directly after launch).And sometime when ARH get chaffed, the missile will jinking between target and chaff for several time(if target get out notch too fast), because it recapture the target too fast. We can do nothing about this.:doh:

OK, I've viewed your ACMI, and plz see the attach 2 picture. I think it should help you better understand what has happened. You are fighting against AI, basically all your missed ARH missiles are notched by AI, and don't doubt it, AI is really good at notching, very precise 90degs beam turn. As you can seen from the pic, these missile complete match those 3 conditions for notch that I mentioned above, so they get notched as intended. Nothing wrong here. ------------- Several other points need to mention: 1. One SD-10 is notched but not heading for chaff, just like bump away from target.This is a side effect introduced very long time ago(back to DCSW 1.5),to protect helos from ARH missile.If the target is beaming and it's speed is below certain value(usually M0.7 below, better at M0.5 below), the ARH will drop the lock and turn away automatically. And this does not need look down and chaff support. 2.For AIM-7 It's chaff resistance is really low at the moment and the speed is also too too low, AIM-7 is completely useless outside 5NM. And your teammate may not firing the AIM-7 at STT for several shots, I see some shots are not guided at all and AI didn't even drop the chaff. Some other AIM-7 are missed because the target entered notch, APG73 can not provide illumination when target is lost.

If U help the missile passing Mach 1, It may reward U with a better terminal speed .:D

Range >30km Pitch angle >8deg

I know the situation you described, but I'll look into the ACMI first for sure .

Uncage the seeker will command the missile SLAVE to radar

The ARH seeker also suffer from notching like the airborne radar in DCS(not in another game which name should not be mentioned). When the following 3 conditions are met, the ARH will lose track(near 100%): 1. Seeker look down situation(missile higher than target). 2. Target near beaming. 3. Chaff is dropped. Chaff is mostly accepted by seeker when target is near beaming, the accept angle is related with missile chaff resistance value defined in LUA.(So chaff SD-10 is more easily than 120, since the chaff acceptance angle is larger)

8NM @ 10Kft is just around the NEZ, the target will fall in great danger if the SD-10 is not being chaffed, but it's still about how well and how quickly the target react. If the target started the run at the time you launch(usually happens in test not in real fight which both you and the target is perpared for the missile shot), it may still escape in a very narrow window. Note that the reaction time in real fight is different than in the test, and 2 secs delay in this kind of situation can have great impact on hit or miss. --------- The overall looking down penalty has been increased some time ago, this impact to all A2A missile, since SD-10 chaff resistance is poorer than AIM-120C(this is one good reason why SD-10 is stated has a rank between 120B and 120C), it will eat chaff more easily than AIM120.

Plz identify the exact time of your problem in acmi, I'll review them when available.

Again, U have to consider what the missile is doing at that time, to give U an reasonable explanation. --------------- Bring up the AOA chart on main axis and Mach chart on side axis, now read it again. Does the missile losing more speed when its pulling AOA? Yep, you got the answer. The target is maneuvering hard(agile F-16 with M1.0+ speed), so you have to combine the altitude exchange with the missile G load/ AOA at the same time.

We will try adjust a profile for SALH scheme, but other values will aslo be changed accordingly so that the range does not get beyond what it should be. I think there will still lots of complain about the range even after the scheme is changed to SALH.:megalol:

Lower Cx0 at high MACH does not refer to lower actual drag force at high MACH. Cx0 is a coefficient not the force, for the drag force U have to consider the speed. (It's the Vsquare that inside the drag equation)

Sorry, your img does not showed up properly on my side , so I didn't noticed. ---------------- And the analysis that you did is wrong. Switch to relative time of SD-10 will give you a better idea of what happened at what time. Select G chart on main axis, Mach chart on side axis, now read that chart again. U will see the G force suddenly drop to 0G @1:20 after missile launch, which is the time of battery dead, and it is supposed to happen since the missile battery time have reduced to 80secs. ---------------- And for the curve that you "want", it's completely wrong again. Low altitude have much high air density than high altitude, this means: lots of drag when coming down, espically at high mach. The missile coming down from loft still decelerating becasue of the drag, but with the exchanging of altitude, the speed bleeding is much lower than none loft shots, but this does not mean diving at that angle can completely overcome the drag from high mach or even accelrate. If you can't under stand this, try it with your plane. Select a F-15, burner on and speed up to MACH 2, now thrust IDEL and dive with 15deg pitch angle, see if you are accelrating or deccelrating or you can just maintaing the speed.