Goliathus

You ask how you can acquire and maintain lock no matter what even on enemy using jammer. You can't, this is the whole point of jamming. If there was anything you could do about it, the jamming would become pointless. To be honest, jamming in DCS is probably not a simulation, it's just modeled 'somehow'. I'm pretty sure this can't be simulated because documentation about jammers is probably classified. This why it seems like jammers in DCS make it impossible to maintain lock until certain distance and 'simulates' what would jammer do, if used properly. So no, you can't maintain the lock, just try to maintain your SA.

This issue was reported in the past and it is on ED's To Do list. Maybe somewhere in the future they will fix it. It's no big deal to the game play so there are bugs that are with much higher priority.

In my instance the thing that helped me the most with AAR is to "be very gentle with the throttle". I try to control my closure rate and anticipate reactions of my plane, because decreasing the throttle input won´t change the speed instantly (for obvious reasons). So before my first attempt to reach the basket I make sure that I have my closure rate under control and that I´m able to change the distance to the tanker by few feet only. Then it is much easier to connect to the basket, because anytime I see I´m not aligned with the basket, I can simply slow down and extend the distance by few feet before another try (when I was new to AAR, I hated how I had to approach the tanker after unsuccessful attempt from a long distance and pretty often from a wrong angle - this is something I did because I flew too far away and had to change the altitude and attitude to avoid midair collision with the tanker. Everyhing just because I was too fast and wasn´t gentle with the throttle enough) . Using this method I was able to refuel at night without NVGs using only the light from my refueling probe. I´m not any AAR guru though... but good enough not to fall from the sky

I tried your solution today, but with no luck. I always get response "Rearming complete" despite the fact, that Voiceattack stands clearly that I explicitly requested crew to install the NVG. It must be some kind of bug in the Vaicom pro plugin. Only way I can overcome this issue is by using the options menu. No spoken command can force the crew to eqip my flight with NVGs...

Thx, I´ll try this later when I get back to DCS this week. But as I remember things, this was not the reason why it didn´t work. I can recall one time when I got reply to my request "Unable to comply" (or something similar) with additional information that my cocpit isn´t accessible due to canopy closed. But after I opened the canopy, I got only "rearming complete" reply and no NVG was installed at all. It seems to me like if only the VAICOM PRO plugin doesn´t work with this command correctly, because using the menu I have no issue at all. I checked the voiceattack if my command was recognized properly and it was, but in game it didn´t force the ground crew to equip me with NVGs. I´m able to overcome this issue by using the menu, but I like to play the game without the menu and with "hide on-screen text" enabled.

Hey guys, I´m experiencing an issue in my F/A18 C Hornet using vaicom pro plugin. When I request crew to install the NVG ("request NVG" command), I get response "copy" and then information "rearming complete". But I don´t get any NVG installed. I tried to search this forum, there are plenty users reporting same issue since beginning of 2021, but no one responded or given any advice. Is this a known bug of the vaicom pro plugin or is there any solution for this problem? Thx. Goliathus

Hey guys, I want to open a topic about TALD usage in DCS game play. No mean to criticize the TALD implementation, it's great to have them simulated and they have obviously important place in real military life. But what tactics do you find best for the usage of TALDs in DCS? I'm thinking if it is reasonable to shoot TALDs on SAMs to saturate its RADAR or force it to stay turned on, when I can saturate its radar even with JSAWs that can bang the thing with plenty of luck if they manage to get through the defense... In DCS money isn't any issue, so there is really no reason to shoot TALDs instead of something more expensive and there is also no reason in DCS to force the enemy to spend expensive missiles on cheap decoys only to ruin his budget. There is clearly an advantage in numbers - it is possible to carry 4 more TALDs than JSAWs. Can you think of any other pros carrying TALDs? Do you have any tactics that you use more successfully with TALDs than without them? Please consider this only as a general discussion, that can help to build some tactics for the TALDs in DCS. Cheers, Goliathus

Hi ED, it would be lovely to have a special setting for the burble effect (on/off), affecting only the existence of the burble effect in the gameplay. At the moment it seems like it is possible to experience the burble effect only if the "wake turbulence" is on, which affects the CPU performance a lot when plenty aircraft is in the air, so it is pretty common for players to disable the wake turbulence to get rid of the stuttering. If it was possible to enable only the burble effect, maybe it wouldn't cause any stuttering for those who don't have a high end PC and they could still experience more realistic carrier landings with the burble effect. Thx. Goliathus

Hi BIGNEWY, I can see this post is still tagged as if the trackfile was still missing and as if it was not a reproducable issue. I´m sure that issue mentioned in our posts isn´t a high priority case, because it´s not affecting gameplay that much. But I´d just like to ask you to confirm if we lately provided enough information for the ED dev team, so it can dive deeper into this issue somewhere in the future. In my previous posts there is a video track, steps how one can reproduce this issue, and there is also a short trk. file. Thx. Goliathus

Here is a track replay, I hope this helps to find out what are we talking about and why this happens. I flew a free flight instant mission on the Persian Gulf map and recreated the "TK PRES LO" issue. Goliathus TK PRES LO.trk

This thread is still marked as "investigating", "can not reproduce" and "need track replay", so I did some testing and made a track replay of the issue. Please ED, look at this way to reproduce this issue anytime you want: 1. You must change the value on the barometric altimeter to different value than is the default value (29.92 inHG) BEFORE you reach the 20.000 ft altitude 2. Level at alt. between 20.000 - 20.100 ft 3. You get the TK PRES LO warning instantly 4. Then you can play with the barometric altimeter settings as you wish and see that returning to the default value (forcing the altimeter to show less than 20.000 ft) clears the "TK PRES LO" warning. I tried this in the free flight mission in the Presian Gulf map and in other instant missions as well. You get this issue all the time, but only if you change the barometric altimeter value before you reach the 20.000 ft. If you don´t change the barometric value on the altimeter at first, leveling at the 20.000 ft and playing with the values won´t work to reproduce this issue. Here is link to the track replay: Please note that I´m aware of the fact, that in this mission the briefing says that QFE is 29.86 inHg, not 29.92 inHg.

If there is any problem for the ED to reproduce this issue, I can do this anytime I want. It is very simple. Just fly straight to the altitude 20.000 ft and don´t exceed 20.100 ft. Then just change the altimeter pressure setting and voila - you get the TK PRES LO message. Then change it back to the default pressure setting and the message is gone instantly. This can be done multiple times if you stay flying between 20.000 - 20.100 ft. I fly the liberation campaign missions and set the altimeter pressure to the value in my briefing page. And it seems like the only way to avoid this warning message is not to set the altimeter pressure, but then it is not showing the correct barometric altitude, which can be an issue during landing approach on a carrier. If the ED still can´t reproduce this issue, I can upload one of my liberation missions to help checking if it is not related only to the Liberation campaign messing something in the mission editor´s settings. To be honest, I din´t try if this issue persists in any of the ED´s original missions. I hope this helps to investigate this issue. Thx, Goliathus

Hey guys, I found out that I experience this issue only if I set the barometric pressure on the altimeter differently than is the default value (29.92 inHG?). If my mission briefing says, that the pressure near the Carrier is e.g. "30.12 inHG", I usually modify the barometric pressure value during the cold start procedure. After that I pretty often get the "TK PRES LO" message after I climb to the 20.000 ft and it lasts only for a second or so. It doesn´t seem to me related to my current fuel state (in DCS). Goliathus

Hi, I started another DCS Liberation campaign and I´m not experiencing any issues with HMS or INS anymore. Seems like there was just something bugged in my previous campaign, because even after aligning the INS properly (no GPS -> turning the knob after INS aligned into NAV position) the HMD symbology was still drifted elsewhere than it should be. Just wanted to let you know. Goliathus

Hey Skywalker22, do you know how far you were from the tanker when you tried to tune its TACAN signal? Maybe I´m just guessing, but I found it from time to time impossible to catch the TACAN signal if tanker was too far away from me. It´s very same with other TACAN beacons as well, probably due to signal strenght weakening with distance. Just check if this was not your case. Goliathus

Thanks for your answear, Tholozor! Ok so for some reason my campaign runs without GPS at the moment, I´ll try to look more into it and to find why the GPS is missing (the date when its happening is may 2021, but OK, maybe I messed something up when starting the campaign or it´s some kind of Liberation campaign bug for this specific campaign). Just to be sure I aligned the INS properly even with GPS missing - I ran all fire tests, started the APU, then the right engine... after the right engine is lit up, I usually run the BIT test, then I swith the radar to stby and INS switch to CV (I was taking off from a carrier) to get the INS aligned - I speed things up by using the stored heading button. Meanwhile the INS gets aligned I turn on the IFF and DLINK, start the left engine and do other settings, that are not important to mention. After I get the "OK" message and information about the alignment quality (0.5) I switch the INS knob to NAV. Doing this cleared all INS messages from the MFD, so I didn´t get the "INS RDR" message. But the HMD is still not centered properly even after I do the HMD aligment So my last question and then I´ll solve the whole thing by running a new campaign - am I missing something important in the INS aligning process (when aligning without GPS), that could cause the HMD in advance not to align properly? Maybe I forgot something, but I fly the DCS for 1.5 years now in the F/A 18 C with zilion cold startups without having almost any issues.

