Kondor77

After several traps I can say that to me it doesn't feel as being 'doubled'. If anything it feels much milder than before. I agree, for us it's impossible to actually quantify it. I would image Devs have access to tools that they can see exactly what's happening with the effect(s) in real time.

Good question. Currently away from home so I can't test now, but I am curious if the new 'burble' implementation was just ED basically doing the same thing as HB with the 14. Adding the effect to the aircraft itself, rather than to a specific carrier. Since the 14 is affected by the burble on all carriers, not just SC.

FYI, this has been a bug for quite a long time in the 14. I haven't tested it every single patch release, as I found out early on that having Jester input multiple F10 waypoints in quick succession would lead to some waypoints being incorrect and nowhere near where it's supposed to be.

Didn't take pictures, but I tested it out last night and it does work. Unfortunately it's not as 'clear' as say a Jeff or Apache given what we're working with. It didn't look much different from 26,000 ft (which I wouldn't expect it to). But down in the low teens you can clearly see the difference. This is a good representation of what it looked like for me. The 'default' looks OK, I'm sure with a human RIO able to further tune it in the back it would look better than the default. https://imgur.com/a/fM2u6dT

SC took a major backseat to the rest of other ED stuff. Frankly, if the long promised new SC features don't bring along with it a massive list of bug fixes, I'll just keep using the Forrestal instead. We might need to send the guys some Ritalin to help with the Early Access ADD

Left panel, RIO volume button is #1 https://www.heatblur.se/F-14Manual/cockpit.html#ics-control-panel

Yes, it absolutely does. Especially if say, the guys you TWS launch at ~40nm are at 30,000 ft (you have TID range to 100nm) then another group at 5,000 ft shows up at 90nm, it will likely mess up the track of the first group. Always always always keep the TID range at the shortest increment possible when launching in TWS.

Absolutely it is. If you notice, I believe all the instant action quick BFM missions included with the module, start with roll SAS already off.

Definitely worse performance than previous patch. Not just related to our beloved 14. 9600K with a 2070, so not a spectacular rig but good enough to run 1440 at 60-100 fps depending on the situation. But I can tell flying over cities especially that frames have decreased from the previous patch.

Not to point fingers - b/c at the end of the day it's no one's fault really. ED's release of the SC undoubtedly changed the outlook and purpose of the Forrestal. Let's not forget that HB was well into essentially giving us a SC-like experience, but because of SC things changed. I hope that at some point in the future it will have the ability to use SC features like the deck crew and the burble effect, etc. It would be a real shame to have a proper boat for A6, A7 and F14A, but unfortunately stripped of features that are available elsewhere. Hoping for the best...

Happy to hear that was it! I think I remember this being an issue even from very early on in EA, to the point that I've been trained as the pilot, not to overwork him too much

This bug has cropped up every now and then - and in different ways. I think the last time using Jester to input waypoints from F10 map would hard crash the game. I know other versions of this bug Jester would be 'prone to input errors' if you gave him multiple f10 waypoints to enter all at once. Have you tried just giving him one waypoint at a time? Are you having this problem across multiple maps?

I haven't tested this in the newest patch, but from experience you have to be pretty close. I don't have a hard number memorized, but from experience, I think the slant range is about ~10nm? Maybe a bit more or less? You know you're in range once the diamond stops blinking while moving it with VSL LO/HI. I use it to drop GBUs on lazed targets while staying above AA/manpads.

For #1 (I assume), at a minimum we (who own the SC) should be able to place the SC statics on the Forestall. Currently we can place them on the Stennis and on ground AFs. So we'll at least have people/cranes on the deck. They won't be moving or doing anything like they would on the SC though. Hopefully this will serve as a good interim solution until it gets developed further. As for #4, I assume if it's done as a Stennis clone that since it probably uses the same framework, that the AI should have no issues with it?

On your last point about AI omniscience, that was actually fixed last patch. They now no longer evade/chaff until the missile actually goes active (I'm speaking strictly about TWS shots). I'm consistently making hits on AI fighters at 50+nm when firing in TWS.

Interesting, it is the same account and I can play the campaign in SP. Maybe it takes some time for it to update server-side? Gracias por la respuesta

Hi all, I'm trying to load these missions into my server box in order to help with FPS (I don't want to reduce the # of planes using F10 menu - and the server box helps a ton in this regard). But when trying to load the missions I get this error in the dcs log file. 2021-05-21 16:41:37.095 INFO WORLDGENERAL: loading mission from: "C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 01.miz" 2021-05-21 16:41:37.739 INFO DCS: use_xRay: yes 2021-05-21 16:41:37.739 INFO DCS: netfm_enable_coeff_switching: yes 2021-05-21 16:41:37.833 ERROR Dispatcher: Mission Load Error: Mission is not authorized. I get the same error even trying to load even one of the 'Coop' missions: 2021-05-21 16:41:43.208 INFO Dispatcher: loadMission C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 09_COOP.miz 2021-05-21 16:41:43.208 INFO WORLDGENERAL: loading mission from: "C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 09_COOP.miz" 2021-05-21 16:41:43.989 INFO DCS: use_xRay: yes 2021-05-21 16:41:43.989 INFO DCS: netfm_enable_coeff_switching: yes 2021-05-21 16:41:44.075 ERROR Dispatcher: Mission Load Error: Mission is not authorized. Thanks in advance!

For the time being, a way around this in MP is to input the coordinates for the waypoints manually using the Jester wheel. It's obviously not as quick or easy as F10 markers - but it works.

I posted about this in the bug subforum and attached my log file. I tested it in SP and it works, but as soon as you try it in MP it CTDs. Manually entering waypoints with Jester wheel works in both SP and MP.

As the title suggests, game hard CTDs when using the Jester option to add a waypoint from F10 map. As for my tests, this only occurs in MP. dcs.log dcs.20210414-183148.dmp dcs.20210414-183148.crash

Thanks, there are other tracks as well posted here:

I can confirm I ran into this bug as well yesterday. I'll see if I can upload my .trk file. This actually is one of the Reforger 'Iron Heel' campaign missions from HB, running off my dedicated server with me and my human RIO as the only clients using the SC. I got the same 'Flight is delayed' message, spawned in soon afterwards and immediately noticed the plane felt like it was stuck in mud, needing way more throttle than normal to taxi. Cat launch and trapping all exhibited the same effects of having this ghost weight onboard. **EDIT**: Track file download link: https://drive.google.com/file/d/1nrG3hSZvyx19XATlYGXUd1-ZX0wNQykJ/view?usp=sharing

It absolutely has to do with head position at launch, which is a really cool touch.

Looks like sparrows also got borked in the update. I'm having the same issues posted here - with all sparrow variants. AIM-7MH Issues - Bugs and Problems - ED Forums (eagle.ru)

Thank you for the update Cobra. When it comes to the 'General Jester TWS-A issues specifically to desync/track loss issues, I'm not sure if others have mentioned elsewhere, but I think I've found the culprit. It's the Datalink. I've only had enough free time to test it myself about half a dozen times offline and online. If I make sure my Datalink is set to anything that's NOT the AWACs, It eliminates the issues with the desync/ghost contact which lead to track loss. Hope this helps, and can't wait to wrestle with the A.