vctpil

Hi, I have the F/A-18 stick and I was wondering what was the function of the Sensor Control Switch Depress ? I didn't find the answer on the manual. Thanks, Vincent

Here is the track. AI aircraft with default livery. Tank no texture.trk

Hi, I have the same problem with the adversary F/A-18c default skin.

Hi, Any chance for an update of the NTTR to include some visual landmark like this one : https://www.google.be/maps/place/Crescent+Dunes+Solar+Energy+Project/@38.2400764,-117.3708791,5582m/data=!3m1!1e3!4m5!3m4!1s0x80bc12a045751d3b:0xe272bd32ab77ada2!8m2!3d38.2389891!4d-117.3637676?hl=fr Thanks, Vincent

Hi, I was looking the inverted yellow EW symbols appearing around the compass rose of the SA page (DCS manual p227) or on the radar (DS manual p215). I created a simple mission with differents aircraft flying around, close and far from my position. Those EW symbols does not appear. What condition(s) or option are required for those symbol to appear ? Thanks, Edit : found on p228, but the symbols does not appear.

For training!

Work at 18000ft, not at 24000ft.

Yes, I am! I try again at lower altitude (18000ft instead of 24000feet) and now the LGB does react to the laser point. This should the high altitude laser bug, but also the AUTO bomb to Lightening marked target depends on elev of selected WP.

Hi, The DUD cue appears because the flight path is slightly under the level flight. This is a bug, apparently know. See this video I double check the laser code, and it was the same and currently used.

Hi, The aircraft is equiped with AGM-65E and LGB-12. If I fire the MAV first, the LGB completely the target (see screenshot, the LGB if dropped just over the target!). If I drop the LGB first, the MAV will completely missed the target as well. For each attack, I have reset the TGP and undesignate the target. Any idea about the problem ? Thanks.

I have the same issue with the AUTO bomb mode (No TGP use). Once the flight plan selected and displayed on the HSI, I select the waypoint where is located the target then select WPDSG, but that did not work. At this moment, the square around WYPT disappear.

No problem ShalashakaDS, here's my tests with mk84 : Openbeta AUTO mode No wind sd QNH 27000ft for roll-in 45° dive : a little bit short (right outside the circle) Level flight : see the screenshot! Test AUTO mk84 45deg.trk Test AUTO mk84 Level.trk

Same conditions with the OB and mk84. Not so bad, sometimes a little bit short.

Will do that tomorrow with the mk84 if my standby is not activated.

OpenBeta Sd QNH No wind 5 mk83 release Interval 150 CCIP mode

Tested as follow : OpenBeta Sd QNH No wind 5 mk83 release Interval 150 AUTO mode

Tested with mk83 in a 15° dive angle (I know, I should not use this kind of bomb for this dive angle due to fragment, but it is for test ony). 9000ft QNH / 6000ft AGL Sd QNH No wind 5 attacks and 5 bombs on target or very close to. Should be interesting to know if real F/A-18 pilots use the AUTO mode in level flight.

I was using single release, 30° (18000ft AGL) and 45° (24000ft AGL) dive. Apprently, a level flight of even a 5° or 10° does not work. Is the AUTO mode supposed to work in level flight ?

Mk82, mk83 and mk84 all in the target (or very close). I was excited like Riel in Jetstream.

I forgotten the Jestream video (probably one of the best and the most interresting) and decided to test the AUTO mode during a dive attack, 45° and 30°. AND IT WORKS WITH THE MK82 !! Several tests later, I was a able to put the mk82 sometimes on the target, sometimes close enought to damage it. So, finally, CORRECT AS IS is apparently the correct label for this threat. But the question now is : is the AUTO mode supposed to work in level flight ?

Maybe [iNVESTIGATING] ?

I saw the video several time, very interesting. But he says that the mk82 is falling long, and there are falling very short in my tests, quitely the same position than the mk84 in the video (points red, 12:16).

Exactly the problem I have after a lot of tests. I would like ED team do some tests as well, if time permit for sure, have a look at my track, and tell me what I am doing wrong. Maybe this is bug that came back after an update?

+1

Hi Wizard, Don't worry, thanks for your help, sorry if I feel upset but saying correct as is and showing that's not correct is something I don't really understand. I would interested to have the opinion of Ed about my track file.