Steph21

Magic seeker can be still active with canon selected. We can see the MAV vertical scearch icon on the HUD near CAN. You get the DOM indication on the HUD when you are within range for a magic shot with AA canon selected. You have a magic lock and radar lock on your screen, as you get the triangle over your target. Of course you cant fire Magic as Canon is selected. In your case, you just need to select magic on CNM command and shoot. Easy way to switch from canon to magic shot quickly as magic seeker is already locked on target. Nothing wrong here IIRC

Thx for the update decoy.

Just tested it on a new single mission created in the editor, just a mirage on the map, no script and i had the issue on my first try. Then it worked ok the next 3 tries... Very strange issue.

Thanks for you further tests. Make sense that it's related. Issue is that it's a random bug indeed, but still happen regularly as you state. Will try with one bomb on the related station (i guess it's station 7 showing --- as VTB offers a view from above IIRC)

Indeed you won't see a cross anymore when designating a target in CCRP as it's a Mirage 2000D feature, so has been removed from 2000C. Cross only appear in 2000C to show a Waypoint when you're within 10NM of the waypoint. Doesn't mean you can't designate a target anymore, as when pressing AG designate you will still get the wings on each side of the diamond and get the solution cue on the HUD for CCRP release. Magic Weapon is selected with CNM magic on the throttle, click on MAG on PCA will only activated magic seeker as IRST (will display MAV on PCA when selected), but won't select Magic Weapon. User guide has been updated to cover that MAV search new functionality Most of your issues seem to be related to not being up to date with latest updates. i won't blame you as information is quite spread.

Doesn't seem to have made the cut, as i still have issue locking with PPI when target is not in the center on the VTB. Just a made a quick test though. Do you still have the issue too guys in latest OB?

Haven't you mix 530D with AG weapon (other than canon) ?

Yes that's a bit strange as Zeus mentionned in last update that Rho should be in km and indeed it was the case in last Beta version. From the changelog, you could think it has been reverted back to Nm for Rho values. Still downloading the update, so i haven't checked yet. EDIT: Just tested it, indeed Rho-Theta values are now back to Nm/Degrees, which makes sense IMO (i was a bit surprise with the Km/Degrees). Issue on Offset Altitude entry windows in feet is still there (https://forums.eagle.ru/showpost.php?p=4266905&postcount=15). Seems to be only a display issue, but quite disturbing.

Master Arm changing PCA mode when ground weapon selected: When selecting a ground weapon or AG Canon on PCA, selecting Attack mode with WSC Fwd and then clicking WSC Aft, it set PCA back into NAV mode. But then when setting Master Arm to ON, PCA mode is set to Attack Mode. Master Arm shouldn't impact PCA mode. Track attached Master Arm affecting PCA mode.trk

Yes, that's the issue we get randomly. This Tuesday, i had no issue dropping my 4 GBU-12, but i had the issue dropping GBU-12 from stations 3 and/or 7 several times. We'll wait for Razbam feedback.

ED is working on it, from latest Viper mini-update: Tuning NWS authority

Great news ! Noticed yesterday that Master Arm switch impacts PCA mode when weapon is selected on PCA. It shouldn't. Will post a track tonight.

We have the issue regularly in our squadron, but quite randomly. It only happens with 4xGBU-12 load out, not with 2x GBU-12. That's why i guess you don't have it with GBU-16 as you can't load 4 of them. We mainly have it in Multiplayer. I have the issue with the first GBU-12 released, sometime with the 2nd, but never with the 3rd and 4th GBU-12 that are mounted on dual rack on center station. When loading 4xGBU-12 you can see on VTB, with PRES function on PPA, that only 3xGBU-12 are displayed as EL1, whereas you get a '---' for the fourth one. Initially, IRL, only the 2xGBU-12 loadout was valid. The 4xGBU-12 loadout has been validated only in 2015. Not sure how Razbam approached it. There is clearly an issue with the 4xGBU-12 load out, but hard to reproduce on a constant basis, at least on my part.

Rho has to be entered in km now indeed in the open beta. No change for theta Enter delta altitude of offset point in meters (right window in PCN). INS bombing works fine with metrics value for offset point.

PREP 00 is your current location, hence the continous update on lat/long coordinates on the PCN. PREP is set to 00 at start up. Other waypoints will have fixed coordinates which is what you want as you want to fly toward a fixed waypoint. So if you want to see your current location, you have to make sure 00 is selected as PREP.

Thanks zeus, if we lock a new target, will the ghost contact of previous target remain on VTB (if no RAZ is done)? Can we have several ghost contacts displayed on VTB?

It has the same engine than all Mirage 2000 family : M53-P2

If you only see a red triangle, and no blank square on the same spot, then it's only a surveillance/fighter track displayed from Datalink. Your radar is not seeing it, so you can't lock it. Work your radar to find it (play with radar elevation, azimuth scan, bar scan)

I'm using metrics only now for offset, meters in delta alt (right window) and km for rho, and it works fine. Might be only a display issue indeed in delta alt left window

We don't get decimal value for Offset heading with ruler on F10 map, so you can't be precise with Unguided Bomb in CCRP INS Bombing. Use CCIP INS bombing if you want to be precise with dumb bombs. LGB is the way to go for CCRP INS bombing if you want precision.

Seems that Rho value has to be entered in km now, so not a bug. Check here: https://forums.eagle.ru/showthread.php?p=4268309#post4268309 Create BAD with Delta Alt in meters (right window) and Rho in km and you should be fine (change units for ruler in DCS option to get value in metrics).

Indeed. Can we change distance units on the fly on F10 map for the ruler, like we can for coordinates ? Couldn't find a shortcut for it...

Well ok, indeed that's a quite important change ! So on HSI, when flying toward IP, distance will be in Nm, and then when overflying IP, distance to BAD will be in km ? Wonder what they were thinking at Dassault.... Wonder also how TR value will handle that in PCN TR/VS display... There's still a bug in BAD Delta ALT entry in feet though

Already reported in dedicated bug section with track file. Would help a lot if you report bug in dedicated section with track file instead of opening thread in general forum without any info that could help dev to reproduce it :thumbup: Try entering value in meters in the BAD Delta Alt feet windows (left window), it will transform it in feet value when you'll press INS on PCN (bug) Also enter value in km in the BAD Rho window instead of value in nautical mile (bug). You should then get your BAD at the correct location, hence a valid calculated release point.

Issue is with CNM Neutral that is bugged right now. Not specific to Magic. See https://forums.eagle.ru/showthread.php?t=263258 Basically, when going back to Neutral, it doesn't reset mode correctly (try from Navigation mode for example, PCA top line will not get back to standard Nav mode when CMN switch back to Neutral from CAN/MAG). I'll try to provide a track with all differents scenari in bug section. That's probably why you can still shoot magics from CMN neutral Magics are not selected from the PCA, only from CNM Magic. MAG/MAV on PCA just activates them or displays they are activated, you can then use MAV search with other weapons selected on PCA or even in Nav mode with no weapons selected.