Guys it is definitely INS related. Despite the fact I'm not sure what am I doing wrong. I tried to run a different Liberation campaign and whole issue was gone, the HMD was absolutely fine. Then I switched back to the first campaign and the HMD was disaligned. Only thing I can tell is, that if I move the INS to IFA, there is an "INS RDR" warning on my MFD and it goes away only if I switch the INS to NAV. Unfortunately it doesn't solve the imprecise HMD. Now I'm sure it is a Liberation campaign issue, for some reason there must be something set differently in this particular scenario. I thought maybe I'm missing the GPS, but that shouldn't be the case because the campaign takes place in the 2021 and I tried the INS aligning with moving the switch only to the NAV and it didn't change anything. There is still a decent chance that I'm doing something wrong in the INS aligning process, something that I'm not aware of. Do you know what does the "INS RDR" message mean and what should I do with it? I play DCS for more than a year and I saw it for the first time only after I started this USA vs. Iran campaign. Thx. Goliathus

Hey Sacarino111, yes, INS was in IFA, after I did the CV stored heading alignment (because I was on a carrier). Now after you asked - I did find it strange after I started this new campaign, that after I switch the INS to IFA, I can still see on my HSI page the "OK" message. It stays there all the time, and that´s definately strange behavior. It never did before, so maybe there is something wrong with the INS in this campaign and I´m missing GPS in my Hornet despite the fact it´s taking place in 2021. Maybe I should try the slow INS method and put the INS to NAV to see whether it make some difference or not. If yes, then I should report a bug to the Liberation Campaign creators, because it´s not DCS related.

Thx guys for your replies. Unofortunatelly I don´t have time for DCS any other day than on Friday and Saturday evening, so I wasn´t able to do more tests yet. Maybe I won´t be able to play DCS this weekend at all, because I was asked to go and help on the Ukraine border with transporting friend´s family fleeing from the war zone. I don´t know yet when or if they manage to get to the border, so we´ll see, and it is more than 1000km trip for me too. So mabye no DCS for me this weekend. Just to explain what I was experiencing - I play DCS solely using the Liberation campaign generator, I´m not sure if this mission generator can influence how HMD alignment is working, but I don´t think it can. At the moment I run the USA vs. IRAN campaign that is taking place in 2021, so I don´t think I can have any issues with doing the quick INS alignment using the stored heading, so even this shouldn´t be the culprit what could affect my HMD not aligning properly in the advance. While doing the HMD alignment, sometimes I´m not able to hold my head still enough to align the crosses properly at first attempt, but I always do the fine tuning until crosses match perfectly. And I get the "Aligment OK" message all the time. I didn´t have any issues with HMD aligning before...

Another crazy picture - it seems like even HUD is affected by this "bug". In this mission there is target marked by the red smoke, it is laser designated. I locked the target using the FLIR LSTD with the help of grid coordinates entered as my waypoint. In the picture you can see on the HUD my waypoint as if it was ahead of my aircraft. Except it isn´t, cause it is to my left, as you can clearly see the red smoke and on the FLIR you can see that the target I´m looking at is on a distinguishable field to the left. Anyone experience this too?

Thx for your reply. I finaly had some time to play DCS again and I can post some screenshots of the issue I was talking about. Drifting cues aren´t the thing I meant, because it happened since like forever. My issue is that my HMD is misaligned even after I do the aligment process and everything shown in the HMD is offset from the spot it should be. I did the aligment procedure dozens of times before, I do nothing differently. Hence I have this issue now. In the pictures you can see my wingman in the red circle and the "B" sign is flying somewhere far above him. The other picture is maybe not that clear, but you can see on the flir where I´m looking and on the HMD you can see, that the mark is quite offset. I tried aligment on the deck, even in the air, or do the realigment process... nothing helped.

