Slim_Kermie

I did not encounter this problem until the most recent beta patch went live. Cold-War-Syria-v111_DME1-20230625-070649.trk dcs.log

I have noticed that on multiplayer servers with magic IFF enabled, using the IFF filter will sometimes cause all contacts to be ID'd properly and then disappear from the radar. When this happens, the radar is unable to pick up anything aside from ground clutter. After a period of time (not sure exactly how long), the radar will begin functioning normally again, but the IFF filter will stop working entirely. What I mean by that is that pressing the IFF button has no effect at all - all contact icons remain the same, including both friendlies and bandits that are on the scope at the same time. This occurs in situations where the IFF was functioning normally beforehand. I saw the bug twice today on back-to-back sorties, which are both on the log file. Thanks for taking a look at this. dcs.log

I have only seen this happen under three conditions: Overweight at high altitude Trim not reset before slowing to a hover Turning in a very tight circle at speed and OGE 1 seems like LTA, 2 seems like the autopilot & flight control curves trying to murder me, and 3 definitely seems like some form of LTE. LTE from wind direction might not be modeled, but you sure as heck can lose tail rotor effectiveness if you turn too quickly in the Hind.

So far I have not seen anything on the PFL, but I have not checked every time. I will start doing that when I run into problems.

It happened again, this time with the GB-6. Third sortie, at the end of the replay: https://we.tl/t-607Pl6PM8E dcs.log

I experienced a similar situation again where I could not fully select the SD-10 while in vertical scan mode. It occurs at the very end of the linked replay: https://we.tl/t-WImMh5P1oI . I will check back in with more replays if I experience the bug with other weapons. dcs.log

I tested it several times in a custom mission and was unable to replicate the bug. The SD-10 was selectable and fired in both BVR and vertical scan every time, even after landing and rearming. I did encounter the bug 2 days ago with LD-10 and GB-6 SFW loadout. The replay is very long though so I will wait until I see it another time (and quit right away to keep the track shorter!). The only odd thing I noticed before the bug occurred was that the "LD-10 ON" option on the SMS page was not present. When the button that should have said it was pressed, the LD-10s turned on and aligned like normal, but "LD-10 RDY" on the HUD was crossed out. I will post here again as soon as I have more information and another track.

Additional info: Weapons that don't fire can still be jettisoned, which ironically results in LD-10 and SD-10 missiles launching in passive/"mad dog" mode, respectively.

Sometimes, weapons systems on the JF-17 will not fire/release. Once they fail, nothing will fix them. The bug occurs in singleplayer missions and on multiplayer servers. For example: sometimes one weapon (ex. GB-6 HE) will drop, but the other GB-6 HE will not release even just two seconds later during level flight. Sometimes both GB-6 will drop, but then the weapons on outer pylons (with rockets, LD-10, etc) will not work. Sometimes only the gun will work, and sometimes nothing will work at all. Quick facts: Weapons switch is on "armed" (not safe or training) Weapons not damaged by over-g (no pylon damage indicated, and the bug occurs in A/G 2 mode as well) DTC updated and uploaded Speed/altitude restrictions observed for weapons like 802 AK Once one weapon fails, it will never work again, even after repair and re-arm. Only death/respawn can fix it. Weapons sometimes fail one at a time, and sometimes all at once (and sometimes everything works just fine and nothing fails) Can affect all weapons (even the gun - yes, the "feed" button is used) HOTAS buttons confirmed working correctly via "adjust controls" - correct keybinds light up every time I have not experienced this bug with any other aircraft, and I never experienced this bug before the 2.7 update. It seems to happen most often on a second or third sortie, but this is not guaranteed; Sometimes the weapons will fail on the first sortie, and sometimes they will never fail. Unfortunately, I do not know how to reproduce this bug, as it seems entirely random. I have not been able to find any single factor that will cause the bug to happen 100% of the time. The replay and log show a failure of the SD-10 during my second sortie in the 17. The second sortie begins at approximately 48 minutes into the replay, and at ~52 minutes, something happens in the replay that did not happen in-game: When I went into Vertical Scan mode, I selected the SD-10 instead of the PL5, and everything looked normal. However, in the replay, it shows that nothing is selected in the lower box instead, while the SD-10 is selected appropriately on the upper visual indicator. A few moments later, I start attempting to fire the SD-10s at the F-15 (right as it starts to turn around), but nothing will launch. I like the JF-17 simulation. It is very fun and well-produced, and I enjoy it. Thank you for taking the time to debug it after its release. Note: the dcs.log is attached, but the replay was too large to upload along with it, so it's on a file sharing website for one week: https://we.tl/t-GtziW8HMQ6 dcs.log

+1