Lord Vader

Hi @WHOGX5 This is a known issue, currently just not on top of our priorities. But thank you for bringing this to us.

We will certainly continue to review George's behaviour and logics. Thank you for your input.

Hi @vctpil Are you using the comm switch to contact JTAC? Are you choosing the correct radio to do so? Sometimes this causes confusion between users. Also, are you using the "Easy Communication" option for this mission? I am asking this due to what you mention above.

Hello @Rufnax Every case is a case when it come to why George does or does not engage with the gun. This is why we ask for a track whenever people feel something isn't right. In most of the cases we observe, we see that the distance can be an issue and George will only lase sporadically until it feels is coming into range. However, in some circumstances, due to the distances, say about 3km, the gun position also comes into play and if it's inhibited by aircraft angle and altitude. If the gun can't compensate for the range, George won't shoot. Whenever this is sent to us as a "bug", we take control, climb or raise the nose and when George finally reports "in range" he always fire the weapon. So, be sure about the range but also aircraft pitch and altitude, remember the bullets need to travel a good distance and with like 3km to go, the gun needs to be quite elevated. So why does George not lase more often as seems to be some people's suggestion? He does lase quite often when in range or close to be in range. Why would he continuously lase for range beyond this limitation if he can't shoot anyway?

Once more, canopy reflections on the DCS: F/A-18C (and other aircraft) are being reviewed. We are aware of some issues and will fix them in future updates. Thanks @GeneralDynamicsfor your findings.

Hi again @JabbyJabara Thanks for bringing this to us. We appreciate when people test these very specific conditions that certainly help us create the best possible simulation. First of all, from a logic standpoint, all equipment available on the aircraft is there to be used by the crew. If an FCR mast is mounted on an AH-64D, it makes little sense not to use it. We can't think of a situation where the pilots would deliberately turn off the FCR and rely on a third party provider for their targets when they can do it themselves. Now, you can make a point the mast can be damaged and rendered inoperable, but then we would be talking about non-normal procedures which, right now, are not really our main priority with this module. This means that, in the future, we may review the functionality of RFHO operation with an inoperable or damaged FCR, but it's currently not a priority. If you wish to take advantage of the datalink sharing, then please operate the system as it was designed (and that you already agreed is working correctly), with a FCR equipped aircraft as donor and non-FCR wingmen as recipients. Thanks for understanding.

I see. George's target finding and tracking abilities are still being worked on. Regardless, it's totally normal that he sees a target but if it's moving or is obscured he'll have trouble keeping the lock. Furthermore, our own position can cause an offset due to the perspective, even parallax comes to play. If that happens and Georges loses sight, he'll try to reacquire. But, after a while if not successful, he'll say something "target lost" and you'll have to request it again. In any case, if you're able to make a track of this issue you're reporting, please do share.

Glad you sorted it out. Thanks.

Hey @JetCat Thanks for bringing this to us, we're reported this internally for analysis.

Hello again @FalcoGer Analysing your track, we've come to the conclusion that you are approaching low with a moving target. George will lase when it feels is necessary and when in range he'll tell you so. The fact that your position and angle of attack limits weapon elevation, limits his ability to shoot at the target. Taking over your track and assume a slight climb, we were able to command George to fire with success as soon as he reports "in range". Thank you for your time.

Hi, @Tom P Please do share a track of this happening. Thanks.

Hi @FalcoGer Please wait for future updates to see this resolved.

@JabbyJabara Please do try again with the suggestions given, and if the problem persists do share that track for our analysis. Thanks.

Hi again, @FalcoGer I reviewed your track and at first George isn't firing due to range. He also doesn't fire closer due to the angle limit of the gun. As for laser ranging, though, it does seem he's not performing regular ranging. I will present this internally for analysis. Thanks for your cooperation.

Hi @JabbyJabara Like @LorenLukementioned, are you actioning the sight to FCR after accepting the targets from datalink? If so, it should work. It seems you need to review the procedures.

Hi @FalcoGer This seems to be correct according to our sources. If you feel this requires a review, feel free to send you documented, non-classified information to @BIGNEWYand we'll have a look. Thanks

Hi @FalcoGer As you may realise, this is something we need a track for in order to observe what's happening. Thanks.

Hi @nighteyes2017 The FLIR and cloud depiction is considered Work in Progress as we continue to improve them. In future updates to DCS World, we expect to improve these visual features. Thanks anyway for your care.

Hi @SharpeXB The procedure depicted in that excerpt refers to the CASE I landing. Although the gear can be extended below 250kts, this is a recommended step (emphasized by the word "generally" at the beginning of the paragraph) at that stage of the landing sequence, as is with the extension to full flap configuration, in this case to avoid the introduction of "balooning" on higher speeds. This text is not supposed to list aircraft limitations. If you look at page 104 and 105 of the procedure of VFR landing, there it is stated the gear should be extended below 250 kts and that's operational limitation of gear operation. The Early Access manual may be reviewed in the future to revise some procedures and suggestions. But in this case, there doesn't seem to be an issue here.

Hi @edudix The switch does spring back into the off position after the start up procedure is performed. Are you pressing it with the mouse or do you have a joystick button/switch assigned to it? If it's a switch, is it a toggle? Have you tried to assign a keyboard command to it? Also the, switch will only revert to off once it passes about 55% RPM, after the throttle is moved to idle. Are you performing the start-up procedure correctly? If you feel this is a bug, please post a small track of your start-up and we'll have look.

It could be a matter of positioning but I don't see it on my side when loading a fresh mission on the same locations. We'll keep an eye out for this one, but for now, I cannot reproduce.

The tag was changed because, like I said above, the JDAM own guidance logics are currently being worked on. So, again, this is work in progress for now.

Hi @creme_fraiche This issue was identified internally. Please wait for a future update to see it resolved.

Once more, I cannot reproduce this in a fresh mission. Are you using the same mission over and over? Have you tried running a simple new mission or even an Instant Action one?

Hello @skywalker22 Thanks for bringing this up, quite a find there, very specific. I've reported this internally for analysis.