DoorMouse

Super fun as always, I liked the added depth of having a ground objective, rather than 1985-2 that was just an all out brawl. Looking forward to future scenarios!

Ive had more luck with a human rio- IT may be that the MLC issue has broken Jester's brain and hes dropping tracks, not locking stt, and missiles are trashing because of it? Im going to test some TWS shots this weekend with a human, but as of right now its almost entirely broken in multiplayer and you have to STT ACM all your phoenixes to get any hits. I used to be able to get 60-70 mile shots from 30k fairly reliably (under correct conditions, non maneuvering climbing target, 1000knots closure, 10kft-20kft altitude). I have not seen a single hit, even if somehow mercifully the track lasts long enough to pitbull.

So the A has a lot of modern features missing, and some development problems. Two big ones being: The TF30 engines were a horrible mismatch for the platform. They were not intended to be used in the way the F-14 could push them and their signature issue was that they would compressor stall at high AOA... like when you are maybe a bit above on-speed AOA for a carrier landing. Not ideal. The RWR was also a big difference. The A model's radar warning system was particularly lacking, and there are stories of how the crews would put consumer grade police radar detectors in the cockpit on the left and right side to detect incoming missiles.

SO i just did a super un-scientific test and made a singleplayer mission. Everything seemed to work, and phoenixes actually goddamn tracked their targets, the radar didnt drop locks all over the place. I have a feeling it has to do with multiplayer with many players/ground units/stuff going on causing issues with the radar when it tries to reconcile all the players positions.

I'd really love to hear a reply on this. The 14 has become incredibly frustrating to fly in multiplayer since the last patch, and supposedly no changes were made. I assume that means A) ED changed something that screwed up the Radar and therefore Jester's logic is messed up. And/Or B) ED changed the guidance of missiles again without informing anyone, screwing up the AIM 7 and the AIM 54 since they are both SAHR missiles.

Do you like a difficult challenge? Fly the B Do you enjoy randomly getting stabbed? Fly the A

if it went for chaff then maybe it just missed. If you have one that STT tracked the whole way in, had energy, and just plain didnt turn while you still had lock - That could be something?

Go to Advanced Options, Look in Additional Options. Click Manage Attachments From Manage Attachements pick one of the 3 slots to "Choose File" Once you choose it, hit UPLOAD Once it uploads successfully close the window. Id also take a look at their guide here, they get a million bug requests and this will help them sort things: https://forums.eagle.ru/showthread.php?t=253852

Please try to reproduce this and submit a full bug report the way they want us to if possible. The more evidence of this, maybe they will take a look. Heatblur has said they have not changed anything with regard to the radar. Jester's behavior is very different, but that is probably a symptom of whatever the core issue is. Seeing as how the Aim7s are having issues maneuvering. The Phoenix TWS shots seem to also not be maneuvering/hitting... I suspect ED changed something and didnt document it, or there are multiple issues. But please post track files to this thread, or the other threads so we get them concrete evidence. Right now the F-14 is pretty broken.

Go to your Saved Games folder and look for DCS/Tracks, youll probably have a ton, you'll need to find the correct one. Sort by date.

