Mirage CCIP issues V2 - Now with tracks screenshots and mission

After I did look like an complete Idiot over here: http://forums.eagle.ru/showthread.php?t=171007

I sat down and tried to reproduce the issue and took some screenshots. Would have loved to record it, problem is atm series 10 Cards have a driver issue that causes high DPC blablabla simply not capable due to driver issues atm.

The CCIP pipper for MK82s does show not only wrong but also impossible impact point calculations, IF the players plane takes off from an Airfield, flies an extremely low alt attack profile at really high speed. [Afaik, its irrelevant if its hot from runway or cold from parking.]

If you think "what is the guy is talking about, he for sure simply cant bomb for sh***t!" here are some screenshots.

That is what I would expect, and what I get IF you start in the air. I just changed the unit from takeoff from runway to fly over point in the mission, didnt change any of the other waypoints flying through the valley.

As you can see, positive G load, 52ft radar alt, moving in at 717kt/Mach 1.09 CCIP leads to 0,6km bomb flight path and a reasonable Impact point on the HUD.

Now the buggy CCIP indicator you get on the same flightplan, same attack angle and as similar flight params as I could get them, by just taking off from an Airfield.

As you can see, positive G load, 65ft radar alt, moving in at 717kt/Mach 1.09 CCIP leads to, wait wat ? 0,0km bomb flight path and a impact point over the horizon, over the FPM on the HUD?!?!

CCIP Indicator go home, you are drunk !

Now for analysis: flying over the sea, which shall cancel out any possible doubt about wrong Data by radar alt with 0 wind:

I dont need to read out all the params, but the bomb flight path length and impact point calcs are obviously wrong.

Further analysis over the sea:

At some point around 140ft radar alt the Indicator returns to under the FPM again, although the CCIP indicator in the HUD points for sure further away then 200m and the bombs are obviously going to hit closer then the CCIP indicator.

In the attachements there are the mission I used to investigate the Issue, one Tacview/track with starting in the air, the CCIP indicator working and one Tacview/track taking off from an Airfield, with the CCIP indicator beeing drunk.

Since the CCIP indicator is not broken in general just under pretty narrow but imho important parameters, I tried to supply as much info as possible. :)

kind regards

microvax

EDIT: You can notice in the tracks that I did use active pause and speed manipulation to time the screenshots, the issue also exists with no time manipulation.

will this be fixed ?

also my MK20 don't explode. why ?

A bit off topic:

There may be a bug, but the flight parameters are wrong too.

50ft is too low IMHO, and M1.09 is way too fast...

M0.95 is a maximum with AG stores !

Is also broken within parameters. Speed doesnt play a role, if its in the broken state at that target with the same start point, it stays broken, no matter the speed.

It has something to do with where you start and where the target is, its really weird. Thats why I added the mission.

I hope it gets fixed soon.

And well, bombs on retarded, problem solved, for the altitude, and well, things start shooting you if you go higher. :D

Also got same problem at dive angles so its something in general off with CCIP.

And TAS doesnt halp either.

If mk20 are the rockeyes they need some altitude to open first. If you drop them low, they hit the ground before releasing the submunitions.

Mk20 are place holder for BLG 66 Beluga which has a different flight profile.

In Mirage 2000 CCIP is meant for weapons with low level release, not dive release.

Re: Mk 20. Fusing?

I don't know if these are with or without the radio proximity fuse (CBU-100) or with the 2-option time release but you need time and possibly altitude.

Mk20s burst just fine for me.

so what are the proper conditions for MK20 ?

will this be fixed ?

 

also my MK20 don't explode. why ?

Wait for tweaks and fixes in the future

As for bombs not exploding you have to arm them first on PPA

Mk20 are place holder for BLG 66 Beluga which has a different flight profile.

 

In Mirage 2000 CCIP is meant for weapons with low level release, not dive release.

Well okay, then its obviously broken. Thought maybee my zero degree dive profile was a problem, since everything else drops with a slight dive in CCIP normally.

But okay no dive is fine with me. :D Then it only needs a fix. :)

As for bombs not exploding you have to arm them first on PPA

I did

still no go

What are your release parameters?

I was under the impression that all A/G stuff hadn't really been looked at yet and was thus a WIP. Certainly A/G guns CCIP don't seem to work at all, and rockets are pretty bad also.

The CCIP pipper worked brilliant at a point in time before, so i reported its state as broken. :D

I mean its WIP, still a bug thought. :)