jojo

Probably Timghetta doing both. Great level of details, so probably a lot work, takes time for each one. Totally different flight gears :smilewink:

See here: https://forums.eagle.ru/showpost.php?p=4157239&postcount=22 However, when I have a contact on VTB, it isn't especially more difficult to lock.

AFAIK, we see Scorpion helmet in this video... https://www.thalesdsi.com/our-services/visionix-2/hmcs/

MBDA Scalp cruise missile.

I did a navigation test on Nevada a while back. INS drift disabled. The + appears at range < 10Nm. If you are at low altitude, the + seems to seat below the actual waypoint, under the ground. And the as you close in you see it move up inside the HUD. This is why I'm thinking of parallax. For direct CCPL, with dive designation and using the top of the diamond, I can reliably hit a building.

Check in options you are not in easy radio. But despite new V/UHF radio panel, it's the same logic. - new V/UHF: green radio - old UHF: red radio And you still have one key assigned to each radio to call the corresponding menu.

I'm explaining you how it should work and how it's different from US simulated fighters. So you know the background. In game, the work around is to aim with the top of the diamond rather than the center. It's more likely a parallax error (or lack of compensation). Known old bug :( Also I see sometimes in videos guys doing a designation from 10Nm and then flying level until release. This isn't the good way to do it. Yes the release is done automatically during pull up. A level release would be a stabilized level flight.

Yes, this does happen when you fly close and the contact is locked in TWS. The bug is that the radar should switch to STT when too close.:smilewink:

Ok, so it looks like we have multiple bugs when exiting from CAN/ MAG...

Go at time 10:00. Mirage 2000N performing live delivery during Red Flag 1995. https://www.ina.fr/video/CPC08003568 Mirage 2000 uses radar ranging. The mapping mode isn't good enough to perform radar designation. The radar beam (at least the main lobe) is 3° wide. With a flat angle for designation it's less accurate, so they designate in dive. Not more than 30°, and IRL rad alt is selected as back up in case of radar failure, and rad alt is +/- 30° wide. I prefer to keep the French acronym to avoid confusion with US fighters, CCRP = CCPL. The idea is to use low drag bombs with CCPL to maximize release range and avoid over flying the target area. High drag bombs are released level at low altitude and high speed. The choice depends on tactical considerations. CCPL + PI is a back up mode in case you can't designate for direct CCPL*, the CEP greatly increases (from 20m to around 100m). But CCPL + PI is affected by 2 issues: - release consent bug (the bombs are released as soon as you press the trigger) - DCS map/ mission editor ruler isn't accurate enough. *like low clouds over the target area, this is what happened to French Super Etendard bombing a target in Lebanon in the 80'

I'm away from the computer, but there is another bug which might help you :D Click a second time on "CNM Neutral" clear any weapon selection.

WEAPON Select Neutral (PCA Select) will return to previous mode, not necessarily to NAV mode. So if you had another weapon (AG, 530...) previously selected, you will return to that mode.

