Lord Vader

Hello @LaFleur I have sent this to internal analysis. Thanks.

Hi @Rotte The AGM-65F is a "fire and forget" weapon. It will only acquire what you tell it to acquire. If the target is moving, then it can reacquire another higher contrast target under very specific conditions, but only in the very close vicinity, like an overlapping structure, for example. For that matter, make sure you have a secure and confirmed lock prior to launch. We would need a track replay to understand what you are doing.

Hi @Shaman Like @Sharkku said, your description is somehow vague. We need to see what you're trying to do and require a track file to do so.

Hi @some1 Thank you for the information and reference. I have reported this internally.

Hi @some1 I have reported this internally.

Thank you again. We are analysing all the presented data. We will be investigating this with the team. For now, please, if you have that documentation to support this is a bug, please send it over via private message.

Yes, but the condition to use the rocker switch is not related to the OTHER page itself. If you want to cycle Waypoints using that, you need to be on the Waypoint page. In our manual it's never said the ability to cycle waypoints or mark points for navigation is available in the OTHER page. Just that it enables the selection of the FSKs. If you think you are seeing a discrepancy in the simulation, please send any non-classified public information about the actual operation to @BIGNEWYand we'll have a look.

It's a bug, it will be fixed in the near future, just not a top priority right now. Just turn them off manually for now. Or just add rain and justify them.

Hi, @GumidekCZ I don't understand what you're trying to convey here. The OTHER page is only used to activate the function select keys (FSK), just below the CDU screen. The Waypoints don't disappear, they're still on TAD and you can see them on the top line on the display and even cycle them using the Steer switch (between the two dials). The OTHER page position is used to select the various sub-pages, it's not a navigation mode. So in this Mission/OTHER position, if you're in the WP/Waypoint page, it's defaulting to the WAYPT page. If you add a number in your scratchpad and press LSK1, you'll get Waypoints, if you add letters you'll get Mark points. Please tell me what am I missing here.

Hi @target I ran your track and the auto start sequence is stopping because your collective isn't down as required. The system warns you about it and you see in the axis window your collecting is about halfway. When I took control and moved my collective down, I ran the auto-start and it worked ok for me.

Hi again, @Star57 Now I see it. Thanks for the tracks, reported internally for analysis.

Hi @flavnet I am unable to reproduce the issue. I pressed TMS-Right short and it correctly turned all targets in range into system files in TWS mode. Please check your key assignments and let us know if you still have a problem by adding a short track with the issue occurring.

Ok, I'll let the team know about this.

Hello again, @Moonshine We've analysed this new item you presented and we confirm the adding of an altitude error to the new FIX performed. However, you are only performing the FIX itself and you also need to perform an altitude correction, remember these are tridimensional points. You can do that with the ACAL functionality. Hope that helps, this appears fixed at this time.

Hey @Star57 I have sent this to internal analysis. Thanks.

Hi @Star57 I am sorry but we are unable to reproduce the error you describe. Running your track, you only designate one L&S target. In that state, any other track files will not display speed or altitude until you either designate a secondary or move your cursor above it. Here's an example of designating a secondary target (diamond) with the indicated speed and altitude on it. I never saw that "zero altitude" indicator you mention at all. I have to ask, are you on Stable or Open Beta? If you are on Open Beta, can you perform a Repair on your DCS and report back?

Hi @SPAS79 I have reported this internally. Thanks for letting us know about it.

Hi @MavOne96 This command is set to a 3 way switch, and parking brake being a held position. Have you tried to bind your keys for the "up" or "down" positions? For example, set on position to PB and another to "down"? This works on my bindings.

Hi @Geraki I've reported this internally for analysis. Thanks

Hi @Edward3018 The work in improving and enhancing George is still undergoing. I can't give you any estimates, sorry. The best way to follow the updates on each module is to read our changelogs.

Hi all. Even without accurate visual references, the overlapping seems wrong. I am raising this internally for analysis. If you do happen to acquire non-classified information, even pictures, please send to @BIGNEWY. Thanks.

Hi all, thanks for your patience. These systems are being refined by the team and we will have a better radar logic in the near future. For now, some of the features may require some work around.

Hi @Moonshine I will bring this again to the team, thanks for your cooperation.

Hi @Falconeer We are aware of this and are working on a fix. Thanks for bringing this up, however.

Hi @Buzz313th As much as you make a great explanation of what's going on, we prefer to observe a track of the event so we can understand what's going on. From your explanation, it seems you're confusing yourself with the deltas you may have added before during your engagement. Whenever you move the cursor in a weapon sub-mode, you'll adding deltas which then can only be removed by zeroing that cursor. This is just my own speculation, I would need to see exactly what you did.