Lord Vader

Just a reminder to all that the HMD issue with the gear down has been reported earlier and it is already fixed internally, waiting a future update. As for the other issue mentioned mid-flight by @SgtNickElis, there are a lot of items that we need to verify before calling it a bug. Like @_SteelFalcon_mentioned, the DMS aft long press will temporarily turn off the symbology and you have to take into account the blanking settings. I would also add that sometimes in some missions the HMD is not the default device and users will not notice they have NVGs installed. I would also make sure no mods are interfering with this feature. But, if all above isn't valid and you still feel it's a bug, as @BIGNEWYsaid, we need a track to understand what may be going on.

Hi again @CrustyJim After reviewing this report and especially your track, we have found that this isn't related to either the SAM system or the map. In your track, you engage the first SA-8 then proceed to set up a Mark Point. After you do so, however, you do not exit the MARK DED page. This is a recently introduced inhibition based on documentation that when a HTS designation exists, it should be dropped or a new HTS designation is inhibited if, among other conditions, pages like the MARK, FIX or A-CAL pages are displayed on the DED. You do not see the designation being dropped because you switch to the WPN MFD page and to aim your Maverick, while having the TPOD on the other MFD. Taking control of your track, returning to the HTS page and exiting the MARK page you left open on the DED I was able to designate the other target. Re-entering the MARK page again will remove the current designation and inhibit a new one, as expected. This is working as intended.

Hi again. Thanks for the tracks. This has more to do with a possible issue with the EO-VIS mode than with the DTOS/VIS delta logic, although, of course, it is related. The EO-VIS modes are still WIP right now and we will take a look at this again in the future. For now, whenever this happens, you can press CZ in CCRP to remove the unwanted deltas.

Hi @esequiel This was reported internally.

Hi @esequiel I will take a look at your claims but I can advance, that yes, every submode will have its own deltas. That's how it is modelled right now.

I see, @admiki The most common issue with IAT is when someone is applying an input. As soon as any input is applied to the MAN TRK controller, it releases the TADS turret for manual tracking, like not having a dead zone. I believe this is what's happening here. It doesn't matter whether LMC is on or not, actually. I just felt it was exacerbating the issue.

Hi @Lineaxe Yes, like it was said above, a track would be necessary to understand what's happening. Also yes, a "huge amount of Lua code" mission can create logic issues. Try again in a simple mission with vanilla files and save that track if you're able to reproduce it.

Hi @ACME_WIdgets We do require a track of that happening in order to understand what is going on. Please try to replicate the situation in a short track. It would be really helpful.

Hi @Akenar-99 I tried your track and it seems you have LMC activated on that non-moving target. I took control, deactivated LMC and it stood in place. Could this be the problem? You should only use LMC on moving targets.

Hi @FalcoGer This was reported internally. Thanks for your help.

Hi @Hotpocket13 Like @TobiasAsaid, we need something to go with. That log can have some answers. Just remember that every time you load DCS it will renew the log. Just try to capture a new log if it happens again. I've tried the DLINK page on the DED in multiplayer and had no issues.

Hello again @Gunslinger52 Just tried your tracks, as well as fly for a good period of time and could not reproduce your issue. Switched places a few times and flew for about 10 or more minutes, opening the George AI window several times. I would suggest you run a repair on your system and go from there.

I'll have a look @Gunslinger52

Not a problem, @Vortex225. This clarification will be useful for everyone that struggles with this logic.

Hi @itn I may have truncated part of the text I wrote there. I have edited it above for the sake of clarification. Thanks for bringing it up. Every deltas added by current weapon delivery submode can only be removed by zeroing the data. I am sorry if I mislead you.

Hi @Beciak Your description is clear, but you need to share a short track with this event happening. Also, the video is a bit too short to figure out anything. Thanks.

#2 - The steerpoint disappears because it's occluded by the TD Box. It is the steerpoint diamond with added deltas. #3 - That's the steerpoint, yes, but also with added deltas. (edited) As you describe, you are always in VIS mode and I already explained how in that mode the deltas are added and cannot be removed with TMS aft. You need to select CCRP/PRE then press CZ to remove the deltas and reset it to the original position. Please, once more, do not consider Matt Wagner video as a reference anymore. Future product manual updates will attempt to clarify this. I believe you're being mislead by earlier depictions that have been refined over time.

Hi @Floyd1212 I bet there's an issue with that mission, yeah. I counted at least 15 Roland batteries, plus some other SAMs, that's just an overwhelming amount of threats for the RLWR to process at once. I seems the system is just cycling through all detected stations and will eventually stop once all are reported. This mission is also incredibly heavy, my PC was struggling to keep up, btw. I tested a simple mission myself with two Roland batteries and was unable to reproduce the issue. The RLWR will report each (if tracking) and again when they come online to intercept a threat or I come out of terrain masking.

Hi @boerdi It does look like a weird bug. But without watching the exact events it's hard to say what's going on. I understand the track is too big and yeah, it would probably not be useful. I tried several long missions in 2.9 already and never had this issue. You said George stopped responding, was he alive in mission? You could have been shot and he got hit. Again, hard to say without more context. All I can say is that it really looks like a controller command being sent. I trust your words you checked your inputs, so it has to be something else sending that command. Keep an eye out for this one. If you or anybody else is able to replicate in a short track, please send it over.

Hi again @Vortex225 I understand this subject matter may cause some confusion to many. It's not easy to understand this single SPI logic on the Viper, especially when coming from other SPI logics, like the A-10C. I ran your tracks and noticed that you may be confusing the TD box with the navigation cursor. You are pressing CZ (or TMS aft) while still in VIS or DTOS. Like I said above, this will not actually remove the deltas, and will just move the TD box back to pre-designate state (caged to the FPV). I took over both tracks and were able to remove the deltas by choosing PRE or CCRP. None of the actual steerpoints moved like you claimed. In order to attempt to make this more clear, please note: Each mode has its own cursor deltas and pressing CZ will command different actions, dependent of the mode you're in. So if the cursor is enabled in MARK mode, for example, it is only moving that markpoint pipper, if it's in VIS/DTOS mode, it's only moving the VIS cursor, etc. If it's in CCRP/PRE, on the other hand, CZ zeroes on the designated point. Same command, different results depending on the current weapon delivery submode. Finally, the steerpoint symbology isn't actually removed when a TD box is created, it's occluded by the TD box itself. I don't see an issue with either of your tracks.

Hi @Gunslinger52 I watched your track and it appears you are trying to hit the tree trunk at the base and then halfway. I do indeed see the rounds hit beyond the trees once you move up the trunk, but this is expected behaviour. Not only are we dealing with a limitation of how trees are depicted (not affecting sensors and weapons, something that may one day be reviewed), this is also a perspective illusion. Even though you are aiming "just above", the targeting is actually being performed way back in the terrain. Something that's even more evident because you are aiming at a sloped area. So the weapons will fly further. Try to do this on a building or a large object and you'll see how it compensates correctly.

Hi, @Subferro This was reported internally for analysis. Thanks

Hi @giullep Even though we consider George to be Work in Progress, whenever reporting such events we need a track to understand what is happening, no matter how good a written description may be. This is our procedure. Regarding what you said happened, I was unable to reproduce the described issue.

Hi @Emme Not having a track file, it's hard to say what is wrong. But with that configuration you are very much on the MTOW limit. Like it was said, conditions like air density and temperature will affect your performance. Make sure you plan accordingly.

Hi @jazzviper Indeed this is a known issue, already reported. Stay tuned for future updates.