Lord Vader

Hey @Gunfreak This is an AI error, not a module issue. Please post this in the correct section to get proper bug support.

Glad you sorted everything out. Happy flying, full burner now.

Hi @goAdA We believe this will be mitigated in a future update to DCS World. Please try again after it is released, if you can. Sorry for the inconvenience.

Hey @Hotel Tango Like we've stated in this forum thread (and in other occasions), the F-16 ROE logics "will be refined in the future, as soon as we clear other priorities". Thank you for your report, however.

I'll tell the team to have a look. Thanks.

Hi @G-Tech Thanks for the track. It's acceptable to have some residual IAS in vertical flight but this sounds a bit much. I'll send it to internal analysis.

Hello @JFisher Please clarify the steps you're taking to reproduce this issue. Is this happening while you're in the RTE sub-menu selecting DIR? For something like this we often ask for a track file of the event for our analysis.

Thanks @itn, appreciate the link.

Hey all, we believe we have found a fix for this internally and apologize for the inconvenience. Stay tuned for future DCS updates.

We'll, when you engage the recovery mode you can probably see a bigger movement of the control surfaces. But I'd say that's a bit hard to discern if you're in a dogfight.

Hello @itsthatguy We're planning to update the DCS: F/A-18C manual in the near future and apologise if it's not giving you the information you require. Regarding the items you mention, I'll address them one by one: It does work. Make sure to set the correct conditions for it. This is correct according to our references when using the JHMCS. If you think this is incorrect, please provide non-classified documented evidence this should be otherwise (via PM) and we'll look into it. Again, we would need evidence this isn't working correctly with our depiction of the F/A-18C Lot 20.

Hello @GumidekCZ Thanks for bringing this to us. I have sent this to internal analysis.

It's all a matter of optimization, really. Like I said, we're working on it.

Hello @Nzaviator Though I understand what you're saying, can you create a short track with this happening, especially when you mention reaching speeds like 40kts?

Hello @Ahmed Very strange indeed. Thanks for bringing this up, I've reported it internally for analysis.

Hey all. We are aware of some user reports about performance. We will analyse possible optimizations for this module and thank you for your patience.

Hello @Hotel Tango I've raised this internally for analysis. Thanks for bringing this to us.

Hi @Dave62ndFF This is a small side-effect of a current limitation. Though not at all intended, if you turn the mirrors on (you'll need a keybind to do it) the image will be correctly replaced with the correct reflection of the CH-47 cabin perspective. Sorry for the inconvenience, and thanks.

All of the above. Thanks for bringing this up anyway.

I don't know exactly what you mean by "recognizing" if this mode is engaged. Looking externally, I don't think this can be easily identified, perhaps the plane will move in a way you're not expecting. Other than that, I'm not sure.

Hello @Carbon715 The Closure Rate of a tracked target in the FCR shows speed in TAS, while your HUD is displaying your own speed in CAS. @itn Please link that report you mention and I must ask what are you basing your assumption the CR should be CAS and not TAS.

I think I understand what you mean. I believe this is just the way AA tries to correct the smaller details and lines in those textures. Have you tried other AA methods? Like DLAA?

Hello @Hotel Tango It's a bit hard to understand what you're trying to say. I can't see that flickering you mention, at least. What AA setting have you selected in the graphics options?

A new up to date manual is being created for the DCS: F-16C. Please take into account this a complex document for a complex system so it's taking a bit of time to produce. When it is done, it will try to include all the systems logics currently in this module. Thanks.

Hi, this is a known issue, not just with the AH-64D. We're already working on a fix. Thanks for your care, though.