Ok more examples of weird jester/Radar behavior. The track is full of failed TWS shots, but the last few sortes out of Beslan (Gelendzik spawned aircraft though) are where these videos came from. - Jester goes RWS the moment a TWS shot is fired. Two STT ACM Mode phoenixes connect afterwards (that seems to be the only way that the Aim54 connects in multiplayer now) -Jester absolutely refuses to stay in TWS... but you can hear him clicking madly and momentarily trying to change it. Once he sorts himself out, notice that he goes to TWS AUTO, while tracking no targets, no missiles, no hold tracks..... This one is absolutely proof positive of.... whatever this is. It happens frequently. Interestingly, It happens about 2 minutes after the last shot connected so I wonder if its trying to "hold track" but something is broken? (Edit- whoops, I should consolidate this into the other thread with the stuck RWS, and not the stuck TWS-A. I'll clean this up in the morning and post the other tracks in the appropriate thread) DDCS-Modern-CA-3.50_Spring_6-20200729-220430.trk

track - attached In this: Bug 1: Jester is stuck in TWS Auto while cold/no targets TWS locked (I suspect jester has the Track Hold on, but is bugged in that its somehow holding a track even when you go cold and are no longer pointed at the missile/target - I can test with a human rio for reproducability) Bug 2: Jester has a TWS track 20 miles out and loses it upon being asked to STT Bug 3: Radar does not display a Time to Impact for a TWS Fire/Lock This one seems to be reproducible in that your first shot always seems to work fine, but if you lose the track by gimbal limits (IE turning cold) it seems to stick in TWS auto, and subsequent shots do not show a Time to Impact. These happen about half way through, first flight out of Gelendzhik Bug 4 (Maybe?): the number of TWS kills has gone down significantly, near to Zero, since the last patch. I've got an embarrassingly large number of hours in the tomcat... something changed. I took a lot of TWS shots at various ranges in this. (only one connected on a non-maneuvering target 40nm out) Can I reproduce it 100%: Yes/no- It happens frequently and on a regular basis through normal gameplay. I have not found a specific setup that makes this happen. How to reproduce/ description: See Track/video clip Open Beta - 2.5.6.52437 System Specs: CPU 5930k Clocked at 4.4ghz GPU: MSI 2080ti 64gb Ram SSD OS: Win10 Peripherals: Joystick: TM Warthog Throttle: TM Warthog Pedals: MFG Crosswind Others: Headtracker: VIVE VR Mods:2.5.6 IC pass Shader Mod DDCS-Modern-CA-3.50_Spring_1-20200728-215311.trk

The plastic guard is already a bindable button. Just make the pull tab a button/toggle as well. There are multiple reasons to be able to do this- It would be great in VR for carrier operations. And it was an "off the book" tactic to sweep the wings forward before merges, or at high altitude where the air is lighter.

track attached - this moment happens at about ~15 minutes? First sorte. There are also a slew of other jester oddities like not having TWS Time to Target on fired missiles. etc. Im also working on clipping one of multiple examples of Jester being stuck in TWS Auto with no locks, Scanning into oblivion and nothing - and refuses to reset to TWS Manual. Bug 1: Jester switches to RWS immediately after firing a phoenix on a TWS Track Bug 2: Jester does the above even though you have just commanded him to be only in TWS Can I reproduce it 100%: Yes/no- It happens frequently and on a regular basis through normal gameplay. I have not found a specific setup that makes this happen. How to reproduce/ description: See Track/video clip Open Beta - 2.5.6.52437 System Specs: CPU 5930k Clocked at 4.4ghz GPU: MSI 2080ti 64gb Ram SSD OS: Win10 Peripherals: Joystick: TM Warthog Throttle: TM Warthog Pedals: MFG Crosswind Others: Headtracker: VIVE VR Mods:2.5.6 IC pass Shader Mod --- EXAMPLE 2: - Jester goes RWS the moment a TWS shot is fired. Two STT ACM Mode phoenixes connect afterwards (that seems to be the only way that the Aim54 connects in multiplayer now) Track attached in other thread (as it has examples of the stuck radar mode too) https://forums.eagle.ru/showthread.php?t=282072 DDCS-Modern-CA-3.50_Spring_3-20200726-220348.trk

is this new? This is sort of my baseline mission to see if ninja undocumented changes have been made, or just have a consistent experience to test the changes. The aim 7 used to work just fine.

Flood track attached Sparrows broken FLOOD 1 .trk

Setup: Persian Gulf Lion and Sun (BFM) Fire sparrows around 4nm They either seem to do some weird thing where they don't maneuver and then try to loop on top of the target, or completely veer off course. Flood is also ineffective. First track shows a normally high PK dogfight launch where the aim7 seems to just fly off the rail like a ZUNI. Sparrows broken 1 .trk Sparrows broken 2 .trk Sparrows broken 3 .trk

This is 100% not the behavior in multiplayer right now. I have a million tracks of this happening and can reproduce it easily. Ill make one ASAP Jester stays in TWS-A even with no missiles in the air and you cannot get him out of it.

Oh thank god. I feel like im taking crazy pills right now.

Anecdotally I've also seen a major problem with the AWG-9 performance in multiplayer. Routinely id have GCI having me point directly at a hot bandit, id see its contrails, and jester is unable to find it. Jester also gets stuck in TWS - AUTO. So you cant tell him to scan an area, hes stuck scanning nothing in TWS Auto I also don't think ive had a single TWS kill in days, but STT seems to work just fine. Ive seen TWS shots pourpose coming off the rails like they are losing the track and getting it back, even though the TID doesnt show that and FINALLY He also has several times gotten a TWS Manual lock, and then switched to RWS right when I shoot. I have a feeling there is some Multiplayer sync/lag issue that is messing TWS shots up?

pretty much exclusively Multiplayer. Its because as other people have pointed out, if you give jester more than one thing to do he breaks things.

lol yes that did happen. But didnt mention it here. Jester sets the radar to "Standby" and if a human rio joins and expects the radar to be "on" there could be issues. But thats neither here nor there.

I think this is the same issue. If you give jester multiple waypoints he A)messes up your current location B) introduces a ridiculous drift in the INS somehow. I can reproduce this on multiplayer nearly 100% of the time.

I've been having this or a similar issue as well. Unless I tell jester precisely where to tws-m, almost no contacts ever show up even when at a perfect co-alt 40nm orientation. Jester also seems to have huge issues with locking things up that are above the aircraft, which I've noticed for a while, but seems to have become worse. Additionally, I've noticed that even with the tws lock (1∆1) iconography half my Phoenixes in tws just fly off into space (jester and multiple human Rios) Something changed with the radar.... I've got more hours than I care to admit In this thing and the last update drastically has changed my normal routine.

Please see video this time- since I seem to be the only one experiencing this. 1) waited for full alignment and weapons on rails 2) Entered Waypoints 1 2 3 and HB in F10 map 3) used jester wheel to queue up entry of waypoints 4) Jester places HB waypoint ~40nm from aircraft 'current location' Result - Alignment is useless, and you cant even tell jester to Landmark Align to the HB coordinates he set. PLEEEASE tell me what I did wrong, or let me know this is still a known issue.