Jump to content

DSplayer

ED Closed Beta Testers Team
 View Profile  See their activity

  • Posts

    1256

  • Joined

  • Last visited

 Content Type 

Everything posted by DSplayer

  1. DSplayer
    Is there a RAZBAM Official Roadmap?
  2. DSplayer
    I just always thought there was like an extended RIO startup that multicrew humans didnt need to do but only Jester needed to do. I guess I now know its a bug.
  3. DSplayer
    Making this since people wanted a separate forum post from the other one.
  4. DSplayer
    https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.7.14727/ You are indeed correct. October 20th.
  5. DSplayer
    Missiles do veer off when getting notched sometimes. It's more prevalent with older API missiles like the AIM-54. Nothing wrong besides the old API being the old API.
  6. DSplayer
    With 2.7.7, the JF-17's detection range has stayed relatively the same but holding and acquiring tracks beyond ~40nm in look up and maybe ~30nm in look down has significantly diminished compared to 2.7.6. Sometimes when you're trying to bug someone that has a track file built in TWS beyond ~40nm or in a look down, it doesn't stay bugged and you'll drop the track pretty quickly (even if the target is hot). I'm a bit curious to how accurate the radar is now compared to the real deal or if it even is supposed to act this way.
  7. DSplayer
    This is more of a DCS weapon issue instead of an AV-8B issue. I don't think RAZBAM can't really do anything.
  8. DSplayer
    Well now the 120’s magical powers of missing now will hit those playing the stable release.
  9. DSplayer
    If Jester is using up all my chaff, I would just make him give me control of chaff and then turn him off so he doesn’t deploy chaff. Not the best solution but it does work. Another way is to manually give yourself the keybinds for the RIO CM switches by editing the .lua files.
  10. DSplayer
    +1 I agree that we should have the ability to tell Jester to use a specified scan azimuth and bars for our own custom scan volumes. This, of course, is only good in RWS since TWS is fixed in the way it scans. In my opinion, however, I feel that the +/- 65 degree azimuth scan is kinda useless since it takes so long to sweep across the entire volume and in my experience, I feel that the RWS scan volume that Jester puts us in already, is pretty good (I think it's +/-40 degree 8 bar scan) but that's my experience of course.
  11. DSplayer
    Well the AWG-9 gets notched super easily in PD modes due to its wide doppler gate. It's the same reason why you get X'd out or lose lock when someone turns around or starts even getting close to flying perpendicular to you. For making Jester not changing STT modes when getting close, you can change it in the special settings.
  12. DSplayer
    Nope.
  13. DSplayer
    No. In all my experience within the new patch, both single player and multiplayer, it is NOT the ECMs on any aircraft causing the root problem. You can force AIM-120s to absolutely miss without much effort with the ECM turned off.
  14. DSplayer
    Just so you guys know what and why.
  15. DSplayer
    ED is planning on at least addressing the issue. Now it’s a matter of how they’re going to do it.
  16. DSplayer
    The AI F-14 currently doesn't employ the AIM-54 in the way that pilots do and therefore they're not a good indicator to the range of the 54 or how effective it is. It's going to be overhauled soon btw. For long range kills in real life, the figures you're going to generally get are from test figures since the figures for combat kills are basically all Iranian and its super hard to get any really credible info outside of the knowledge of the kill itself. An article on The Aviation Geek Club states that during a test firing of the AIM-54, it shot down a drone from a distance of 120 miles (Source). So I'd say if the AIM-54 was able to hit a target at that sort of distance, it sure could hit a fighter sized target at 40+ nm. In terms of DCS, the AIM-54 is really hampered by the old API and the ease that the AWG-9 can lose tracks (notching, etc.) but it can easily get long range kills if you really get high and launch at a high speed. During a comp match, I was able to score a ~72nm kill on another F-14 while I was RIOing. The range will probably be increased with the new API comes out and makes the missile more efficient with speed management. Just tell him to git gud.
  17. DSplayer
    Here's a track file of me just turning around and the missile doesn't even attempt to keep tracking me in both the OB and the Stable along with respective Tacviews. 120Trashed.trk 120TrashedbutStable.trk 120Trashed.acmi 120TrashedbutStabe.acmi
  18. DSplayer
    It's a pretty big problem tbh if that's the case. It makes the AIM-120 really hard to justify using when it just gets defeated so easily. It has definitely made an extreme change in how people play in the comp scene since you can just push super aggressively since you know their missile will not hit you. I would personally maybe like the changes to be rolled back or at least the issue be identified and then fixed in a hotfix but I don't know if that would happen.
  19. DSplayer
    Okay. Is there another factor that is causing missiles to simply get trashed after going cold or barely notching? There also seems to be a lack of reliability in otherwise high Pk shots in comparison to 2.7.6.
  20. DSplayer
    I've been having the exact same issues with the SD-10 and the AIM-120C with this new patch in terms of reliability. Plus they're acting the same with that Datalink/INS guidance thing. Maybe it's a placebo.
  21. DSplayer
    I would like Jester to immediately IFF targets that you have STT'd no matter what. The delay between him actually IFFing the target and marking it as hostile is long enough that in high intensity situations, friendly fire incidents can occur. I know that Jester verbally says if something is a friendly or hostile but it'll call out targets that are hostile as friendly sometimes if they're flying a Bluefor aircraft.
  22. DSplayer
    From what I could gather, it's the 120 API (AIM-120 + SD-10) that go changed with the new INS+Datalink guidance, notch filter "improvements", and the new physical seeker limitations. Notching just got worse with all these "improvements".
  23. DSplayer
    Jester spotting stuff is a bit inconsistent. Sometimes he's able to spot tanks and ground vehicles that are very hard to see but other times he can miss an entire moving oil tanker that is directly in the FOV. I would also like Jester to be able to use Point track instead of just Area track. Slight suggestion for the future: Jester LANTIRN A/A Mode. Would like to see it be used to spot aircraft and point track them.
  24. DSplayer
    Yeah it's absolutely insane. When I was reading up on the changes when they first got announced, I thought it would do the complete opposite and make the AIM-120 super hard to defeat. There is clearly something wrong that made the missile complete crap to use. Sparrows are more reliable than 120s atm.
  25. DSplayer
    In me and my squadron's current experience with the new patch, the new AIM-120 API (which should apply to all AIM-120 variants and the SD-10) made the missiles extremely easy to defeat. Is this intended or was this a unintended side effect of the new realistic modelling of the seeker head? Guidance on targets that are going cold or beaming have gone out the window and basically made this missile a medium range paperweight. What do you guys think?
×
×
  • Create New...