Lord Vader

Hi all I've reported this internally, thanks for your help.

Hello @sepruda I just tested this myself and it works fine binding it to my HOTAS. I can either bind the Canopy Handle - Up and Canopy Handle - Down individually or the Down/Up toggle. Please review your assignments as well as your hardware. There could be an issue or conflict.

Hey @Mal0v It doesn't matter, but thanks. We probably identified the issue and will report it internally. Thanks for the information.

Hi @LorenLuke Your track can't be used because it causes a DCS instant crash. This can happen due to many reasons, like mods or scripts running in a mission. What I suggest is that you record a simple track in single player, nothing too elaborate, just use any instant action or training mission in Caucasus for example and try to replicate the issue. Thanks for understanding.

Hi @nikoel The purpose of this specific mission is to train SAM avoidance and it's carefully tailored to allow you to do just that. When you pass the SA-13, if you follow strictly the route given you can avoid it entirely by flying low over the route. The same can be done if you fly strictly towards waypoint 5 and engage from the hills. You'll be able to mask from the SA-6 on your right side, and easily defend from the SA-8 on your 12. It's all choreographed to allow you to train using terrain to avoid SAMs. Now if you don't follow the route as you do on your track, of course you'll miss the triggers and conditions. The SA-6, for example will not activate at all if you overfly it. Maybe you were expecting something harder or more challenging, I'm not sure. But I'm not seeing an issue with this mission as it is.

Hello @falconzx I watched your track and can't understand what you're trying to claim here. This appears to be induced by the antenna gimbal limits trying to remain within that extreme volume angle. If you have public documented evidence this is wrong, please send it to @BIGNEWYand we'll look into it.

Hi again @=GR= Cypher I checked your track and indeed I can observe the #2 issue. However, this track is a bit tricky to use, since it contains several scrips, including Mist and CTLD. Some of these scripts have been reported to have issues with our datalink logic. I am not sure their creators solved these issues or not, maybe it's related. The point of this is that I tried to replicate the issue in my own simple mission, no scripts, and couldn't see a problem with the IDs and allocation. Of course, I won't suggest you edit your mission to remove the scripts, but it does seem like they could be the cause here.

Hi @Gigafiga We will need much more information than just that. What do you mean "interference"? We will require a short track file of this happening to make sure we understand what you are saying and if it's really a bug or an issue with the mission itself. Thanks.

Hi again. I was able to reproduce the issue and reported it internally. Thanks for your support.

Hello @cptmrcalm Thank you for your track. I will take a look. As for HARMs jettisoning by firing like rockets, yes, that's realistic. They are fired unarmed and with inactive seekers. The only way to "drop" them in a free fall is to jettison the rack itself. This is by design.

Thanks @eror85and @bworld1 For some reason this one slipped our attention. Reported internally for analysis.

Hi @=GR= Cypher Since you didn't supply the Miz or Track file, I created my own simple mission following your steps. Aside from the fact that the Transmit Power is indeed ignored if set to High (may need a revisit), I couldn't reproduce the ownship number and flight lead status.

Hi Actually in order to deselect the target you need to press TMS Up again. This doesn't sound right. I reported this internally for analysis. Thanks

Hi @Pmedic548 As a rule of thumb, whenever you report such an issue, we require a track to verify what you are doing. Also, there was an issue reported earlier regarding this. It's an extensive thread here: TLDR, check you antialiasing settings and verify if you have MSAA selected and try different antialiasing settings. Also verify the cockpit display resolution isn't too low, this also appears to cause the same issue. If none of the above works, regarding those mods, have you checked this feature after temporarily uninstalling those airplane mods?

Hello @darkman222 First of all, when you first try to designate the station, you are beyond the HARM envelope. But that's not what inhibits you from locking. You still have the Markpoint DED page open and you need to exit it first in order to use TMS up to designate the station. Taking over your track, I climbed to increase the flight envelope for the HARM, exited the Markpoint DED page and was able to lock the station with no issues. Thanks.

The thread was closed because all the discussion was done, the bug was reported internally and future updates will bring a solution. The request for a track file was for the original poster since he didn't detail the conditions he was in. As the matter a fact, we still don't know if altitude was his issue here. So please don't hijack the thread with other issues. As for "workarounds" perhaps it's best you wait for our fix since those suggestions are not permanent solutions. Thanks for your patience.

Like I said, I've asked for the tolerances to be reviewed and if any change is required, it will be added in a future update.

Hi @Hootman9104 I've sent this to the team for analysis. This is, however, a very low priority item. But thanks anyway.

Oh, I see. That envolves something deeper, then. Please add this to the Wishlist section of the forum here: https://forum.dcs.world/forum/207-dcs-core-wish-list/ Maybe we can pick up this suggestion for a future feature.

I'm not sure what you mean. This is already in the mission options to restrict the use to the Blue side (unchecked) or allow it to all coalitions (checked). What would be your suggestion? null

Hello all After we reviewed the tracks and observed the conditions, we believe we have found the culprit for your reports. It's actually a feature in DCS, regarding GPS quality. In your track @RPY Variable your F-16C is set to the Red Coalition. As such, the GPS quality is by default much lower than the Blue Coalition. In order to mitigate this, you can select "unrestricted sat nav" option in the Mission Editor or just select a Blue coalition side. I tested this myself with the DCS: F-16C Viper and with the DCS: A-10C II Warthog and you can observe the difference. Without proper or with poor GPS guidance, the GBU-38 can have a CEP at about 30m or even more. So this is actually well modelled. Thank you for your patience and, yes, this was a tricky one.

Hi @Moonshine Offset point altitude issues have been reported and are being addressed internally. Please stay tuned for future updates.

Hi @The_real_slim_Sshep Thank you for the track, but it seems it doesn't depict the OP's deviations. Running your track, I only see a slight error that appears induced by air density. We are analysing if this is within the tolerances for these systems but like someone said above, altimeters are prone to errors and you should expect some deviations from digital readings.

Hello @EPiQWelcome back. Yep, you are correct, the key binding options changed over time. Glad you sorted it.

1 - When is this requested? 2- Like it was suggested, move the throttle levers to fly slowly. This doesn't sound like an error. 3- When is this happening? Are you using your mouse or using a key bind? 4- The tail wheel moves freely and has no directional control. If you remove the lock it will just move where it is pointed. You'll need to compensate with rudder input. This is a realistic behaviour according to our sources. Move slowly, apply proper rudder control and if you want to follow a straight line the wheel lock pin will engage again once the wheel is straight, never before that. As a rule of thumb, whenever you feel you found an issue, please include a short track of the event happening so we can analyse the conditions.