The RDN

Hi, same for me here... CTD when using HRM mode both in Multithreading or Normal version.. so single thread isn't a solution Thanks

+1

I may have found a temporary solution for this HTS problem, but I haven't done enough testing to confirm or not. If others want to test this is what I noticed: At the beginning I used the HTS, never had a bug, then suddenly on a mission I always had it... the HTS lost the lock and then impossible to relock. And it was only specific to one mission... so I asked myself what was different from the other missions where I had no problems, and I noticed this: The first tests I did, I had not edited my missions to put the HTS pod in my payloads directly in the mission editors. I was mounting the HTS at the beginning of the mission via the radio groundcrew menu. On these first missions my targets for the HTS were very close to my starting point, barely 10 min of flight to get in range. The mission where the HTS was bugging was a mission where I put the HTS directly in my paylaod in the mission editor, and I turned it on directly after takeoff, but the targets were already further away (almost 20 min flight time before being on target). So I tried it again by setting the HTS at the beginning of the mission (via radio groundcrew menu), and I turned on the HTS about 5 min before arriving on target. And there no probs.... I retested already 4 or 5 times with this method, and to see more probs, but it was perhaps a stroke of luck... so if some want to test to confirm or not if it could be a solution in the meantime... so to summarize; Mount the HTS pod at the beginning of the mission via the grondcrew radio menu then only turn it on right before you have to use it. Good day to all

I all, When ED do the corrections to the detection range of hornet's radar, I was also a little bit skeptical.. but luckily I work on Swiss Air Force, and I know a Hornet test pilot, So I asked him the question. And according to him, beyond 40 nm they can only detect large aircrafts. He can't give me a precise figure, but when I asked him if it seemed credible to him to detect a mig23 or an f4 only from 40 nautical miles (hot aspect with PRF high), he answered that it seemed more or less correct.

Hi, I also confirm, and not only on the A10, on the hornet and the viper too. On the viper it's particularly obvious, there are times when the flir and the IR mavericks are totally unusable. As soon as I have time I will make a track for the viper. A comment from ED would be welcome to know if this problem is taken seriously and put in high priority (it affects an important function of several modules), or will we have to wait almost 2 years like the last flir bug for this to be fixed? Thanks and have a nice day...

Hi, Thanks it works... to long time I haven't use the A10 :doh::megalol: No prob anymore thanks

Hi, I've bought the A10C II and since installed, both on A10C and A10C II I've no more steerlines betweens the steerpoints on TAD.. I have checked on CTL page on TAD but all is "on".. Try on Caucasus and Syria, same prob... here are two screenshots taking in Instant Action Mission Is it a bug or is there a new feature? Thanks

Hi, same issue for me, on caucasus map...

Hi again... Here's an exemple (from 12:44):

Hi... Same problem as you but with the 65D... sometimes it lock, sometimes not, and if I manually lock on the WPN page, is not sure that the missile hit the target.

Hi, It's clearly the same smoke problem that is bugging the FLIR... and ED has been ignoring this problem for over a year now, because it seems that the policy is: if we can't reproduce it, then it doesn't exist. (Personally, I think it's a shame for their customers but well...) So you might as well make a reason, you'll have to live with it ... I advise you to read this thread: https://forums.eagle.ru/showthread.php?t=253277&page=8 there are some "solutions" to know before a flight if your FLIR will be bugged or not (because it's totally random).

Hi, same here… I also had this bug, and other friends I play with online as well. It's random... in the same DCS session (without leaving), I had 2 missions without probs and another one with the bug. I'll try to provide a track sometime... all I can say for now is that in our group we use the carrier deck crew mod.

Indeed there's no solution … totally random bug… and set the chimney smoke to 0 was a good fix before version 2.5.6. A missile smoke trail can turn the FLIR screen totally white.. I have the case with a AGM122 in the Harrier :hmm:

Hi, It seems to be the same case as on this subject: https://forums.eagle.ru/showthread.php?t=253277 For the one who asks for a track: a track is useless... it's a random problem due to the smoke shader... I can have the bug during a flight, read the track and not have it anymore, then read it again and have it... There have already been dozens of posts on this issue for over a year, and I personally have already summarized on several of these topics what the community has found: - Prob appeared with version 2.5.4.29167. - Before version 2.5.6 you could set the prob by setting the chimney smoke density option to 0, but no longer in 2.5.6. (This means that the day the stable version goes to 2.5.6, the bug will be there too, and not "fixable".) - It is clearly the smoke that generates this prob, even missile smoke can saturate the flickering image. - Deleting "FXO" and "Metashader" directories and cleaning the "direct X shader cache" does nothing. Other thread for this probs: https://forums.eagle.ru/showthread.php?t=253277 https://forums.eagle.ru/showthread.p...74#post4212674 https://forums.eagle.ru/showthread.php?t=240675 https://forums.eagle.ru/showthread.php?t=239818 https://forums.eagle.ru/showthread.php?t=239907 So since more one year we have this issue, please stop [investingating] or [checking] or [need track], you have all informations to REPORT IT :mad: Thanks

Hi everyone, This bug is more than a year old and considering ED's policy, we're going to have it for a long time to come... the only reaction after several reports of this bug is that they will wait to develop the new FLIR engine... and you know what?.... I'm ready to bet that the bug will always be there with the new FLIR engine... because it feels more like a smoke shaders problem than the FLIR engine itself... and since ED specializes in adding new features to buggy stuff, I think we're still "laughing" for a long time. Personally I think it's a shame... it's been reported for more than a year now, the community has done a lot of the work in determining which version the bug came from, that it's because of the smoke, that before 2.5.6 (or 2.5. 5) we could fix the bug by setting the chimney fumes to 0 but not anymore... we explain that it's still a bit "game breaking" when at night we can't target a zone anymore, but no we'll wait another year (or more when we know that the new FLIR engine is in low priority)... This means that we have to fly during the day to make sure we have the CCD image as backup in case the FLIR image is buggy. But nothing... nada... we'll wait to develop the new FLIR engine and we'll see... a shame! :mad::mad::mad: