Jump to content

Hardcard

Members
  • Content Count

    991
  • Joined

  • Last visited

About Hardcard

  • Rank
    Member
  • Birthday 11/30/1984

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Frederf Thanks a lot for the detailed post. I think the responder works
  2. @Spins321 Ok, we're talking about the replacements at Kobuleti, right? I can confirm that AI replacements are removed after ~3 minutes, fortunately, this issue doesn't seem to affect static replacements. Until I find the culprit, I recommend that you set Replacement_Type to "Static". (Keep in mind that tomcat static models are bugged since the introduction of 2.7, this is a known DCS bug and has already been reported. It has nothing to do with SWAPR) Also, I noticed that your SWAPR script is using several client suffixes that aren't present in the mis
  3. @Willie Nelson I boresight them on the ground, using runway / taxiway signs (these are lockable objects in DCS). The procedure I follow is pretty much the same shown in the video that @Dawgboy linked, but, unlike the author of that video, I use lockable objects to boresight my mavs. He used a hornet's wheel, which the mavs couldn't lock on to properly, I wouldn't have trusted that alignment. In any case, I double check the alignment once I'm the air, using friendly ground units around the airbase. Small corrections are needed sometimes, but nothing major.
  4. Bypass is definitely the way to go if you want full control. I also can't stand wasteful release of CM, which is why I use bypass exclusively. Just set the mode to BYP and have both chaff and flare switches up, that'll dispense a single chaff & flare per command. If you want chaff only, set the FL switch off (down). If you want flare only, set the CH switch off (down). Disregard betty's "chaff, flare" callouts, she'll say that even when you're only deploying one type of CM. I have CH and FL switches + CMS all assigned
  5. Watch the video again (or better yet, replay the track. It'll allow you to see the tiny radar queues on DDI). First two amraams got the LOST queue both at launch and during midcourse guidance (watch the radar page on the right DDI, at the bottom of the STT line you'll see "LOST" flashing briefly during midcourse guidance). I'm not gonna say that the radar isn't bugged (it's the hornet, after all ), just considering alternatives. Also, remember that whatever the hornet was capable of doing before 2.7, doesn't necessarily apply now, with the new radar implementation, so I woul
  6. I don't know how realistic that simulator is, but sure, that kind of approach will definitely get you killed in DCS
  7. @jwflowersii Your third missile tracked the bandit and the first two didn't, that's the fact we have on the table right now. The explanation must be found in the variables that changed between launches. Could be max range violation, loss of DL guidance before pitbull or something else.
  8. @jwflowersii After watching your track, looks like the issue might be related to the fact that your first two amraams were fired beyond the calculated max range. I don't know whether this is expected behavior, but I do know that STT locking a bandit at 30nm isn't a good idea (unless he's chasing a friendly and you want to distract him). Next time wait until the bandit gets within max range, at least, and don't use STT lock from so far away. (Hell, with good DL picture, I wouldn't even turn on the radar until the bandit were within 40nm, or within 10nm in the absence of
  9. Yup, post the tacview track file, so people can see what your missiles actually did. I'm betting that all your amraams were tracking, problem is that you launched them from way too far. Amraams aren't phoenixes, don't expect crazy range from them.
  10. @Willie Nelson Yup, you're not alone. Auto handoff won't give you a valid mav lock most of the time. I force correlate H and K mavericks, using manual handoff and area mode, but in order for this to work well, mavericks need to be perfectly boresighted.
  11. @Spins321 Thanks. Could you also attach the dcs.log that was running when you encountered the issue? Also, if you were running the mission in MP, I'll need the server hook as well. Additionally, if the mission is using mods, please remove any modded units/objects, so I'm not required to install them.
  12. If those results are screenshots from the manual, I've already seen those. What have you found?
  13. @Willbassen SA-10 sites don't have that many missiles available, I suggest that you first drain the site of missiles and then attack with HARMs, so they can't be intercepted. Draining the SA-10 (or any other SAM site) quickly is as simple as finding a hill / mountain (good enough for masking) within its umbrella. Pop up above cover, let the SAM site lock on you and fire, then dive behind cover again, instantly defeating the incoming missiles, rinse and repeat. It shouldn't take you more than 5 minutes of this to drain any SAM site in the game. You can also live dange
  14. @Mangrove Jack What are you using those flags for? What's the goal you're trying to achieve?
  15. I've tried Google, forum search, checked both the manual and Chuck's guide, but I haven't found any info about the Mi-8's IFF responder. Does anyone know if it actually works? Does it require setting up? If so, how? I'm asking because Mi-8s don't seem to respond to IFF interrogations (at least when vipers perform them... I'm not sure if it's a viper bug, an mi-8 bug or something else)
×
×
  • Create New...