earnil

On Mi24, that's exactly what it is. It's a visual aid for the pilot. It doesn't read AOA though, it will indicate yaw on vertical axis and climb or descent on horizontal one.

Thanks Grover, but in that case, reseting the programmer should be irrelevant with Jester shouldn't it, since Jester does it on it's own. Can you please post step by step how you rearm countermeasures in the plane with Jester? I fully acknowledge that it's probably my incompetence at this point because EVERYONE tells me it's just 'easy' and just do it like 'you always do', but as posted above, I tried almost every possible combination and I can't get it to work.

Hi HB, unfortunately, even after this was supposedly fixed according to change log, I just can't make it work. I tried: -> refuel / rearm-> don't touch CM sliders -> F8 - F6 to set CM count -> F8-F6 to set CM -> refuel / rearm -> don't touch the sliders -> set the sliders -> refuel / rearm -> F8 - F6 -> set the sliders -> F8 - F6 -> rearm / refuel went back to RIO seat and reset the CM count none of this works. If I'm doing it wrong, can please somebody, who actually made it work and seen it work tell me, how to do that? (btw I'm talking about plane with Jester. It works with human RIO).

Is there any update on this?

My apologies for the bump, but would it be possible at least acknowledge that this is being looked into?

I was told that maybe my procedure was not entirely correct, so hopefully this is the track with correct procedure. After expanding all flares 1) Refuel / Rearm the jet 2) I'm not touching the sliders at all 3) Use the F8 - > F6 menu to reset the CMs. Still doesn't work, unfortunately. This is with Jester. F14 CMS Test v2.trk

For what it's worth, this works for me so far as a workaround. https://forums.eagle.ru/showpost.php?p=4191203&postcount=3

Sorry for the bump but can anyone at last acknowledge this is a bug? Or are we doing anything wrong with the rearm?

Here's a track file showcasing the countermeasure issue, in SP, using F8 menu to rearm. It doesn't work - the rearm doesn't work. I have tried any combination of using just F8 -> F6 menu, F8 -> F1 menu, doesn't work. As you can see, in the trackfile I did use the F8 -> F6 method, then rearmed the jet without touching the CMS setting - if I understand it correctly, this is the right method. This is really extremely annoying bug, especially for MP, since it takes 2 years to start and fuel the jet. Thanks a lot in advance, hopefully you guys can have a look. F14 CMS Test.trk

If anyone is struggling with this, I wanted to post a short update here with a workaround First, there appear to be 2 distinct bugs 1) Under certain conditions, Jester seems to input desired waypoint coordinates as your plane's actual position, breaking the alignment 2) When selecting waypoint, the waypoint selection works ok, but then the wheel shows incorrect information as bonesvf103 mentioned. Regarding the 1) this seems to work for me almost 100% of the time: During startup, after your engines are both up but BEFORE you continue and before the INS alignment is past first stage, ask Jester to enter WP1. Then follow through the startup, wait until alignment is complete, until Jester says 'ready to taxi' and then you can start to input other waypoints. When you go through the startup, once you power on HSD you should see correct distance an bearing to WP1 ALWAYS input just 1 at a time. Let Jester finish it, then input another. Keep the HSD in NAV mode as you enter the waypoints Don't change WP1 Following these steps, I can now use the waypoints freely without messing up the alignment. I cannot say if all of these are necessary or if the timing is bit more loose (like adding WP1 during INS alignment seems to work too) but this is what works for me.

I think the problem is that the behavior is not entirely consistent. I've experienced same thing. In some instances, when you pull Gs the blackout is gradual and can be controlled. But in some cases, the onset of blackout is immediate and happens when there's still plenty of non-blacked area. Actually, it seems to me that it happens when you slightly unload to control the blackout. Here, find attached my track when this immediate onset happens at the end of the flight. The visuals look exactly as Daniel's F16 video - you pull gs and suddenly with approx half of the screen not blacked out, there's immediate switch off. Before that I was pulling Gs, including 10.6gs but I got this nice, gradual controllable blackout onset and didn't black out. It seems to me that the problem is rather that the onset of the blackout somehow stops working, so it allows you to pull much more Gs without getting your visual cues and then, when you unload the airframe it suddenly 'wakes up' and snaps you out. F14 overG example.trk

Bump, hope it's ok, but this behavior is still present

Well yeah you can, but sometimes, actually, most of the time you need to both maneuver the jet and set those things so switching between seats is kind of tedious. And the OP said he wants to join the squadron ultimately so that kind of precludes that SP part too.

You need to ask yourself first what do you want to do. While F14 has some limited A/G capability, it's primarily an fleet defense interceptor so you're mostly limited to A2A missions. Moreover, while Jester is imho fully adequate in A2A, you still lack the capability for controlling the TPOD. Also, you need to realize that most of the things you do in F14 with Jester, is telling Jester to do things. Essentially, you're limited to the 'pilot shit' (flight + dogfighting) and everything else, especially BVR / advanced A/G is run from backseat. If you want to change scan distance, you need to tell jester. If you need to lock contact, you need to tell Jester, if you need to set up bombs / rockets, you need to tell jester. So the actual gameplay consists a lot of just clicking in Jester menu. I still enjoy it, but I think it's fair to point out that it may get very repetitive for some and since you said that F18 feels bit videogamish, trust me, that F14 with Jester is far more videogamish in that regard. For example, let's say you're setting up bombs - in F14, you just tell Jester to do it. In F18, you need to do it yourself. In F14 you just tell Jester to set up waypoint. In F18 you need to do it yourself. More over, as far as I can tell, most squadrons will tell you to get a RIO and GTFO with Jester. F18 is pretty versatile jet and will allow you to do everything. A2A, A2G, antiship, SEAD/DEAD,... So as a study plane, it gives you much more broader pool of things to study. Granted, the FBW is far less satisfying to fly, but I think anyone can confirm that putting it back on the ship at night in heavy rain is not substantially easier then F14:-) So again, up to you depending on what you want to do, but I just wanted to pierce a bit the myth that F18 is gamish while F14 is proper analog plane. With Jester, not really.

I think I've figured it out. First there's a bug https://forums.eagle.ru/showthread.php?t=256380 for some time already that makes all the waypoints wrong if you try to set up anything else then WP1,2,3. Second, since the jester wheel appears to be shifted, if you enter WP3, it gets input as 'Fixed Point', thus triggering the bug. Third, if you set WP1 and 2 only, even though the wheel is not correct, Jester actually switches WPs correctly So, bottom line, if you use WP1 and 2 you'll be fine, if you use anything else everything breaks down.