2- I will retest when home, but the last time I checked it was ok for waypoints, and using a software for IP offset, it was OK for that kind of attack...minus the release consent which is bugged. 4- apart for high drag bomb in CCIP (where it's actually mandatory), M-2000C doesn't really do level bombing, not in CCRP.

I did already post a YouTube video with AG gun. The normal procedure is to select AG options on PCA long in advance, return to NAV with WEAPON SystemCMD AFT, and go into attack mode when needed with WEAPON SystemCMD FWD when needed. That flow is disrupted with close combat radar mode on first try. If you use keyboard shortcuts or mapped HOTAS command you can change radar range in close combat mode, I managed to lock at 12Nm, but I didn't perform a maximum range test. Nothing past 10Nm should be locked in close combat mode. For the scan elevation I built a custom mission with B-52 flying head on at the same altitude (FL250) from 80Nm. When adjusting elevation the B-52 will disappear while it should be within scan zone according to min & max values next to radar cursor set at target range. If someone pass you a contact to find, you will have to set your radar elevation randomly to find it, you can't do it effectively on the first try. This isn't "clean", it used to work fine. For the list I published in previous message I tested everything after last DCS update. I'm not here to post BS about the module, it doesn't please me at all. I will be happy to report if it's fixed, but both good and bad things must be reported.

Yes, waypoint altitude are supposed to be topographical altitude, not your flight plan altitude. You have to handle that yourself. In western Europe, no topographical altitude is above 25 000ft. I wonder though if Indian Mirage 2000H got a custom INS with higher limit ? :D

- AG weapons: going into attack mode triggers AA radar close combat mode. - radar elevation control bugged: you can't trust the min/ max altitude values next to radar cursor as soon as you move up/ down the scan zone. - TWS: detect only one target. - bore sight mode: offset to the right - vertical scan: offset to the right. vertically it scans +/-15° instead of -10°/+50° - SVI & vertical scan (depending on selected weapon) are triggered before bore sight. - you can change radar range in close combat mode (it should be 10Nm scale only) - the radar screen displays line number setting even when using 1 line mode (like displays 4 in TWS which is 1 line only...it should not) - the symbols used to signify contacts on top or bottom line (V with wings or under lined) are now unusable. Like target at the same altitude, radar elevation 0° on 4 lines scan mode. The contacts should be detected on line 2 & 3 (with overlap). So it should be displayed as simple V. Currently it's switching between V with wings and V underlined. So, if you are new to the module, you will miss all that. But these are recent bugs, some are disrupting newly introduced features useful to build up radar situational awareness. So we went 1 step forward then 2 steps backs. And the coder announced a pause to do something else.

The module does look and fly nicely. If you are new to it I understand you like it. However recent bugs added with work on the weapon system brought it several steps back. So long time users are pretty unhappy (I am).

I have been a long time supporter of the M-2000C, and I had a lot of arguments with Viper. But this time I am heavily frustrated too. The weapon has never been so bugged since early release. After correcting PCA logic for AG, and it did work well, it has been broken again for month without any concern to fix it. The radar is heavily bugged and you would be better with any FC3 module. And this is not about realism, no need to be type rated to see that radar elevation control is bugged or that radar bore sight and vertical scan are offset to the right side. Break something then work on something else. Great pattern :mad:

Overall yes. 12Nm form the shore line/ islands are territorial waters = national territory. National air space is aligned on it. So from a peaceful situation, shooting down an airplane in international airspace isn't a war crime, but at least kind of war act/ declaration. Then it depends, fighters are kind of expendable, and there are plenty of cases where fighters are playing with the limits, get shot down but no war is triggered. Sometimes some retaliations, sometimes not… But once the "hot war" is triggered, international air space won't stand. The air tankers would be placed much farther than 12Nm and behind CAP fighters. Attacking a ship in international waters is a much more serious business. But again, there are some exceptions (USS Liberty, USS Stark…) depending on political situation, and in shooting war there is no rule anymore (just avoid shooting civilians ship). You also have the Exclusive Economic Zone (EEZ) 200Nm frome shore line (fishing, oil, gaz whatever…). If there are less than 400Nm between 2 countries EEZ you split, in the middle.

If you look closely at the picture, the repeater is displaying ********* FF P 010 or something like that... So it's only the green radio on the bottom line.

Last I checked, the button's logic wasn't right :(

The PCA texture has been updated after Chuck’s guide writing. The AG gun button (CAS) should use the same S|P logic as others weapon selection buttons. S: Sélectionné/ Selected P: Prêt/ Ready

I don't really see where you want to go but: - India requested to fit Meteor on Su-30MKI but MBDA said no. https://www.indiatoday.in/amp/mail-today/story/iaf-s-meteor-missile-plans-likely-to-take-a-hit-1249650-2018-06-04 - India requested an early delivery of Meteor missiles to arrive on the delivery of the first 4 Rafale in India. Indian Air Force: IAF may get ‘No Escape’ Meteor missiles in May https://m.economictimes.com/news/defence/iaf-may-get-no-escape-meteor-missiles-in-may/articleshow/72376375.cms So to me it looks like they are eager to get Meteor ASAP. - India is developing Astra Fox 3 missile http://www.ndtv.com/india-news/watch-air-to-air-missile-astra-test-fired-from-sukhoi-su-30mki-2102454%3famp=1&akamai-rum=off :music_whistling:

I think 251 MHz is default DCS frequency... DCS has long way to go for realistic radio management :smilewink: You can find in DCS folder documentation with airfield data, including radio I think. Most airfield have multiple frequencies.

The 3rd party modules live within DCS World. :smilewink: