Bearfoot

Yep, we need a RED 4+ gen high-fidelity jet as badly as we need a BLUE heavy attack helo. So this one is a no-brainer: Su-27 (or Mig-29). Though I will take an Apache over either :)

Can I reproduce it 100%: yes How to reproduce/ description: Assign keybindings for "UHF ARC-159 Mode GUARD" and "UHF ARC-159 Mode Preset" Pressing key assigned to "UHF ARC-159 Mode GUARD" switches radio to PRESET mode and vice versa DCS Version:: 2.5.6 (latest as of 2020-05-01) System Specs: Intel Core i7-4790K Devil's Canyon Quad-Core 4.0 GHz LGA 1150 16GB RAM Nvidia GTX 1080 Ti FTW Peripherals: Joystick: VKB Gunfighter Pro Mk II Rev A Throttle Thrusmaster Warthog Pedals: MCG Crosswinds Others: CH Pro Throttle Quadrant, Elgato Stream Deck Headtracker: Oculus Rift S Mission File: Any Log: N/A Track: N/A Video/Screenshots: N/A Mods: N/A

Ah, is this a bug, then? At least, in so far as not behaving as per documentation and/or actual aircraft?

Update: followed the above procedure, and same results. The only way I can get the wings to go to oversweep position is by having the handle raised. However, with the handle raised I cannot close the cover. And I cannot seem to depress the handle while keeping the wings in oversweep. I have to move the handle forward to the 68 deg position to depress the handle, and this brings the wings out of oversweep. I can actually move the handle all the way back while depressed, but this does not oversweep the wings agtain.

I think so, but TBH, I'm not sure. I've been trying follow the official HB manual: http://www.heatblur.se/F-14Manual/procedures.html If wings are not in oversweep, move the wing-sweep emergency handle to 68° in raised position. Then raise handle to full extension and hold until HZ TAIL AUTH caution light goes out and OVER flag appears on wing-sweep indicator. Move handle to full aft OV SW and stow. But this seems to imply a two-step raise. First you raise handle and move to 68 deg, then raise again and wait. I can only get the handle to raise (one step) or deptress. And furthermore, it also implies that you can stow the handle from the second raised position, but this does not seem to be the case. In the instruction you posted, it says "When the HZ TAIL AUTH caution light goes out and the OVER flag on the wing-sweep indicator appears the oversweep interlocks are free and the handle can now be moved to the 75° position and stowed." To move to the 75 deg position, the handle has to be raised, correct? What exactly do you do to stow it then? Just close the cover? Depress the handle? If so, how? Is there a video showing this done?

So, I am missing something here After landing, I open the emergency wing handle cover, pull the handle back to 68 deg, wait, and then pull up the handle toggle and pull it back to its maximum position. The wings indeed go into max oversweep mode. That's good. Now, I cannot seem to push the handle down again in this position. And because I cannot do this, I cannot close the handle cover. The only way I can push the handle down is by moving it back to the 68 deg position, but then, even if I bring the handle back to its minimum position the wings are no longer in oversweep. The handle seems to need to be in the up position to put and keep the wings in oversweep, but in that position I cannot close the cover. What am I doing wrong?

I support this in principle for its realism, but REALLY hope that it can be switched on/off at the user's choice (as a Special Option, for e.g.).

And, it's been mentioned before, but absolutely worth emphasizing --- do NOT look at the basket! Focus on the pod, and just keep track of the basket using your peripheral vision.

I think you can replicate this issue even when starting out in TWS-Man, giving the az / elev commands (check to see if Jester is in TWS-Man), and then firing a phoenix. Key mashing starts immediately.

As others have said, the key is practice, practice, practice. But there is practice that helps, and practice that doesn't. I can tell you that it will take a while, and worse, for most of that while you will feel like you are not making any progress at all. I can tell you that one day it will click into place, and very soon after that, you will get it. You will still have a ways to go before you can comfortably and reliably do it every time, but still, you will get it. And on that day, you will be wearing a ear-to-ear grin for a week. You can spill coffee on yourself and be dumped by your SO and have your car wrecked and lose your job, but nothing will be able to take that grin away. Do NOT start with the VIking. Start with the KC-130, flying straight and level at 250-300 IAS. At first, just try to fly in formation with wings in bomb mode and probe out. Get trimmed up so that you stay in formation for second or two even if your hand is off the stick brielfy. Then set yourself the goal of getting plugged in. Stabilize in formation just behind the basket, then increase speed to plug, controlling for gain in altitude. Do not worry if you disconnect right after. Make it a point to get in some daily practice with 10 plugs ("contact!") minimum before you do anything else in DCS. Then work on staying connected after plugging in (typically, by correcting the overcorrecting that you do after plugging). Then work on staying connected for a full tank. Then move to the KC-135, again, as straight and level. Then move to the Viking, straight and level. Then move back to the KC-130, but this time in a circular orbit. I find that HUD mode cruise helps so you have a reference as to your roll vs the tanker. Then move to the KC-135, again in a circular orbit. And finally, the Viking. In between some of those later stages (especially after beginning to practice the orbiting tanking), move back to some of the straight-and-level ones to see how much you have improved. It will be remarkable! Then work on staying connected till full.