Hey guys, anyone having issues these days with HMD alignment, too? In the past, it was common after I did the HMD alignment and looked on my wingman, I saw the circle marking my wingman falling from the place he was at to the ground and then it recentered and started to fall again. I think, it was because of the small distance between us and refresh rate of the datalink. But now I have strange behavior of the HMD and it seems to be misaligned someplace above the center even if I do the alignment procedure (correctly). Thus I see enemy contacts few centimeters off the place they are at (even if they are like 40 nm away) and the thing that really bothers me - even ground targets and tpod marks are not positioned correctly. What am I missing? Is alignment procedure broken since some last update? Because I do the alignment procedure the very same way for a looooong time without any having issues ... but I do have now. Thanks, Goliathus

Thanks, I thought so. I usually don´t carry any HARMs if my main focus is on Tunguska SAM, cause it doesn´t use its radar most of time. Thats the main reason why I get shot by Tunguska so often, I can´t see it and I´ve trouble finding it, especially if weather conditions aren´t very welcoming at the site. But its fun anyway, I just thought, that maybe if the SA page is capable of showing AG contact at their exact position, there is way how to get my FLIR at exact spot using SA page. Nevermind Who knows, maybe real F/A 18 C can´t do anything about it either.

Hello everyone, do you have any suggestions how (or if) I can make my atflir to look at a ground target shown only on my SA page? Its common that my god-like AI buddies spot plenty (non-moving) ground targets mirraculosly from a pretty decent distance and I can then see them on my SA page, if they are engaging them. But I don´t see it that usefull, cause I can´t see what they see and I have to try to find a needle in the hay stack with my atflir. This is why I ask this question - yesterday I played my DCS Liberation campaign mission and I was frustrated by several Tunguskas guarding the frontline, because I couldn´t assign there for a CAS mission any AI operated planes (they would get killed almost 100% chance). I could see the Tunguskas on my SA page as a known threat, but it is only an approx. location and I can´t lock it via SA page. If it was a day time and I wasn´t in need of operating with NVG, I could try to make the atflir to look at the location near the Tunguskas using my JHMCS and then check the SA page if my atflir is looking somewhere nearby and eventually make some corrections until I managed to make a lock and get a kill. But this is not easy and at night it is almost impossible, if you´re wearing NVGs instead of JHMCS. It is mainly because it takes a lot of effort to slave the atflir to the right spot chcecking only SA page if you´re slaving the tpod in the right direction or not. So is it possible to slave the atflir to the exact location of Tunguskas using only my SA page (e.g. to the spot where I move my TDC cursor on the SA page)? That would help a lot, if it was possible, cause then it would take just few seconds to make the atflir look at the right direction and then just search in a relativley small area for any ground targets. If I don´t want to get too close to known threats, then I have to search for the Tunguskas from quite a distance and Tunguska is a relatively small target to search for even if you´re looking in the right area. I find it almost impossible to search for Tunguska without using SA page showing at least approx. location of this threat and I don´t see a way how make the atlfir to cooperate with the SA page enough. Thx for your help. Goliathus

Hi, let me picture my problem, which brings me to file new topic to the wishlist. I like to play DCS with Liberation Campaign, which generates missions to me and works as a dynamic campaign system. It is very capable and generates missions with plenty of ground units in the frontline area. Anytime I bring my (usually not very capable) AI wingman with me anywhere near frontline, he reporst me the location of all spotted ground units and he never SHUT UP his mouth. Yea, he gets annoying, but that is not the issue, you can change the COMM channel or just mute it. The issue is, that if your AI wingman gets excited, he feels the need to report you ALL ground units he spotted and you can´t talk to him until he feels like he´s finished reporting. This issue leads to plenty strange situations, like me giving him orders to engage bandits, which are about to kill us, but the wingman is smartass and doesn´t listen to you, at least not until he´s finished. Ok, not until then, cause he usually gets killed by the bandits he refused to engage. Is it possible to change the radio coding, so you can interrupt your AI wingman talking and give with new orders, so he will obey your commands even if he feels like reporting all non lethal threads is more important than respecting his flight leader? It doesn´t seem to me like if this is some hard work on the DEVs part to make this possible. I get it, that all the RADIO comms need much more work, maybe reworking, but this little thing could bring a big improvement to the way the AI wingman listens his flight leader. Because if you´re in the battle, there is nothing such as "Wait 5 min until I´m done reporting", I need my wingman to obey my commands right away or provide me info, that he´s unable to do so. Thx! Goliathus