Jump to content

Cpt. Weber

Members
  • Posts

    80
  • Joined

  • Last visited

Everything posted by Cpt. Weber

  1. Thanks @Victory205 as always for your guidance. I'd have a question regarding the DLC functioning, as described in NATOPS F-14B 8.5.4., it says in the note: "Automatic pitch compensation for DLC activation is optimized for approach angle-of-attack speeds. Activation of DLC at higher airspeeds will result in inducing noticeable changes in pitch attitude." Does that mean, that this pitching up we experience right now should normally not occur and will be removed in the future hot-fix(es) during cleanup or we should get used to it?
  2. So let's keep our hopes high and visible till the end. Phantom ftw
  3. Any version of the Phantom would be a long awaited dream come true for me.
  4. The logic of the NWS switching off has changed, please refer the changelog.
  5. So again, coming back to my point, the essential info about how they should work (loft/no loft) is here, in yet another thread. Theoretically, for someone who is just getting into the Tomcat, it would be hard to distinguish if the behaviour is intended or bugged. Like in the case of lofting M-type.
  6. I'm slowly thinking it would be nice to have a sticky thread about the functionalities of different Sparrow types in different radar modes. It gets gradually more confusing as the manual contains only some information in that regard and the rest (usually even more detailed info) is just spread around the forums in the comments in different threads .
  7. Thanks for sharing, it's a really helpful video. Nice reference for my BVR routines and exercises... ...if only the Sparrows we have at our disposal right now wanted to cooperate at all...
  8. A truly saddening news Blue skies & RIP.
  9. Would be a welcome ressurection indeed!
  10. That is true, the interval I used may be forbidden somewhere, I did not check the Natops for that. I just found it strange, the bombs seemed to drift towards each other. I menaged to replicate this several times in a row yesterday. Today tried twice and they didn't blow each other up, just came really close. The problem doesn't seem to concern the Mk-83 though as they are smaller.
  11. Here's another perspective, right before the explosion.
  12. With all due respect, you don't seem to understand, it concerns the collision of the bombs with each other, midair, not with the jet. I assumed a correct bombing run profile. Here's the moment of explosion.
  13. I'm not sure if it was reported already for the F-14. How to recreate: Pick 4 Mk-84, Single, N/T, set ripple quantity 2, ripple distance 10m, CCIP, around 20-25 degrees dive. Pickle twice in around 1 second interval. Blow your ass off. (Reference mission, edited (exchanged bombs for Mk-84) instant mission with bombing the island on Marianas map.
  14. And less range compared to the second A, aaand going crazy up close more often then not. Haven't scored a kill with the C in recent couple of sorties, SP, ranges between 30 and 40 miles. But even at close range it seems quite unreliable right now.
  15. Hah, I thought it's on purpose, to make sure the F-18s will do the job.
  16. In my scenario Elvis also couldn't refuel, as the tanker interrupted my refueling without warning, beside reaching a waypoint and headed back home. Because of that, Elvis was "unable". Is it possible the mission took me too long? I wasn't flying fast in the CAP station, chilling. Maybe the tanker runs out of the track?
  17. Thank you for your answer, Naquaii, I was just wondering about the very same issue in recent days, as the results of my Phoenix shots, especially on lower altitutdes with lost tracks were very inconsistent. I wish I knew it earlier (how this mechanics works) as it would have spared me a lot of frustration.
  18. Most probably that's the reason why. I had the same issue with the mission, the faster you go, the less chance to see them, they just disappear. It gave the mission a pretty depressive flair, I couldn't see and target the first guy going for the AWACS because he was too fast. Until I got in range and slowed down enough to see him, it was much too late. It also kinda borked the next mission for me as well...
  19. That's a wonderful patch HB! Thank you guys!
  20. I also could hear it from the beginning, the strange whining in the background, the same as in the Viggen - I assumed it's a placeholder for the proper engine sounds, but they stayed much longer than expected.
  21. Sure, but I'm really not expecting the single F-14 to be a murder machine, nor find this mission this thread refers to hard to do, tbh. I'm here only, because I don't like how the new changes of the AI behaviour are shaping. It seems much like faking the difficulty by making AI omniscent. I would also argue, the immidiate usage of chaff can also fiddle with the modeling of the missiles itself, where ED now has to take the strange behaviour they created themselves into account while modeling the chaff resistance of the Fox-3s. I have doubts about this kind of realism.
  22. Amazing stuff, thank you for the hard work and taking the time to explain the workflow here!
  23. The problem is, how does the AI MiG-23 or 29 or Su-27, with it's relatively limited RWR, know, it's being painted by an F-14 and not something else? This omniscient AI solution to try to simulate expected behaviour is not a good solution.
  24. I just got this bug after 5th (without intro - the 4th) mission: But I have the code, next target and everything. May I skip the mission using the logbook.lua in the C:\Users\[YOUR NAME]\Saved Games\DCS.openbeta\MissionEditor and continue to the next one using the generated code or do I have to re-fly it? Will it brake anything? Thanks for help! Edit: (The mission I finished was "Operation Pontus Stage 2.3_Clear.miz"). I also saved the result of this mission so I can write it in the logbook.
  25. It's totally not the same - if you assume and you're wrong, you're only making your position worse, by giving the opponent a window of oppportunity to push closer as HE knows, that he didn't fire. And he did not waste any ordnance. The AI knows when you launch, starts immidiate chaff employment (?!) and goes evasive. He acts directly agaist your missile and only when you launch. He will not make a mistake in evading a supposed launch where there was none. Thus he always reacts 100% correctly to the situation, where his knowledge should be limited. In this case, TWS shots totally lose all their tactical sense, whatsoever.
×
×
  • Create New...