Jump to content

Snoopy

Members
  • Posts

    6773
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Snoopy

  1. Wouldn’t call it a bug so much as leftover from when the A-10C was it’s own product. would be nice it it was updated to mirror more recent modules though.
  2. The ED model of the RSC has been there since the II was released
  3. We "know" from the 3d model that we are getting the ARC-210 radio set control (rsc) panel in the cockpit. This is what I'm hoping the ARC-210 also includes: 1. MFCD Comm page / ARC-210 Presets pages 2. MFCD DTS Upload "LOAD ARC-210" button (although honestly without a mission planner/DTC builder this isn't useful) 3. Control of the ARC-210 via the UFC 4. HUD displays ARC-210 configuration/status
  4. Yes but it does have an ARC-210 PRESETS page that we hopefully will get.
  5. UFC integration ties it to the HUD
  6. During the day you don’t need to adjust any switches to see the repeater or clock at full brightness.
  7. Actually the default color in DCS is almost a perfect match to the real color on the jet.
  8. So same exact response paying costumers have heard for over a year with ZERO actual updates or information.
  9. So based on your responses all we are getting for the A-10C 2 is the radio and maybe some bug fixes? is ALQ-184 long and additional TAD symbology not gonna happen?
  10. We’ve been hearing this for a year and at this point it’s a blatant slap in the face to paying customers. Basically the A-10C has zero priority and we shouldn’t expect anything anytime soon.
  11. I have not but it’s in my “to do” list
  12. Appears to be the case but I’m sure we’ll eventually get the same post we’ve gotten for over a year… ”when the programmer has time they’ll get back to the A-10C v2” ignoring it was released over 1.5 years ago with little updates or bug fixes and zero additions of promised features such as the ARC-210 or long 184.
  13. Year or so ago ED said they were going to add some symbology/features to the TAD as part of the A-10ac v2 upgrade but it’s been super quiet on the subject (and any other bug fixes or planned features such as the long 184, ARC-210, missing HMCS symbology (I.e. what shows for AI Hornets and Vipers isn’t the same as clients) and based on comments from Nineline I don’t expect any of the actual missing HMCS symbology to be added).
  14. Even on the real jets nose illumination on bright isn’t that bright and wearing NVGs for night air refueling is the norm now days not the exception.
  15. That was for A models not C models and for the Mav screen.
  16. Classified isn’t an actually “informational category” in the DoD anymore. Could spend hours explaining export controls and DoD information classification but everyone would fall asleep before they reached the halfway point. lol
  17. Classified isn’t the correct terminology but everything, including what we have now, is secret. It’s just a matter of what ED has been allowed to add. I’m overly critical of ED at times but understand these limitations. What frustrates me is when communication isn’t clear or it is ambiguous. That being said I for sure can’t understand why something like threat rings are okay in one module but not another. Only thing I can think is the A-10C (v1 and v2) are direct results of DoD contracts which likely have clauses specific to the consumer product where as the Hornet, Viper, and Apache (to my knowledge anyways) are not.
  18. Snoopy

    ALQ-184 Long

    I’ve only seen the ALQ-184 long on A-10s at Moody and Whiteman over the last 10 plus years. Not exactly sure when we transitioned from the short pod though. We carried the short version at Moody and Osan in the mid/late 90s
  19. ha ha ha okay if you say so. So it’s okay they have one for the Hornet, Viper, and Apache but not for the A-10C v2…and the A-10C v2 hasn’t had a meaningful update or bug fixes for over a year. we don’t need an unofficial roadmap/faq we want a statement on what is planned for the module from ED.
  20. Like I’ve said a few times….a roadmap thread would likely reduce most of these type of threads. I guess as long as the DM folks are happy with what they’ve gotten from their contract we’re just out of luck.
  21. it does encryption without needing the Ky-58, you can change presets/freqs through the UFC, and depending on what ED decides to code “when a programmer becomes free” we may have two radios managed by one head unit.
  22. Maybe an official statement in a newsletter or a roadmap thread on what is still planned when “a programmer becomes available” would stop all the complaining and questions or at least provide a location for those with issues could be pointed to. Otherwise all we’ve gotten for almost a year is the same statement you posted above. Which to be honest is basically a slap in the face for paying customers who expected at least some development movement on a product they purchased.
  23. Actually we connect the bag to the cord (with Velcro straps or metal clips depending on the bag type) so It doesn’t move around excessively.
  24. ED considered the original A-10C feature complete years ago. That being said the TAD never had all the features the real suite 3 or 5 had. version 2 of the A-10C is missing even more TAD functionality, HUD symbology, TGP symbology, the HMCS is missing lots of symbology as well. Unfortunately we won’t get any of that and I’m not holding my breath for the ARC-210 or long ECM pod in 2022.
×
×
  • Create New...