Would this help until proper support comes? https://forums.eagle.ru/showpost.php?p=3877480&postcount=118 Add to "C:\DCS World\Mods\aircraft\F14\Input\F-14B-Pilot\keyboard\default.lua": {pressed=device_commands.HSD_Knob_Course, up=device_commands.HSD_Knob_Course, cockpit_device_id=devices.HSD, value_pressed=0.0028, value_up=0.0, name=_('HSD: Course Knob [+1° very fine] - CW'), category=_('[19_CTR] HSD (Horizontal Situation Display')}, -- *** CUSTOM *** {pressed=device_commands.HSD_Knob_Course, up=device_commands.HSD_Knob_Course, cockpit_device_id=devices.HSD, value_pressed=-0.0028, value_up=0.0, name=_('HSD: Course Knob [-1° very fine] - CCW'), category=_('[19_CTR] HSD (Horizontal Situation Display')}, -- *** CUSTOM *** {pressed=device_commands.HSD_Knob_Heading, up=device_commands.HSD_Knob_Heading, cockpit_device_id=devices.HSD, value_pressed=0.0028, value_up=0.0, name=_('HSD: Heading Knob [+1° very fine] - CW'), category=_('[19_CTR] HSD (Horizontal Situation Display')}, -- *** CUSTOM *** {pressed=device_commands.HSD_Knob_Heading, up=device_commands.HSD_Knob_Heading, cockpit_device_id=devices.HSD, value_pressed=-0.0028, value_up=0.0, name=_('HSD: Heading Knob [-1° very fine] - CCW'), category=_('[19_CTR] HSD (Horizontal Situation Display')}, -- *** CUSTOM ***

Folks, with all due respect,this is about a radial menu option or a key command or any way at all to ask Jester to switch between TWS auto and TWS manual. Complaints about Jester inefficiency etc. are a little tangential, and there is another entire thread about Jester vs direct keybinds specifically for dropping tanks here: https://forums.eagle.ru/showthread.php?p=4034579

This goes to TWS Auto. At least that's what it seems when I jump in the back briefly?

I agree, but honestly, I will take an option on the radial menu as well ... but it does not seem to be there. We can command TWS or RWS as pilot, but that goes to TWS Auto. I tried hopping into the backseat and selecting TWS MAN but it resets when I go back front. So, this means that as SP there is currently no way to go to TWS Man?

How? Is this an option in the radial menu?

Does this exist? If so can someone point it out to me? On the Jester radial menu, I see only "Radar Mode -> Auto", but nothing to switch from TWS Auto to Man. This is badly needed because of the horrible bug right now in commanding azimuth/radar elevation while in TWS Auto. A key-bindable command would be great, but as far as I can see there is not even a Jester menu option?

Thanks for clearing that up, all. I really would love to have a (flyable) A-6. The F-14 and A-6 would be the perfect team! And I love the idea of a maritime strike mission with some stick-and-rudder chutzpah.

Bug reported: https://forums.eagle.ru/showthread.php?p=4308010 Please contribute any additional information / experiences you folks might have that might help solve this!

Following on from: https://forums.eagle.ru/showthread.php?t=271334 Running latest Beta, at some point Jester begins hammering away at one of the keys. Like several times a second. Non stop. Does not let up. At least the last couple of times, it was a radar mode key. When I hopped into the back seat (in SP), I could see the "RWS" key being continuously pressed and release, again and again and again etc.. Nothing I could do to stop it (including pressing other keys or press the same key). From the pilot seat I tried deactivating and reactivating Jester (crew contract), silencing him, commanding a new radar mode (TWS, RWS, auto), etc. Nothing stops it. ANd, of course, this makes staying in any other radar amode impossible (including VLS LO, which is pretty useful in, say, a dogfight!). I cannot figure out how to replicate it yet. It started happening last night. I've flown a few missions where this did not happen (e.g. AAR practice). As I noted on the other thread, so far the only commonalities of missions where it did happen is: (a) after I've commanded radar elevation at a certain distance (b) fired off some AIM-154's[ © gone feet dry But this is really a tenuous correlation. I will update this thread as I learn more. EDIT: Ah, this appears to be a known issue, reported under a different form (the "inability to engage PLM" rather than "jester hammering a radar mode button preventing engagement of PLM [or other modes]") as reported here: https://forums.eagle.ru/showthread.php?t=271118 . The cause seems to be, specifically, "giving Jester radar elevation or azimuth commands when he is in TWS-A". Work around is currently telling Jester "to switch to TWS-M first. Note: when a phoenix is launched, he cannot switch to TWS-M"

Ok, this is definitely a bug. Have not figured out the conditions under which it occurs, though so far (probably coincidentally), the last four times it has been (a) after I've commanded radar elevation at a certain distance (b) fired off some AIM-154's © gone feet dry The only reason I mention the last is because the RWS-mashing happened right after that. Could be unrelated to all or any of these three. Running latest beta on Caucasus map.

I have this too And it is not just annoying. It's game-breaking, depending on what button he is pressing. E.g., last night, it was no problem -- he was mashing away at something that did not interfere with operations. Tonight, however, he kept pressing on RWS, which meant I could not stay in VLS LO. In the middle of a dogfight ... :( :( :(

Sure. You can also eject :). Either way, the immediate problem is solved. Either way, though, continuing any meaningful activity beyond sight-seeing is impossible.

Here's a spin on this .... were Tomcats ever considered (or was there any planning/training) for the maritime strike role? They obviously never carried stand-off weapons for this like the Harpoon, SLAM, or Maverick (though https://fas.org/man/dod-101/sys/ac/f-14.htm says it was possible they could?), which the A-6's and Hornets could. (1) So did the maritime strike torch pass directly from Intruders to Hornets? (2) What would be the feasibility/realism of Tomcats dropping dumb freefall munitions as antiship strike? I think the Argentinian Skyhawks did this in the Falklands, but I imagine this was exceptionally dangerous and aircraft would be shredded by a respectable CIWS?

https://www.navysite.de/cvn/deck.htm

^ True You will need 4 goats to break even Goat: $300 2080Ti: $1200