Lord Vader

Hi @Shimvolski Can you supply a track of this happening?

I'll have other people test on their side. Rest assured we're trying to figure this one out.

Thank you all. I have reported this internally.

Hi @_SteelFalcon_ Thanks for bringing this to us. I've raised this internally for analysis.

I understood your report on the original post, but like I said, I did exactly what you described and I don't have this issue: Originally created: New mission, generated from custom template. What I suggest is that you run a repair and see if this helps fix what you are seeing.

Hello @Voy This is indeed an odd one. I've reported this internally.

Hi @Moonshine Following your instructions, I was unable to reproduce your reported bug. I created a new mission, added 4 F-16s (also tested with F/A-18s and A-10Cs), saved the group as a custom template. STN: 201, 202, 203, 204. As you mention, I closed this mission, opened a new one and loaded the template. STN: 201, 202, 203, 204. If, however, there are more units in the mission, the spawning of this template will continuously generate unique STN sequences. If I add more than one template, it will also continue to generate new numbers, also sequenced. This is by design. Please help me understand what is the issue here.

Hi @Istari6 As much as we like Tacview as a blackbox tool, it doesn't offer the proper replay analysis of what you are doing in the cockpit. This is critical to our analysis. If you feel this is a bug, we need your track replay in DCS. I was able to test the MK82 and MK84 with drag kits and was successful hitting targets. So we need to understand what you are trying to do. Thank for understanding.

Topics were merged. Like @Raptor9said, the current implementation is correct according to the variant we're replicating in DCS World. Please remember videos or documents created months or even years ago may contain certain procedures that could have been refined by new documentation, subject matter expert input or just a better understanding of certain logics. This is why it's important to follow the changelogs for the updates.

Hi @=BoB= David This is a known issue, we're trying to solve it in future updates. Thanks for your patience.

Hi all. For these types of reports, always make sure to test the ILS system with various maps and even different runways before claiming the system doesn't work. Sometimes it's the runway itself that has an issue and not the module. I've tested this in the Caucasus map, approaching Batumi and it does work. If you still think this is a bug for the DCS: F-16C feel free to add a track and I'll take another look. If it's map related, perhaps take it to the corresponding map forum.

Alright, looks like you're programing it like I am. I do see CMWS not recognizing the initial position, but not the others you mention. I will report it internally for the team to have a look. Thanks.

Thank you all for your help. I've finally reproduced the bug. It does indeed require a certain set of coincidences, but it does need addressing. Reported internally.

@Captain Orso Sorry for this back and forth, but I tested this in my side and it appears that only CMWS is ignoring the preset switch position. I just want to confirm I am programming just like you do: Two sided switch, one side to CMWS, BYPASS or Jettison Cover OPEN, another side to NAV, Auto and Jettison Cover CLOSE. Or are you using the single toggle command?

Hi @=BoB= David Thanks for bringing this up. The IR marker effect will be reviewed in future updates. Stay tuned.

Hi @SickSidewinder9 Please create a small track with what you're doing and we'll have a look. Thanks.

Hi @Captain Orso I'll probably ask the obvious, but are you turning on the option to sync the controls to your HOTAS on mission start in the Miscellaneous section?

Hi @FalcoGer This was reported internally for analysis. Thanks.

Hello @OfficerBull Adding to what everyone as said, yes, George will do its thing even if you set up its station. Remember it's an AI and it will operate the systems with a certain pattern. As for it missing or not registering targets, it depends on a lot of circumstances. George is still "WIP" and will get refined as we continue to work on it. That being said, feel free to record a track of certain any circumstance you feel he's misbehaving and we'll have a look. Regarding TADS/IHADSS as acquisition source, I believe you were already oriented.

Hi @grim_reaper68 and @ThatSillyGinge I personally never seen this particular bug. Are you moving forward in the CPG POV? Can you supply a short track with this happening? I would like to know what are your visual options as well, if you can share them.

Hi @Moonshine We believe we have fixed this internally, please wait for future updates and try again.

Hi @FalcoGer Looking forward to that track. Thanks.

Hi all. Some aspects of the operation of the AGM-144L are still being refined by the team. Much like other systems, we ask that you wait for future updates. Keep and eye on the changelogs and report what you find. Thank you for your patience.

Hi @Voy This was reported internally. Thanks.

Hi again, @Jalava It's confirmed. Ground Power Switch 3B powers the armament computer. Since the CAGE button is associated with the SMS page it won't operate until that particular system is powered on. This is correct behaviour. Thanks for bringing it up, though.