Jump to content

Wags

ED Team
  • Posts

    11786
  • Joined

  • Last visited

  • Days Won

    59

Everything posted by Wags

  1. Thank you, all, and have fun! A lot of hours, devotion, and passion has gone into this from all the programmers, artist, designers, IT, and managers. Kind regards, Matt
  2. We are working on the ability to be in either seat for network play. It will require careful testing, and it is coming. Kind regards, Matt
  3. You can go to UTIL page and set the launchers to stow. Casmo talks about this in his rockets video, please give it a watch. Kind regards, Matt
  4. Either or both your collective and throttles are probably not zeroed out. Kind regards, Matt
  5. The TADS has a built-in level of stabilization, but LMC on the target (don't slew) can provide a rather stable look at the designation point. Later, we'll be adding the additional stabilization options. For now though, it just takes a little practice with the LMC. Kind regards, Matt
  6. The highlight of the project for me.
  7. Dear all, Although it does not have the same meaning it did before the advent of digital media, today, DCS: AH-64D went “gold”. Meaning, that the code is locked and will not be touched unless we discover a crash or error that severely impacts gameplay. We are in the final phase! Just as a reminder, once the DCS: AH-64D is released into Early Access, the 30% pre-order price will end and move to 20% for the duration the module is in Early Access. e-Shop: DCS: AH-64D (digitalcombatsimulator.com) We thank you for your patience during these last few months. We trust that the quality of the Early Access release will be up to your expectations. Kind regards, Wags
  8. DCS: AH-64D Early Access Guide Available To give you a head start learning to fly and operate the AH-64D, we have released the Early Access manual. Please find the PDF document here. https://www.digitalcombatsimulator.com/en/downloads/documentation/AH64D_flight_manual_en/ Spanning 361 pages, the guide provides a detailed accounting of all the history, sensors, weapons, systems, and basic tactics of our AH-64D. The guide is a work-in-progress, and as new systems are added to the module, the guide will be updated. We believe, more than anything else so far, that the guide illustrates the extreme amount of detail and care that has gone into this project. Enjoy. Kind regards, Wags
  9. Sooooon.
  10. Today we integrated Offset Aim Points (OAP) into our internal version. This will allow you to create two offsets from a Steerpoint (OA1 and OA2) from which you set a point to conduct an attack when set as the SPI. This is normally done on the AG radar page (TGP is possible too), and often when a good radar track cannot be had on the programmed Steerpoint or target. On the HUD, they appear as a triangle when selected from the Sighting Options at OSB 10. Kind regards, Matt
  11. It simply orients the pilot to the nose of the aircraft. Given the non-stabilized nature of the HDU, and even more so at night, it can be easy to lose nose-reference. This helps maintain that reference, and it can be used as an aiming reference. Kind regards, Matt
  12. With rockets, you'll want to be in aerodynamic trim such that the rockets fly true. If not, you can fly in nose-to-tail trim, which may feel more natural, and safer for NOE flying. Kind regards, Matt
  13. At the start of the video, I made a point to explain and show the head tracker symbol. Perhaps a few missed that part. Kind regards, Matt
  14. Warning and Caution lights.
  15. Dear all, I apologize that the video was not at clear as it should have been for some of you. It’s really a simple technique to quickly put rockets on target that was taught to me by a 64 pilot. Let me try again. When shooting a rocket, you are solving for azimuth and range when aiming. Assuming that you are first set up for aerodynamic trim, you simply place the pointy, right end of the head tracker over the desired impact point. In the case of the video, it was the ACQ Source. You would not center the head tracker over the target because the flight path vector is off to the right, so you need to compensate azimuth aiming a smidge. To set range, just move your head up and down to place the center of the I-beam at the range of the target. It does not need to be aligned in azimuth… that is what the head tracker is doing. This is just one technique; I plan to create another video for rockets that will explain another technique that may make more sense to some of you. In the end, it’s the end result that matters most, and use the technique that works best for you. Kind regards, Matt
  16. Just the cool kids.
  17. Raptor is my AH-64D sensei.
  18. Today we completed internal integration of L16 and IDM sharing of HTS/HAD emitter contacts. This will allow you to designate and share emitter location between Flight, Team, and Donors. Additionally, sharing of emitter triangulation data between flight members is also internally complete as part of the TDOA option from the HAD page. We've made further adjustments to SPI sharing regarding accurate HSD symbology that includes Flight/Team member ID. Finally, we've made good progress on adjustments to the ITR and G-onset, and internal verification tests will probably start next week. If testing goes well, we plan to have it included in the next Viper update. Progress on datalink is going well, but we still have some significant items to still complete. Once datalink is complete, work will commence on the CRUS DED page. In parallel to datalink and FM, DEST DED page, MAN bombing mode, and LADD bombing mode are in work. Kind regards, Matt
  19. Can you please provide a link? I don't recall ever making such a statement a few days ago. Rather, for some time I have been messaging by the end of Q1 2022. This provides us some buffer, that we hope we do not need to use. We sincerely apologize about the delays, and we understand your frustration, particularly for those that pre-ordered. We can only provide our best estimates at the time, which sadly has changed much more than we had wanted due to team health and technical challenges. Kind regards, Wags
  20. Closed Beta Testing Has Begun DCS: AH-64D has entered Closed Beta Testing, and this is a significant milestone. Our Closed Beta Test team consists of many community members that assist us in testing new modules near the tail-end of development as an addition quality control step. This has proved valuable for us to help identify bugs in highly complex modules that requires many eyes to ensure thorough testing. We sincerely thank all our Closed Beta Testers for their time and hard work. Testing is not always fun; it can be tireless work. A critical aspect of the Closed Beta Test effort is network play. This has historically been an area more difficult to test internally because of the requirement for many players online. Yesterday, the Closed Beta Test team conducted their first large-scale network test with excellent results. We hope you enjoy the attached images. We understand that you are eager for the release, and we are working at full speed to make this happen. We are still on track for an Early Access release before the end of March 2022. Thank you for your patience and support; it will be worth it. Kind regards, Wags
  21. Some of our customers are visually impaired in their right eye. Kind regards, Wags
  22. To finish out a busy Viper development week, we've added Markpoint exchange between flight members (IDM and L16 Steerpoint storage ranges) and hearing the "Lock" VMU message when an STT lock has been obtained while in an ACM mode. Have a good weekend, Matt
  23. With the earlier release of the DTOS mode, I got quite a few "Christ-on-a-bike, Wags, where the max toss anticipation cue?" Well, it's now in the game and should be released in the next big Viper update based on final testing results. The maximum toss (45 degree) anticipation cue consists of a circle, 100 mR in diameter, displayed on the HUD (below the boresight cross at 0 degrees azimuth and -3 degrees elevation). The cue is displayed 2 seconds prior to a maximum toss pull-up (based on 4.0g in 2 seconds). When the solution cue is displayed, the anticipation cue flashes for 2 seconds before being removed from display. Weapon release occurs as the aircraft approaches a 45-degree pitch. Because there are multiple release points that can result in weapon release, release can occur any time after the solution cue is displayed. For less than a 45-degree toss, the pitch at release varies depending on the maneuver performed. Kind regards, Matt
  24. Link 16 SPI sharing was implemented today. I think this will prove a very handy feature. With the HSD not SOI, pressing the COMM switch right (inboard) for greater than 0.5 seconds will transmit the player’s SPI to other Mission members. When a SPI message is sent, the XMT L16 label at OSB 6 will highlight for two seconds on the HSD. The sent SPI is based on the current SPI sensor track. If there is no SPI sensor track, then the current Steerpoint is sent as the SPI. When the SPI is sent, recipients see it as a large, white “X”, the same as a Mark Point. On the HUD, MKPT## will appear that assigns the SPI location to Steerpoints 71 to 70. “DATA” will be heard as a voice alert. As you can see, it is the same as receiving a Mark Point, but it based on a SPI location rather than a Steerpoint location. One difference is that if the SPI is created by the TGP or A-G FCR, there will be a lock line between the sender of the SPI (Mission members 1 to 4) and the SPI “X” symbol/location on the HSD. The line will disappear after 30 seconds or by pressing WARN RESET on the UFC. We look forward to adding this to an upcoming Open Beta. Also, to answer the posed question, yes, we plan L16 and IDM. Kind regards, Matt
  25. Much of our Viper work is now centered on the Link 16/IDM interflight datalink. This is a very important and useful element of the Viper, and currently, our highest Viper priority. With this feature in place, you will be able to: - Share Mark Points between flight members - Share SPI between flight members - Network the flight together for HARM HTS TDOA mode to more effectively triangulate emitter locations - Sending SEAD contacts between flight members - Assign air-to-air target sorting between flight members - Support Primary Datalink Track (PDLT) - CAS mission assignments and reception - Battle Damage reporting support We also wish to roll in EXP HAD and HSD support. As you might gather, this is a very complex task, and we don't have a delivery date at this time. We look forward to updating you on this task as it progresses. In parallel, other Viper items continue development such as the instantaneous turn rate / available G tuning, pilot model, bug fixes, and more. Kind regards, Matt
×
×
  • Create New...