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.

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.

Really struggling with transition to landing config You need to understand 2 important things. 1) Your stick doesn't control you flight control surfaces. It doesn't do pitch up/pitch down. It tells the FCS what you want and the FCS moves the flight control surfaces accordingly. 2) Your FCS has 2 different ways how to interpret what you want a) in clean config the stick forward/aft tells the FCS what amount of G you want (and so does trim) b) in landing configuration, the stick tells the FCS what amount of AoA you want (and so does trim) So stop thinking about this in terms of pitch / speed. It's AoA from now on. Let's go over what happens during the transition into landing config. You fly level, clean, at 250kts. Your AoA will be about 4 degs and with stick neutral your FCS is maintaining happily 1G. As soon as you lower the gear and flaps, your FCS switches the modes and starts to worry only about AoA. Now, remember, it's current settings is AoA 4 degs. It's trimmed to 4 degs. But since you lowered your flaps, your wing is now generating much more lift and therefore, if the FCS want's to maintain 4 degs AoA it needs to pitch up. That's where the ballooning comes from. But, you can use your stick to tell the FCS what kind of AoA you want, so you need to put stick forward to tell the FCS - yeah, I know the trim is set to 4 degs, but I would very much prefer if you maintain about 0 degs AoA (that's level flight with flaps down at 250kts). Therefore, you need to use stick forward inputs to tell the FCS to decrease the commanded AoA. You're basically overriding your trim settings. Since you set your engines on idle, the plane starts to slow down. As it slows down, it needs more AoA to maintain the lift. As a result, as you slow down, you will need to ease off the stick forward inputs otherwise you'd start to descent. So just ease on the stick to let the jet slow down while maintaining level flight. At some point, as you slow down further, you will come to stick neutral position. This is a point where your trim settings match your stick command in terms of AoA. As you ease of to neutral position, you slowly start to throttle up to stop the deceleration. If you time it well (and you just need to do it for couple of times to get the right feeling) you will end up with stick neutral, throttle somewhere above idle, level flight, AoA about 4 degs. From now on the jet will maintain this flight. If you want to descent, you decrease the throttle, as a result, to maintain stable AoA the FCS will command pitch down movement and you will descent. If you increase your throttle, in order to maintain stable AoA the FCS will pitch up, arresting the descent. Next step is to trim to on speed trim settings - 8.1 degs. So as you trim up, you will notice that the jet will slow down because FCS is pitching up in order to maintain commanded AoA. You need to throttle up to keep the plane flying level. Ultimately you end up on 8.1 degs, on speed, level flight. Here's some exercise for you - forget about the boat start with 1) flying straight and level, at 250kts, just lower both flaps and gear and use your stick inputs and throttle to stabilize on level flight. Forget about trim. 2) once you master that, try the same, but using the trim to get on speed. You can start with #1 and then just trim after you stabilize, then try to make it more fluent so that you end up with being able to do in one fluent take. 3) Start to do it in a break 4) Once you master all of that and feel comfortable, you can add the boat and start to try the landings.

Hey, I was hoping you can help me with following issue. I have 3 Cougar MFDs that are set up like this Left- in game ID F16 MFD 1 {9888B.... Center - in game ID F16 MFD 1 {019322.. Right - in game ID F16 MFD 2 {6F0B... I don't think it's necessary to copy entire device ID, it's just to show that while they're called same, they have different ID. So the problem. Some of the buttons on Left MFD stop registering in game for some planes. They still work perfectly in F18, they still register if I try to bind them for any other plane, but, when I press them in game they don't work. I'm 100% sure it's not hardware issue. They work ok for the F18 after all. Here's what I've discovered so far All works well: F18, M2K JOY_BTN 8, 9, 10, 21, 22, 27, 28 (that's three bottom buttons in right vertical, SYM rocker switch, GAIN rocker switch) won't register in game F14, F16, JF 17 It used to work ok, but about 2 months ago, I suspect after a patch, it stopped working. Unfortunately, I can't tell which patch broke it. I have no idea how to debug this. I suspect it's some sort of conflict between Left and Center MFDs but beyond that, any help would be appreciated Thanks! earnil

My setup on CMS warthog switch is like this: CMS forward - start program CMS aft - wall switch CMS left - select prog 1 CMS right - select prog 2 Prog 1 is chaff only, prog 2 is chaff + flare, wall program is panic. This way you can have Progs 1 / 2 for your normal stuff and wall for dogfight or MANPADs evasion.

Hi Heatblur! I think there's a problem with setting up Home Base waypoint via Jester via F10 map. How to recreate: 1) Cold startup 2) No predefined waypoints 3) use F10 map to create waypoint 4) use Jester to set that mark as Home Base waypoint. As shown from attached pictures, while Tunb Island, which is the intended Home Base is bearing 228 degs, HSI shows something over 130 degs. Range is correct. Attached is track file and the pictures. While I didn't do it in the track attached, same thing happens if I use manual input and just input the coordinates directly. Also, WP1 and WP2 are being shown correctly, with correct bearing and range. I think there's same issue with Defense point WP, but I haven't tested it extensively. F14 INS Test 2.trk

I highly appreciate the work you guys are doing on the Viper but please, please, please can someone look into countermeasure rearm. It's such a low hanging fruit! It's massive quality of life improvement for anyone who flies Viper in MP and on the other hand such an incredible annoyance. Just imagine, you have a great sortie on a server like Blueflag, the battle is in full swing, you land for quick rearm / refuel on newly captured enemy field but - eeeee - you used countermeasures so now you have to despawn, respawn on home base far from action, go through INS alignment again... Just because two numbers don't update correctly. I have no idea what kind of technical challenge it is to fix it, but at least for me, who plays almost exclusively MP, it makes flying Viper supremely frustrating now. Otherwise, great job though, appreciate all other fixes!

Just here to add to popular demand - +1 to eastern planes!

Even after this update, you can't rearm countermeasures at all. How to reproduce: 1) take off 2) use any countermeasures 3) land 4) use F8 to rearm you're stuck with what you have (or rather don't have). In MP, that means that every time you use CMs you need to take new airframe. Almost as annoying as repeated bugreports on same issue.

Sorry for the duplication! Maybe as suggestion it would be worthwhile to add something like "things you report but are WIP" thread next to or into 'Known bugs' thread. I checked entire bug report section, I checked planned systems section, I checked known bugs section and since I didn't find it anywhere there, I made a report.