Lord Vader

Hey @kxct86 Please try to record a short track replay, something simple, like in an instant action mission in the Caucasus demonstrating the issue so we can have a look.

Hey @Mort1234 I believe @Yurgongave you a nice explanation on what you need to do in terms of profiles. I can also suggest something much simpler: that you cycle modes in your HOTAS to CCRP every time the weapon defaults to CCIP. The A-10C is a complex aircraft with a lot of depth to its systems. So I give Kudos to you to make it your first aircraft in DCS.

Hey @Nealius I am reporting this internally for analysis. Thanks.

Hi @Shaki I think when you say "designating" you're referring to the PDLT function. I observed your tracks but they are a bit inconclusive. We did, however, test the same conditions in an MP session and were not able to reproduce the issue. Both aircraft saw each other on the HSD/SA pages and we were able to perform PDLT on the F-16. Do bear in mind, though, that the F-18 takes a bit longer to populate the contacts than the F-16. Were you hosting an MP session? Or was this a dedicated server? Also, if your F-18 can't see the F-16 via datalink, then this needs to be observed on the F-18 perspective too. We would also need the track from that bird to understand what's going on.

Hello @SaladinoSaurus I have raised this internally for analysis. Thanks.

Oh, I see now. You wanted to activate it as a fallback option. I was thinking you just wanted to use the mode traditionally. Anyway, yes, this does look like a bug and I have raised this internally for analysis. Thanks.

Instead of deleting and reinstalled, have you tried a repair? Again, this worked fine on my side.

Hi @Savta35 Please understand that, no matter how well you describe your steps, even with a video, we require a track file to analyse what you are doing and what is going on in DCS when you do it.

Hi @Xhonas I watched your track and I think you need to review how the flood mode works. Unless the track has an issue, I see you designating the target prior to launching. If you want to use flood mode, you need to shoot the missile without a lock. This will use the flood antenna to track anything within the circle. The target is never locked in this mode, but it will be illuminated to guide the missile. As you can see, it is working:

Hi @flyingscotsman Have you tried to assign this to another device? I assigned both IHADSS Brightness and IHADSS Contrast knobs and they worked. I also tried the Cougar MFDs and it also worked for me. To be sure, this is what I'm assigning:

Hi @Akenar-99 This is a known issue in the current 2.9 version. We believe the next update will correct this behaviour with George. Stay tuned.

Hello @Savta35 Several fixes and corrections to these logics are being worked on currently to be added in the next Closed Beta update. We understand this creates an inconvenience and thank you for your patience.

One doesn't affect the other. I may want my Intel to show that a unit "may" be there, showing its general location on the MFD, but not necessarily there. So I'll use Late Activation or even a randomized (flagged) condition. It's "reported" there but maybe it's not or just come later. I can also want it hidden, maybe like it's an unforeseen unit, surprising me. In that case, I'll add it already active or pick the same late activation or a randomized event but remove it from the MFD. You can also hide items from the map itself, even the Mission Editor to make things even less evident. These are all options that mission makers find very useful, especially for Campaigns.

Hello @Apache 64 I've raised this internally for analysis. Thanks.

If you don't want any pre-activated item to appear in your TSD, you will need to add the option "Hidden on MFD" in the Mission Editor. These are not "detections", they act like "pre-briefed" items.

Glad to help. Happy flying.

Hi @dutchili When you enter the CCIP sub-mode, it ignores any SPI indication, slaving sensors to the bomb pipper. There is nothing in that mode to undesignate regardless of what SPI you previously had. The diamond on your HUD/HMD coincides with the last location of designation, yes, but it's actually the last steerpoint with the added deltas. It's not actually a designation. If you press CZ it will revert back to the original steerpoint pre-designation. Hope I could help you understand this.

Hi, @Zarmaand all repliers. This is a known issue with some liveries and is already reported internally. Thanks for bringing this up.

Hi @TAIPAN_ The Viper manual is currently being reviewed internally and a newer version will be released soon. We apologize for possible changes in the current version of the module that may render some sections of its manual a bit outdated. Please consider the fact that creating such a manual is a very extensive work that needs to be checked with available sources.

Hello @Rosly In order to create a case based on your claims we would require a track file replicating a situation you feel is representative of a possible issue.

@ACME_WIdgets Without looking at what your doing and watch axis information when that issue you describe does happen, while we can't really reproduce it ourselves, it's hard for us to provide any resolution. In a single player mission, when you exit it, you need to save that track manually in the debriefing window.

When EGI fails, the TPOD is indeed reverting to pure INS information provided by the last updated data. If anyone has any publicly available information or documentation stating otherwise, please PM @BIGNEWYabout it and we'll have a look.

Hi @ACME_WIdgets After some tests, we are really unable to reproduce this item, including carrying the TPOD on the center pylon as you described, slick or loaded. I am lead to believe there could be a conflict of axis or even an issue with your joystick calibration. Or, perhaps, there is an issue with that mission you were flying in. Again, I am unable to replay that track due to scripting. Please try to fly a clean mission in single player, no scripting, just the conditions you set up and your joystick. If the problem persists, please confirm it with a track and we'll have another look, just to check if it's a local issue. I would also try to open up the deadzone on the Aileron and Elevator axis a bit just to check this isn't a dead zone problem. Thanks for your cooperation.

Hi @SaladinoSaurusplease do send your publicly available evidence to @BIGNEWYand we'll analyse the situation. Thanks.

Thanks @Cydrych, I've added this to the report.