VC

Hello, I finally bought the full version of VA recently and installed this pack, having a few issues right off the bat though. Firstly, some of the commands call a "beep-disconnected.wav" sound file which doesn't exist and is not provided in the pack. Secondly, I currently use the special option for the radio menu "OPEN MENU: RADIO MENU KEY FOLLOWED BY PTT" and would like the profile to work with this. I guess I'll have to manually edit it, but just want to know if anyone has done this, what needs chaning and where do I start? And how would it interact for example with which radio I want to call on? As part of this, I noticed that because I have a UK keyboard layout, the button it expects for comms menu \ doesn't work. Is there a quick way to change all the commands that use it? The in-game control mappings are mapped to \ but the VA profile is using a button that physically doesn't exist on my keyboard, if in VA I press the button that gives me \ in game, it selects #. Finally, I have no intention of using ClickAttack (don't think I even can in VR), can I just delete these profile lines to stop it doing that intro action?

Ah, I avoid those anyway, too much drag ;)

Excellent, then I am happy. It seems the MiG-21 has better weapon selection ergonomics than I expected!

Is the interaction between these correct at the moment? It seems if the missile type select is in IR, it will fire IR missiles one at a time regardless of the pylon select position: e.g. I have SARH missiles on pylons 1&2, IR missiles on 3&4, pylon select is on 1, switch is on IR, it fires pylon 3, then next time it fires pylon 4 even if I don't move the pylon knob. And reverse, if I select SARH on the switch, even if I put the pylon select to an IR missile it fires a SARH from a different pylon. If the missile type select is neutral, then it fires whichever pylon is selected regardless of missile type. I assumed "neutral" position was a sort of "safe", and that it would not fire at all if the missile type and pylon select are mismatched, or the selected pylon is empty.

Ah OK, if it's a known issue then that's fine I can wait for a fix. The way I have it seems way worse than the other reports, but it is usable as long as I bear in mind to treat it with suspicion and follow actual calls as well as DL HAFUs.

I assume it's a simplified process at the moment based on range and closure rate, not IFF. I do want to see friendlies sometimes, especially ones fighting enemies, but I don't think we can expect a huge upgrade to the complexity of this. With a real human AWACS operator you'd be able to discuss what you want to see in different situations. Especially with the Tomcat, I want to see threats 100 miles away so I can plan my engage. Of course I also want to know if someone just crept up below me, but not the friendlies chilling around the airbase I just happen to be above crowding out more important things.

Thank you!!! Wow, this finally makes sense I missed that there was a limit. :doh: So basically on a busy server it will always only show things close to me. Is there any way to affect what it's showing, e.g. filter out friendlies temporarily?

Didn't help :( Screenshot attached is on Growling Sidewinder, Tbilisi is about 170 miles on my 12 o'clock. Nearly full server, AWACS has called out multiple bandits high altitude to my 11 and 12 o'clock. But all my TID is showing me is a bunch of friendlies next to me.

He's on it by default but yes I have. And I have told him to turn it off and on again, tune to something else then back to AWACS, no luck. Thing is, I do see AWACS DL contacts, but only under certain parameters. I've done a complete uninstall and reinstall of the F-14 module, and a repair on DCS to be sure. Will test again.

As far as I understand it's a realistic limit but can be a bit annoying. You need to plan ahead. My tactic now is to take my first BVR shot with tanks on, turn cold then judge my fuel state and the situation. If I'm safe and I have tons of fuel I would repeat. If it looks like things are getting heated or the tanks are nearly empty anyway, I re-engage with a high yo-yo or zoom climb so I'm slow enough at the top to drop the tanks but not wasting the speed I have, instead storing it as altitude and diving to accelerate for the next attack. Also just standard BVR advice, if you're below Mach 1 you're too slow.

And if you ever find yourself thinking "huh, I wonder why that guy just started cranking" you should already be doing something about the missile on its way to you :megalol:

When TID shows not a single enemy HAFU from DL despite there being 30 people on the enemy team on a sever they can only take off in two places and the fight is always in the same area, AWACS spamming calls so you know roughly where they are and that it can see them. And all you can see from DL are a few friendlies right next to you... something is very wrong.

I don't see most enemy DL contacts even when I logically should, e.g. AWACS is giving me BRAA calls to them but they aren't on my TID. More detail: https://forums.eagle.ru/showthread.php?p=4453761#post4453761

I recently got back to flying Flankers a bit and tried turning on pilot body in cockpit for extra immersion, since I don't need to click the cockpit anyway. But I ran into a problem with the body/view position. The default head position looking straight through the HUD has the eyes somewhere in the pilot's chest. If I move the head position around so it is logically above the shoulders of the pilot 3D model in the cockpit, I can't see most of the HUD because I'm too high. Looks like the seat is not in the right position for how tall the pilot 3D model is, or something else is up with the proportions.

Missiles fired at you in TWS should never give you a launch warning. Are you sure that's what you mean? Or you were not getting the missiles active (pitbull) warning? I flew the J-11 a couple of days ago and was getting the angry pitbull warning fine. Were the missiles fired from way above or below you? RWR has blind spots high and low.

Once Fox 3s are involved you should be fighting based on standard engage/disengage patterns and respecting minimum abort ranges, not relying on trying to work out if/when the missile was launched.

I agree with this bit, had no real issues with Jester recently. He was swapping modes fine, putting the scan zone where I told him, locking and only dropping when it was completely understandable for that to happen. Last night I had an issue in a sortie where TWS-Auto would not come on even when firing AIM-54s at TWS tracks, but I don't think that was Jester's fault. I managed to reset the Auto by clicking to SP then back to PH. One thing that was Jester's fault is calling "we locked a friendly" when PAL picked up an enemy. Made me second guess and miss a kill, but I got away. How was your datalink picture on the busy server? That's still somehing I have a problem with.

I've been having a persistent problem with the F-14 in MP for a couple of weeks now (haven't had time to test in SP). The server has good AWACS coverage but in the F-14 the datalink isn't showing obvious enemies that the AWACS definitely can see. I know it can see them because it's giving me BRAA calls to them... but they aren't on my TID. I also know AWACS can see them because if fly e.g. an F-18 the DL shows a trail of red all the way back to the enemy airbase. But in the F-14, little or nothing especially at long range. Sometimes the DL HAFU appears on my TID after I scan the area and my own radar picks them up, even though logically it should have been there before. It also gets more reliable if they get close to me (like <20 miles). But I basically never have a complete picture on the TID of what the AWACS can see. Sometimes friendlies drop off too, it's like it has a range filter on or something. I've made sure it's on and set to AWACS as host, it does work but as I said really inconsistent as to what it shows. Does anyone have any ideas what could be causing this?

Does anyone else have weird datalink behaviour as part of these radar bugs? I noticed the last few times I flew the Tomcat I don't see most of the enemy DL contacts. Some of them pop up some of the time, usually when I get close to them or if my radar can see them anyway, but a lot of contacts that DL really should see clearly either aren't there or pop in and out.

I was only saying "appear" because I was trying to help interpret what I believed pepin was trying to say, not make any claims on the matter. If my observations from my watching the tracks are incorrect then so be it. I know the missile is old and its guidance isn't great, I have no stake in it and I'm happy if it's accurate as it is. But if the missile is lock-on-before-launch (which we know it is) then it should be flying its internal PN intercept course from launch, not turning into the target then having to reverse its turn as it flies to get back onto a collision heading. I don't really understand what you mean by "APN parameters which look like pure pursuit but aren't".

I think he's trying to show that in DCS it doesn't. In his tracks he fires at the Hornet when it's not nose on to him. I looks like the 27ETs turn towards the target until they're nose on and, at least for the inital stage of the flight, appear to track in pure pursuit not PN.

Yes, this is clear, the second missile overtakes the first. But this is, in part, because it is not turning... it is not tracking the target. Can you really predict intercept yourself accurately enough to get hits at real long range with ET?

OK, I did not realise it cleared the setting. I was moving the collective hoping to return it into the range that the auto-altitude had control authority but now it makes sense that if I was clearing it, then it would sink past set value. Is it enough in this case to just tap the collective brake off/on and then it sets your new altitude?

I understand what you are saying, but in your track the missile that you fire first, with lock, is the one that hits. The second one, after you unlock and override, doesn't track the target at all.

OK thank you, I will try TWS again both Auto and Manual. I still find the behaviour very odd, in every other plane the default mode is auto scan zone as soon as you assign a target. I may only be one button to press but on the real plane this button isn't even on the HOTAS (we can cheat a bit there).