earnil

My apologies for the delay. Here we go. AV8B WAYPOINT visible.trk

As per description - the waypoint shows on second MFD as if the HSI was extended all the the way there. See attached picture

An update. It happens in cold startup too. I went through full alignment, the PREP 00 coordinates are correctly input, they match the initial position, F10 map and WP1 is set to same position. Yet, HSI shows 5.1nm to the waypoint. BUT, when I move, it changes to 0.8nm. I'm not sure if this is within tolerance for M2K, still seems like way too high. Hope this helps...

Ok, this one is bit complicated so hopefully it will make sense. The problem is, that after correcting the INS drift by changing the coordinates in PREP 00, the HSI is still showing heading and distance as if you were on the old 'drifted' position. I'm attaching a track & picture, hopefully it's more clear from that. How to reproduce the issue. 1) Cold start - full INS alignment 2) input your start position as WP1 3) verify that HSI shows minimal distance from your position to WP1 after INS is aligned 4) take off, fly until INS drifts 5) land - verify the distance shown on HSI and the INS drift 6) note your current coordinates on F10 map 7) input your current coordinates to PREP 00 and WP1 8) check HSI As per attached picture, after landing - the coordinates in PREP 00 and WP1 are SAME, ie the HSI should show distance 0 (or approximately so). However, it still shows distance as if the INS drift has not been corrected and plane is at the 'old' position. This can be fixed by switching off the INS and rerunning the full alignment again. I haven't tested the inflight alignment. M2K INS dirft can't be corrected on the ground.trk

Can someone explain why the feature is activated at all then? Is it because of the carrier? Otherwise it makes no sense to have it active if it's broken, regardless of whether it's ED's fault or RAZBAM's fault.

As per description, it seems that it's impossible to remove the wheel chocks with engine running. The ground crew responds with 'Unable to comply'. You have to switch off the engine, then it responds normally.

For anyone that is actually looking for solution for this - you need to have the EXP switch in off position when you rearm countermeasures or switch it off and on again once you complete the rearm.

Hey everyone! As per title - if you expand your countermeasures, land and rearm, the CM counters are reset as if reloaded but the actual reload doesn't happen. Regardless of rearm, you're stuck with whatever was loaded in then plane at the beginning of the mission. Observed both in MP and SP. Track attached. AV8B CMS rearm not working.trk

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.

You're right to be skeptical. They'd probably use pre-planned coordinates from datacartridge or datalink.

To be absolutely clear, I have no idea whether this is how it even works in a real jet. This is what seems to me to be the best description of what the FCS is doing in DCS. It makes sense that it does, but the effects in actual jet may be completely different. The problem is, that the simulation may be 100% accurate in terms of aerodynamic and technical factors but you have to consider there are vast differences between how the real plane interfaces with the pilot and how the DCS one does. Things like speed of the trim, the movement of the stick, stick resistance, that's impossible to simulate correctly, just by the simple fact that there are hundreds of different sticks with different spring loading, different forces, how fast the computer repeat the trim commands,... It's entirely possible that what results in a dramatic ballooning in DCS and what needs to be arrested with rather dramatic stick / trim input is IRL a gentle rise that can be easily delt with by couple taps on trim button (and actually if you watch some Hornet landing vidoes, right when they come out of break they tend to go gentle stick forward and trim a bit nose down and then right nose up again as they get on speed). Also, Hornet is really unique in DCS since it's the only jet with advanced FCS and separate flaps controls. In F16, you just lower the gear and the flaps are managed by FCS based on AoA. So there's really no point where you'd have this abrupt change in lift factor. Other planes with flap controls like F14 or L39 definitely ballon too but probably since you have direct control of the flight surfaces and the response to corrections is more immediate it doesn't seem to be so 'un-natural' to people.