Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Kondor77

  1. This is a leftover from the original Stennis. After some trial and error you'll find out where the 'catapult hook' zone is for each cat. Some are bigger zones than others, which makes it all the more annoying.
  2. Ding ding ding, especially the last bit. If the AI could actually react when the missile goes active as opposed to 10nm away...maybe this will come with the further improvements to the AI.
  3. Fantastic news, thank you HB team. Can't wait! This is very fun as well when you combine it with the TCS and get 'accurate' designations. Really cool then to use for CCRP loft attacks.
  4. Yikes. Constant degradation? I've set up quick test missions to test all phoenixes in different scenarios. Just now I was able to hit a bomber at 100nm away - with the A mk47. My reading of this, is that you guys got way too comfortable with a Phoenix that was clearly over performing in it's first year+ of EA. And now when changes are made to correct it, because you are no longer able to splash a 29 from 60nm away while you're at 5,000 ft - it must be broken.
  5. In this specific case there are AI F-14s, but they are on the Iranian side, so no carrier interaction with them. Obviously on the Blue side there are, and my CTDs did happen to occur when I was on my way back to the carrier, but nowhere near (at least 50nm away) each time.
  6. To add a bit more to this... I haven't been having as frequent crashes as others, but that may be due to the server I played on mostly - Grayflag. This server was on the Syria map and additionally does not include AI F-14s. Just in the past few days, it's changed to a different scenario, in the PG map AND using AI F-14s. I've now had two separate CTDs while flying the F-14 and an hour plus of flight time. Reading between the lines of everyone else here, it's clearly something related to AI F-14s unfortunately, which usually manifests itself after a fair amount of flight time. The CTD can even be 'accelerated' by increased use of F2 view as well. So is this some sort of memory leak issue?
  7. Thank you. I noticed this as well yesterday and forgot about it already! Hopefully this gets fixed soon.
  8. Glad it's being addressed. So far it's been a fantastic release IMO. You can tell it's definitely a cockpit issue because even the handheld flashlight needs new batteries...
  9. I can report same issue, only have tried in Syria map. Some more details (In 2D btw): Syria Map MP Only occurred with the 60nm radar setting Anything lower and the FPS drop was gone I'll try and do more testing today especially on different maps. And then I'll try and attach a track if no one else beats me to it.
  10. If I remember correctly the first mission in the Operation Reforger campaign has you do several Case I traps. There are other aircraft going in and out of the pattern, as well as statics on deck. You should also be able to open the mission in the editor and make changes if you want, like add client slots, etc.
  11. Yes, I've run into the same issue when trying to drop two bombs onto one target (or two targets next to each other) on the same attack run. Even if I drop the first bomb at T-3 seconds, and the next bomb 3 seconds later, the first one guides and hits, the second just flies on as if the laser was never firing - which it obviously was as the first bomb guided and hit.
  12. Personally I'm all for the grey ones. AFAIK the only ones made so far are early 70s version, and another 80s color version. You catch a snippet of one in the OG Top Gun intro as it's launching.
  13. Any update to this problem? This still persists as of the latest OB.
  14. Am I in the minority that I actually prefer to fly the A over the B?
  15. I think you're on to something here. All my tests yesterday were with WT off in the mission editor. I just did some more CASE Is with WT on and the downdraft caught me totally off guard the first time. It's not so bad when you prepare for it, but it's definitely stronger than previous patch.
  16. 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.
  17. 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.
  18. 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.
  19. 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
  20. 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
  21. Left panel, RIO volume button is #1 https://www.heatblur.se/F-14Manual/cockpit.html#ics-control-panel
  22. 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.
  23. 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.
  24. 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.
  • Create New...