Jump to content

Hawkeye91

Members
  • Posts

    237
  • Joined

  • Last visited

Everything posted by Hawkeye91

  1. I've never tested solid numbers, but I almost never hold the track once the AI starts chaffing and the TWS will track the chaff and lose the target. I sometimes score hits but I believe its because of the missile going active even though it shouldn't after losing its target due to the API being on ED's side of the things.
  2. Yes this is exactly my issue. In the F14 TWS the AWG9 creates ghost tracks from AI popping chaff the second you fire in TWS. This renders TWS effectively useless against AI. There’s really no point in having TWS existing in the F14 as long as this behavior persists.
  3. READ THE ORIGINAL POST. I said to just have waypoints imported into the KNEEBOARD for manual human rio entry. NOT automatically uploaded into the plane like through a DTC.
  4. Im talking from the standpoint of being a RIO and being able to import the F10 map points to my knee board for entering them myself. I know Jester can do it from the radial menu. It’s for human RIOs
  5. Do you have an official source that there won’t be any glove vanes on the F14A? I did a forum search and this was all I could find mentioning them.
  6. This would be a cool, very nice QOL feature to have in the F14. As a RIO and trying to get up in a large dynamic mission is a bit more difficult and its a bit harder to get a whole flight of F14s on the same page. If we could import F10 map marks in a similar fashion to the viggen that would be huge. Even if its just into the kneeboard so the RIO can manually put it all in. Something like labeling the marks as WP1, WP2, WP3, IP, ect. It works extremely well in the Viggen, especially how you can have one person the mark points and have everyone use his, guaranteeing everyone is on the same page.
  7. Thanks, appreciate it. Wish heatblur's documentation was a bit more indepth on specific function. Its pretty vague on a lot of things.
  8. Can’t seem to find it in the manual anywhere, but is hostile area an actual “area” or just another fix? Also what is point to point? And how’s it used?
  9. I did some reading on an article about wheel landing techniques and it said that cause of the bounce in a wheel landing isn’t from bouncing off the gear but from the tail dropping down after the main gears hit hard causing a pitch up. This is what seems to happen with the wheel landings in the p47 currently.
  10. Watching some videos of the P47, I see almost all of the landings are wheel landings rather than 3 point. Does anyone have a good wheel landing technique to try?
  11. Some exhaust effects with heatblur distortion and exhaust smoke always makes a module really feel alive and not a static set piece for me. Just adds a nice touch. Loving the P47. Surprised by how much I like it actually. Well done ED. and maybe a flyable B17 some day, just saying. I bet it would blow WW2 DCS wide open!
  12. So dumb the AI does that because it spoofs the radar SOO bad now in TWS auto with ghost tracks.
  13. Not sure if this is intended, or just simplified AI but it is extremely irritating to launch an AIM54 in TWS 40 miles out only to have the missile trashed as soon as the missile leaves the rail because it starts popping chaff due to being clairvoyant. Is there any intention to fix this in the near future?
  14. My experience has been that TWS is bad for even non maneuver targets. Ghost tracks from track hold constantly fly off in random directions at Mach 3 against non-mauenevering, non-notching aircraft. I can’t get a single AIM 54 to work in TWS. Even in single player where rubber banding/desync doesn’t exist. Edit: I think I know why now, its DCS's clairvoyant AI that pop chaff the second the missile leaves the rail and creates a billion new contacts. The AI needs to be reworked so that they only pop the chaff when the missile goes actives because it shouldn't have a single clue when that missile leaves the rail.
  15. Hey guys, lately I've been unable to get any kills in the F14 because of the constant ghost trackfiles that happen in TWS Auto. This happens against non-notching, non-manuevering aircraft causing me to lose the TWS lock at least 2-3 times in BVR from a nose hot aspect within 50nm and I basically haven't been able to land a single AIM54 in TWS. It appears that when this happens, the ghost track flies away from the real track at almost double the speed on the TID. Its almost like the radar is making some false calculation that doesn't fit within its parameters to update the current real trackfile. Is this a known issue? Is it planned on being fixed the next update? Or is this working as intended and basically useless? I tried creating a track replay, but nothing happens in it due to DCS sync bugs with the F14. F14 TWS Auto Ghost Tracks.trk
      • 1
      • Like
  16. yup, that’s what I get for getting my hopes up.
  17. Hope I’ll be an A driver by tomorrow!
  18. Can you reproduce it and post a trackfile? I'll see if I can get it to happen. Are you level releasing or diving? Edit: Also do you mean GBU-12s? We don't have GBU-16s
  19. Interesting. Yeah definitely some kind of bug going on here then since there is really no way this should be working as intended. So far this has happened to me twice and I was able to replicate it the third time to create that track file.
  20. My exact setup was: Level CCIP Speed was about 0.90 Mach Single Ripple 6 20 foot spacing (10 is set by default)
  21. Pretty much the title. I'm attempting to drop MK82 Airs in level CCIP, Rippling 6 and it appears in the track that they are colliding after release and causing me to lose my plane. Here's a test track file of it happening. Maybe I'm doing something incorrect, but I'm not sure what it would be. TestTrk.trk
  22. You should sell them on Etsy. I'd buy one! lol
  23. How much did these cost you guys to make and is it hard to learn how?
×
×
  • Create New...